3 ms·
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
by aloknnikhil 4y ago
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.
- pranay01 4y agoInteresting. do you mean this by scopes - https://docs.datadoghq.com/api/latest/scopes/ https://docs.datadoghq.com/api/latest/scopes/ ?
- aloknnikhil 4y agoNot exactly. I’m talking about this workflow. https://www.datadoghq.com/blog/mute-datadog-alerts-planned-downtime/ 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.
- pranay01 4y agoah, got it. Thanks