Olivier Vielpeau

Hi @sodabrew, is there a reason you're still using Agent v5? Active feature development is now done on the Agent v6/v7, located in this repository: https://github.com/DataDog/datadog-agent/, and Agent v6/v7 is...

@minzhuo @cvkrreddy thanks for reporting these issues. Since these issues seem quite specific to your environments, please contact our [support team](http://docs.datadoghq.com/help/) and send them your [logs](https://docs.datadoghq.com/agent/troubleshooting/#send-a-flare). Thanks!

Hi @alecl, unfortunately the 5.8 merge window is closing soon and we haven't been able to work on this issue yet. I'll move this issue back to Triage, we'll make...

At first glance, the way we could do this is with WMI, and we're trying to get away from WMI, not use it more (we've had issues with WMI consuming...

Thanks @dovdor for your feedback. I'm adding this to our Triage backlog, we're going to assess what the timeline for this feature could be. Will keep you updated.

Moving to 5.9.0 as the merge window for 5.8.0 is closing soon

Moving back to triage until we can prioritize this for a future release. Feel free to comment here if this is a high priority feature for you.

Hi @mjbruder! By default the check can't determine if it should send `OctetString`s as gauges or counters, hence the warning you get. Have you tried setting the `forced_type` parameter (see...

@mjbruder: your example should work, that said one of the current limitations of setting `forced_type` is that all the `symbols`' values will be cast to integers and sent as either...

(for example the values `1.2` and `1%` wouldn't work currently)