https://signoz.io
Join Slack
Hello guys, anyone knows if it is possible to show all related lines when clicking on a log, instead...
# support
j
Hello guys, anyone knows if it is possible to show all related lines when clicking on a log, instead of just the one I selected?
v
what do you mean by related lines ? are your log lines spread across multiple lines ? or you want to see the related logs from the same resource ?
j
Take the below logs as an example, it's printed across multiple lines 
2024-10-23 15:45:01.123 | ERROR | 0|calcTjApp | Error: Request failed with status code 500 at createError (/app/node_modules/axios/lib/core/createError.js:16:15) at settle (/app/node_modules/axios/lib/core/settle.js:17:12) at IncomingMessage.handleStreamEnd (/app/node_modules/axios/lib/adapters/http.js:260:11) at IncomingMessage.emit (events.js:327:22) at endReadableNT (_stream_readable.js:1327:12) at processTicksAndRejections (internal/process/task_queues.js:80:21)
Currently if I were to click on any of the above lines, it'll only show me that line of logs and its details. But I want to be able to see every line so I know these bunch of logs are "together" if that makes any sense.
d
There is the Context tab on the Log details view. However, you will need to manually input a filter so that it only shows the context that you are interested in, e.g. of a certain service or so. By default, Context simply means the log lines received before and after across all services
v
@Jason Wong - https://signoz.io/docs/userguide/parse-multiline-logs/ this should help you with multi log line configuration
j
I'll take a look into it, thank you!
@Vikrant Gupta Hello sir I'm back. Regarding the multiline parser, I can't seem to get it to work. I'm using signoz helm chart to deploy and below is my otel collector configurations: otelCollector: service: type: LoadBalancer annotations: service.beta.kubernetes.io/aws-load-balancer-internal: "false" service.beta.kubernetes.io/aws-load-balancer-type: "nlb" service.beta.kubernetes.io/aws-load-balancer-nlb-target-type: "ip" service.beta.kubernetes.io/aws-load-balancer-backend-protocol: "tcp" service.beta.kubernetes.io/aws-load-balancer-cross-zone-load-balancing-enabled: "true" service.beta.kubernetes.io/aws-load-balancer-target-group-attributes: "preserve_client_ip.enabled=false" config: receivers: filelog: include: - /var/log/*/**/**.log multiline: line_start_pattern: ^\d{2}-\d{2}-\d{2} I've tried hardcoding the log file path, change it to an easier pattern but still to no avail.
14 Views
Open in Slack
PreviousNext
Powered by

SigNoz Community

SigNoz is an open-source APM. It helps developers monitor their applications & troubleshoot problems, an open-source alternative to DataDog, NewRelic, etc.

Powered by