Configuring SigNoz for JSON Logs Extraction
TLDR Justin faced issues with column addition in the SigNoz UI for parsed JSON logs. nitya-signoz guided them on parsing the log body to extract keys to be used as columns in UI.
vishal-signoz
Fri, 13 Oct 2023 00:23:46 UTCnitya-signoz can answer this
Justin
Fri, 13 Oct 2023 01:43:30 UTCI would appreciate it a lot! :slightly_smiling_face: I think my core question is : "can I pull all the keys out of the "body" (which is just a JSON string) and put them at the top level, so they can be arbitrarily used as columns in the List View". Keys are arbitrary based on the application and it would be annoying to have to keep editing the config to statically define them.
nitya-signoz
Fri, 13 Oct 2023 05:39:24 UTCYes you can for that you will have to parse your log body
SigNoz Community
Indexed 1060 threads
Built with ClickHouse as datastore, SigNoz is an open-source APM to help you find issues in your deployed applications & solve them quickly | Knowledge Base powered by Struct.AI
View in App
Justin
Thu, 12 Oct 2023 05:26:09 UTCHi all, I am using signoz to pull logs from docker. I don't have much visibility into the signoz setup - it's been handed to me by a different team. Our application sends JSON logs, and I can perform useful queries against it. So far so good. Our application produces arbitrary k/v fields, and I can see them all being parsed in the body of each log line. So for example, I can see body.file (source code file) and body.level (log level). I can do queries like "body.level = 'whatever'. However I can't seem to add them as columns in the "List view" of the UI - which is what I need to make this usable by other members of the team. Am I "holding this wrong"? Do I need to either log differently, or configure signoz differently?