That is good to hear, are the script executed at a regular interval before hand or at the time the OID is queried by the cacti server?erwan.l wrote:1/
The Script part (batch, vbs, executable or any process than output a result) will be run on the client part, not on the server part.
So there is no overhead on the server part.
But us windows cacti implementors can also benefit good work. The perfmon counters within the world of WMI are usually called with a Win32_PerfRawData_PerfDisk_LogicalDisk class, how do I represent the same class with your config file?erwan.l wrote:2/
My initial goal was to benefit from windows features (perf counters, vbs, wmi, etc) with a linux cacti server.
For the non wmi perfmon counters, the agent natively supports it : just indicate the path in the ini file.
This was actually the first feature of this agent.
Could you attach a standard SNMP template? as I purged all of mine from the default install thinking I would not need them....erwan.l wrote:3/
You can graph anything you can think of : by the end, cacti will always receive it as an snmp value, so only regular snmp templates are necessary.
I also was looking at some of your documentation, you said you support SNMP walk, but correct me if I am wrong, to setup something like an snmp query template, I would have to taylor the ini file to include all the instances of say drives on my system, you have no automated fuctions for that. Maybe something for me to script as part of a deployment for my servers....
All I would need is a slightly modified INI files for those servers that have more then one of the following, Network cards, CPUs and Disks is that also a correct statement?erwan.l wrote:4/
For the rolling out, copy paste the dll to system32, register a reg file and your are done.
This could easily be automated and/or I could do an installation setup.
I also advise you make one unique ini file for your company defining your own OID list.
Great news! Should make some of my IT security guys happy that MS still would control the access to the counters.erwan.l wrote:5/
This agent will be hosted by the MS snmp service : all snmp aspects are managed by the MS service (community, traps, security, etc ...).
The only specific to my snmp agent is the enterprise OID.
Question: If someone were to be "nasty" could they not interject some nasty exe string into the ini file causing a lot of problems? Could I lock that INI file down, to where only the local system account as well as my account or another admin has access, or are there additional rights needed?
Thanks!
I hope this answered your questions
Regards,
Erwan.