SigNoz is an open-source observability platform native to OpenTelemetry with logs, traces and metrics in a single application. An open-source alternative to DataDog, NewRelic, etc. π₯ π₯. π Open source Application Performance Monitoring (APM) & Observability tool
Hi,
I'd like to say I really like SigNoz so far!
I would love to see Open Telemetry logs within the Trace Waterfall window.
I realize we can achieve similar result by simply creating span with a span.name attribute set to log's message, but that feels like a duplication of the log data that we already have anyway.
This is something that I would love to see in the end:
I feel like this would help debug certain application issues quite a bit.
As for span duration, in the screenshot logging took 1.09ms since I just wrapped the log into a span in code. I think logs could be just treated separately and not show duration next to them, just a line or point in the waterfall so we know when they happened. Let me know if that makes sense.
Thos whole thing could also be hidden behind a setting of some kind(either global, or service based), or a simple checkbox somewhere on Trace details(waterfall) page if there are people who don't want to see logs in that view. From my experience this really helps debugging any kind of problems with application logic.
Hi, I'd like to say I really like SigNoz so far! I would love to see Open Telemetry logs within the Trace Waterfall window.
I realize we can achieve similar result by simply creating span with a span.name attribute set to log's message, but that feels like a duplication of the log data that we already have anyway.
This is something that I would love to see in the end:
I feel like this would help debug certain application issues quite a bit.
As for span duration, in the screenshot logging took 1.09ms since I just wrapped the log into a span in code. I think logs could be just treated separately and not show duration next to them, just a line or point in the waterfall so we know when they happened. Let me know if that makes sense.
Thos whole thing could also be hidden behind a setting of some kind(either global, or service based), or a simple checkbox somewhere on Trace details(waterfall) page if there are people who don't want to see logs in that view. From my experience this really helps debugging any kind of problems with application logic.