Daryes

Sorry to chime here, but either I am missing something, or what you are asking is already the case : > As of version 5.x, Java 11 is required. Java...

@Matthew-Jenkins I've read the initial issue, yes. JDK (or more commonly named Oracle JDK) is supported, OpenJDK (Oracle or RHEL or other variants) is also supported. Now, given you're using...

The initial 100% has always been here, afaik from start. I've had other monitoring utilities with the same behavior, related to the initial connection to the system performance counters and...

@vlastahajek OP stands for Original Poster, sorry, forum habit. And yes, it's the agent collection interval. In my case, as I said, telegraf 1.7 reports false high CPU usage values,...

Separated message, after digging into the plugin code. I might have found an idea explaining the cause of the false values reported by telegraf v1.7 while juggling with the MSDN...

For what I've seen, there's already this mechanism in the telegraf win_per_counters plugin, when creating or refreshing a counter, a call to gather() is done, with the return value ignored...

I need to verify about this, I'm working with `CountersRefreshInterval=0s` which in reality disable the counter refresh. The only side effect is having telegraf blind to hardware change (like adding...

@srebhan Just checked with the latest version (v1.28.3) on a Win Server 2019 , setting back `CountersRefreshInterval` from 0 to "5m" on an idling server give back again a cpu...

Pinging this one, as I have felt on this today with the missing DEVTYPE information from the diskio plugin. Worth noting it would also close #4238 (obviously, I also have...

Just got hit by this one, still happening with Rundeck 5.5.0 on an old job created 274d ago. Funny thing is the job itself wasn't set to have any scheduled...