I feel like an alerting tool that doesn't link you to an actionable display or other information that can make it work - it feels like it's a problem where they want to make it "sticky"
And *please* don't make be use the stupid AWS instance id rather than picking a tag as the ID. Or, at worst, let me use the *standard tag* called Name.
Sure, it's not a mandatory identifier - but if I have it - it's because I want it!
@Rivetgeek Good - I am just .... so frustrated - I don't want to change everything in my new job - but Datadog is so bad
I have CloudTrail for logs - and I wish we'd either double down on it, or stop using it. But I really wish I wasn't getting garbage shoveled into a slack channels without a link to the actually actionable information damnit.
I wish... I could just... get alerts that meant there was a problem and had info about where
@Rivetgeek I just had a massive "change every tool we're using" sweep which kinda sucks, so I'm gonna hold off, but I'll definitely give it a look for when my political capital refreshes
silverwizard
in reply to silverwizard • •silverwizard
in reply to silverwizard • •And *please* don't make be use the stupid AWS instance id rather than picking a tag as the ID. Or, at worst, let me use the *standard tag* called Name.
Sure, it's not a mandatory identifier - but if I have it - it's because I want it!
silverwizard
Unknown parent • •@Rivetgeek Good - I am just .... so frustrated - I don't want to change everything in my new job - but Datadog is so bad
I have CloudTrail for logs - and I wish we'd either double down on it, or stop using it. But I really wish I wasn't getting garbage shoveled into a slack channels without a link to the actually actionable information damnit.
I wish... I could just... get alerts that meant there was a problem and had info about where
silverwizard
Unknown parent • •