Anyone using "TextMatch" in a DataSource Datapoint? (without hard-coding the regex)
Is anyone using the "TextMatch" type of Datapoint Post-Processing Interpreter with a Property?
https://www.logicmonitor.com/support/logicmodules/datasources/datapoints/normal-datapoints (search on the page for "TextMatch")
I'm building a DataSource using SNMP as the Collect method (to try and keep things simple) and I want to be able to parse the full output from nsExtendOutputFull https://www.circitor.fr/Mibs/Html/N/NET-SNMP-EXTEND-MIB.php#nsExtendOutputFull to look for an expected substring.
For example if my SNMPd conf entry is
then I thought I could have a Device Property (or Instance-Level Property) containing the expected "splunkd is running" and then in the Datapoint regex it would be possible to drop in that Property name tokenized like ##TextMatch.substring##
Unless I'm mistaken, the only other way I'd be able to post-process text strings like this would be either
- a Groovy Complex Datapoint, or
- to completely switch the DataSource over from SNMP Collect to Script and write everything in Groovy (which I could do but I'm hoping to avoid that complexity)
Thoughts? Comments? Am I completely out of my mind to be thinking about a Property in a TextMatch Datapoint?
LM User
·3 years agoSwitch to scripted and use SSH. Avoids having to configure anything on the far side and you can pull in the tokenized regex patter right into the script. SNMP extensions are not scalable.