-
Notifications
You must be signed in to change notification settings - Fork 25.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Replacing sigar #11995
Replacing sigar #11995
Conversation
For the record, here are some data collected by the Empty values means "not supported". Linux - Oracle Corporation Java HotSpot(TM) 64-Bit Server VM (1.8.0_20)
Linux - Oracle Corporation OpenJDK 64-Bit Server VM (1.7.0_79)
Windows 8.1 - Oracle Corporation Java HotSpot(TM) 64-Bit Server VM (1.8.0_25)
|
public Long processSystemTime() { | ||
if (!threadMxBean.isThreadCpuTimeSupported()) { | ||
throw new UnsupportedOperationException("JmxProcessProbe does not support process user time"); | ||
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do you happen to know if any platforms where this returns false?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No. This method is documented as the flag to indicate if CPU time is supported, I think it makes sense to use it here before requesting value
Closed in favor of #12010 , I keep the code here for the record. |
A first step in order to remove sigar (see #11034)
This pull request removes all Sigar stuff and adds the ability to query multiple probes at once. It focused on
Process
stats/info for now and serves as an example for the other stats we have (Os, Fs, Network).