4 ms·

you may want to check out https://github.com/SigNoz/signoz https://github.com/SigNoz/signoz I am one of the maintainers. We are building a DataDog alternative

you may want to check out https://github.com/SigNoz/signoz https://github.com/SigNoz/signoz I am one of the maintainers. We are building a DataDog alternative with native support for opentelemetry.

hosh 4y ago
I have seen it around, but didn't know it was open source. If you guys are working on correlation, then I will definitely be watching this. Consistent link urls that can be shared is also useful. Hopefully someone else will contribute the notebooks feature. Those are very useful. Something that DD is not careful about, is being able to consistently use UTC for all time labels in all graphs (and maybe a quick way to convert to a local time if we need to communicate with stakeholders). (I don't know why your comment was downvoted).
- pranay01 4y ago
  Yeah, we are actively working on correlation. We have metrics, traces and logs in a single app - so we should be able to provide a seamless correlation. Thanks for the point about Notebooks, we have not thought in detail on how people use that. Is it primarily to collaborate between team members when an incident happens or even when there is no incident, and you are analysing stuff
  - hosh 4y ago
    We have used those notebooks for: - Incidents, collecting different metrics and showing them next to each other, with comments - Longer-term reliability debugging. They can form a kind of ad-hoc dashboard. These are usually issues that degrade performance, don't have immediate or wide-spread customer impact, and are things we are not immediately able to detect - Related, performance tuning. Sometimes, the key metric is unknown. We want to explore it, and then make changes to infra, and then see if that moved the needle - Sometimes, the ad-hoc widgets are useful enough to export to a dashboard - I can take any widget anywhere else and import it into a notebook, or start a new notebook out of it. The notebooks are similar to the dashboard, just that, the layout engine only allows a linear notebook layout instead of a grid. There are already text widgets, though the button to add that is easier to access. Other than the comments, it's basically a dashboard with the UI changed so that it feels like a notebook. Keep in mind too, all dashboard and notebooks modify timestamps and other states in the browser URL, so it is easy for me to copy-paste those into Slack so that other people can see what I am seeing.
- SOLAR_FIELDS 4y ago
  We use Datadog at the medium sized unicorn I work at. People often don’t understand how important correlating timestamps is. I wish Datadog was just opinionated as hell and said everything you see is UTC by default. Or even less dramatic than that, literally just slap the time zone on whatever it is that you’re viewing. It’s so insanely critical when you’re viewing logs on a prod outage that people immediately see and understand that the logs they are looking at are PST, CST, UTC or whatever. It’s insane that software designed to help people unfuck production systems doesn’t display that by default. As-is we go through a song and dance whenever we look at logs and metrics “oh, this happened at X time which is Y time for most people.
  - hosh 4y ago
    Our ops team standardized on UTC (though not all of our tools support that). When we talk to stakeholders and customer-facing folks though, tend to convert it to local time.

you may want to check out https://github.com/SigNoz/signoz https://github.com/SigNoz/signoz I am one of the maintainers. We are building a DataDog alternative with native support for opentelemetry.

hosh 4y ago

I have seen it around, but didn't know it was open source. If you guys are working on correlation, then I will definitely be watching this. Consistent link urls that can be shared is also useful. Hopefully someone else will contribute the notebooks feature. Those are very useful. Something that DD is not careful about, is being able to consistently use UTC for all time labels in all graphs (and maybe a quick way to convert to a local time if we need to communicate with stakeholders). (I don't know why your comment was downvoted).

pranay01 4y ago
Yeah, we are actively working on correlation. We have metrics, traces and logs in a single app - so we should be able to provide a seamless correlation. Thanks for the point about Notebooks, we have not thought in detail on how people use that. Is it primarily to collaborate between team members when an incident happens or even when there is no incident, and you are analysing stuff
- hosh 4y ago
  We have used those notebooks for: - Incidents, collecting different metrics and showing them next to each other, with comments - Longer-term reliability debugging. They can form a kind of ad-hoc dashboard. These are usually issues that degrade performance, don't have immediate or wide-spread customer impact, and are things we are not immediately able to detect - Related, performance tuning. Sometimes, the key metric is unknown. We want to explore it, and then make changes to infra, and then see if that moved the needle - Sometimes, the ad-hoc widgets are useful enough to export to a dashboard - I can take any widget anywhere else and import it into a notebook, or start a new notebook out of it. The notebooks are similar to the dashboard, just that, the layout engine only allows a linear notebook layout instead of a grid. There are already text widgets, though the button to add that is easier to access. Other than the comments, it's basically a dashboard with the UI changed so that it feels like a notebook. Keep in mind too, all dashboard and notebooks modify timestamps and other states in the browser URL, so it is easy for me to copy-paste those into Slack so that other people can see what I am seeing.
SOLAR_FIELDS 4y ago
We use Datadog at the medium sized unicorn I work at. People often don’t understand how important correlating timestamps is. I wish Datadog was just opinionated as hell and said everything you see is UTC by default. Or even less dramatic than that, literally just slap the time zone on whatever it is that you’re viewing. It’s so insanely critical when you’re viewing logs on a prod outage that people immediately see and understand that the logs they are looking at are PST, CST, UTC or whatever. It’s insane that software designed to help people unfuck production systems doesn’t display that by default. As-is we go through a song and dance whenever we look at logs and metrics “oh, this happened at X time which is Y time for most people.
- hosh 4y ago
  Our ops team standardized on UTC (though not all of our tools support that). When we talk to stakeholders and customer-facing folks though, tend to convert it to local time.