[nrmitchi]

Tip, if you happen to be using datadog, make sure datadog agent logs are disabled from being ingested into datadog.

If you can disable them at the agent level and avoid the data out that would be even better.

At a previous employer the defaults were quite literally half of our log volume, that we were paying for. I was doing a sanity check before renewing our datadog contract and was very not-pleased to discover that.

[fat-apple]

We’re about to release a Datadog compatible API so you can point your Datadog agent at Opstrace instead (stay tuned for the blog post). Our goal is to be able to tell you exactly how much data the agent is sending and how much that is costing you (and for example what services/containers are responsible for the bulk of the cost). Here’s a list of the PRs: https://github.com/opstrace/opstrace/pulls?q=is%3Apr+is%3Acl...

[mdaniel]

I even opened a support ticket for their stupid python agent logging its connection refused tracebacks on every metrics poll and was told "too bad"

They really don't give one whit about log discipline or allowing the user to influence the agent's log levels

[englambert]

Perhaps on a related note, see this discussion about the power of incentives here: https://news.ycombinator.com/item?id=25994653

[brodouevencode]

Lol no, the other really large one. Five minute Cloudwatch polling defaults are just overkill even in production.