Hello everyone,
I am currently trying to monitor a Mirth instance in my IT environment using Checkmk.
Unfortunately, I don’t have login credentials for a running Mirth instance, but I can access data through a dedicated channel that provides Mirth statistics.
I would like to verify how the agent output (the data returned from the Mirth API or from the special channel) should look when the system is operating normally.
Could someone please post a short example of the raw output from a working Mirth server as received by the Checkmk agent?
This is what my channel currently returns:
<<<mirth_unkooperativ:sep(124)>>>
[[HEADER]]
i|channelID|cName|cState|cDeployed|cQueued|cReceived|cFiltered|cSent|cError|
[[DATA]]
0|21112345-121f-4feb-8348-6316b0c12345|PDF to PDFCore|Started|true|0|7706|0|7706|0
1|7ee12345-2243-4b4c-b341-424511512345|MDM to Channel 2|Started|true|0|615|0|615|0
I’d like to confirm whether this matches the expected format or if the agent normally produces additional sections, headers, or metrics.
To clarify: if I can see an example of the expected data format that the plugin processes, I can easily adjust or remap the data I already receive so that it works with the Checkmk Mirth integration.
This would be much simpler than trying to get login credentials from the vendor just to access the Mirth API.
Thanks in advance for any example output or hints!
Hello everyone,
I am currently trying to monitor a Mirth instance in my IT environment using Checkmk.
Unfortunately, I don’t have login credentials for a running Mirth instance, but I can access data through a dedicated channel that provides Mirth statistics.
I would like to verify how the agent output (the data returned from the Mirth API or from the special channel) should look when the system is operating normally.
Could someone please post a short example of the raw output from a working Mirth server as received by the Checkmk agent?
This is what my channel currently returns:
<<<mirth_unkooperativ:sep(124)>>>
[[HEADER]]
i|channelID|cName|cState|cDeployed|cQueued|cReceived|cFiltered|cSent|cError|
[[DATA]]
0|21112345-121f-4feb-8348-6316b0c12345|PDF to PDFCore|Started|true|0|7706|0|7706|0
1|7ee12345-2243-4b4c-b341-424511512345|MDM to Channel 2|Started|true|0|615|0|615|0
I’d like to confirm whether this matches the expected format or if the agent normally produces additional sections, headers, or metrics.
To clarify: if I can see an example of the expected data format that the plugin processes, I can easily adjust or remap the data I already receive so that it works with the Checkmk Mirth integration.
This would be much simpler than trying to get login credentials from the vendor just to access the Mirth API.
Thanks in advance for any example output or hints!