Second this. It’s pretty terrible when you use it at scale particularly. Eg: If you have a monitor with some scopes that you use for exceptions, it gets gnarly in the UI when you have like 50 of them. And the inconsistent UI. Notebooks are cool but so half-assed in their features that it kind becomes useless for anything other than basic charts. Oh and feature discovery is a pain too. It took me so long to figure out a way to add a second Y-axis to my charts.

Interesting. do you mean this by scopes - https://docs.datadoghq.com/api/latest/scopes/ ?

Not exactly. I’m talking about this workflow. https://www.datadoghq.com/blog/mute-datadog-alerts-planned-d...

You use specific tags to mute a monitor by adding a scope. This does not scale well with the UI.

ah, got it. Thanks

Been using it for ~5 years full time and the UI is one if the main reasons to use Datadog vs hand rolling it based in Grafana. The productivity of developers creating datadog dashboards vs in other tools was way better.

Have you ever timed how long it takes a normal user to do certain things easily, say during an incident, or you're just crapping on the CSS?

Curious, what areas do you think the DataDog UX is especially better compared to Grafana? Also, which flows do you use the most in DataDog

I have the opposite opinion. We used Cloudwatch originally but switched to Datadog and it was night and day. Datadog has a beautiful interface for logs, metrics, and dashboarding.

Yeah, we have had some of our users mentioning that DataDog has become too bulky and too many bells and whistles.

Curious though, what specific features/UX did you not like in DataDog?

I have the opposite feeling - to me it looks nice and better than Dynatrace or elastic.

gatta keep polishing that turd! there is a promo packet that needs filling.