Sigar problems on windows 64
There are known problems with Sigar (many), including
https://github.com/elastic/elasticsearch/issues/12281
@msimos thanks for reporting. This is a known problem and this is one of the reason we removed sigar from elasticsearch 2.0.
http://www.ca.com/us/support/ca-support-online/product-content/knowledgebase-articles/tec1640327.aspx We are no longer using the SIGAR components in DevTest and they will be removed in an upcoming release of DevTest.
I think alternatives should be explored.
Do you know of any good alternatives?
no, I wish I did. Thankfully, our production servers are under Linux. It looks as though the project was just abandoned by vmware after acquisition from Hyperic...
Come to think of it. Probably just using topbeat on windows would do the job ?
Yes, personally since Elasticsearch is already in use I'm just leveraging topbeat and doing the OS level monitoring outside of Stagemonitor but I can understand the value of having this all done by one tool. I haven't used topbeat on Windows however.
Yeah, I see the value of having everything at the same place. I think the TopBeat for Windows is a workaround until a better library can be used reliably. SIGAR looks like it hasn't been touched since 2010.
Found two alternatives: https://github.com/dblock/oshi and https://github.com/profesorfalken/jHardware. Does anyone have experience with it?
OSHI looks nice :) but it's JDK7 for the older version and JDK8 for the new one. Something to consider, I suppose. Maybe there could be a notion of host info provider for the generic plugin
Crashes on win10 x64 using stagemonitor-os:0.88.9, jdk 12.0.2 hs_err_pid13232.log
Current thread (0x0000026170f3b000): JavaThread "restartedMain" [_thread_in_native, id=11360, stack(0x0000009598100000,0x0000009598200000)]
Stack: [0x0000009598100000,0x0000009598200000], sp=0x00000095981fd1e0, free space=1012k
Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native code)
C [sigar-amd64-winnt.dll+0x14ed4]
Java frames: (J=compiled Java code, j=interpreted, Vv=VM code)
j org.hyperic.sigar.Sigar.getCpuInfoList()[Lorg/hyperic/sigar/CpuInfo;+0
j org.stagemonitor.os.OsPlugin.newSigar()Lorg/hyperic/sigar/Sigar;+9
j org.stagemonitor.os.OsPlugin.initializePlugin(Lorg/stagemonitor/core/StagemonitorPlugin$InitArguments;)V+44
j org.stagemonitor.core.Stagemonitor.initializePlugin(Lorg/stagemonitor/core/StagemonitorPlugin;)V+28
j org.stagemonitor.core.Stagemonitor.initializePluginsInOrder(Ljava/util/Collection;Ljava/lang/Iterable;)V+91
j org.stagemonitor.core.Stagemonitor.initializePlugins()V+38
j org.stagemonitor.core.Stagemonitor.start()V+0
j org.stagemonitor.core.Stagemonitor.doStartMonitoring()V+45
j org.stagemonitor.core.Stagemonitor.startMonitoring(Lorg/stagemonitor/core/MeasurementSession;)V+45
j org.stagemonitor.core.Stagemonitor.reset(Lorg/stagemonitor/core/MeasurementSession;)V+63
j org.stagemonitor.core.Stagemonitor.reset()V+1
j org.stagemonitor.core.Stagemonitor.init()V+11