Collector ConfigSource(s)


Recommended Posts

  • LogicMonitor Staff

A couple of choices of ConfigSource to monitor the .conf files of your collectors.

Note these are two versions of the same thing - you do not need both.

One explicitly monitors only the four key .conf files; agent.conf, sbproxy.conf, watchdog.conf, wrapper.conf. That's done via the Active Discover script simply printing those four known filenames as instances:

76PEZ2 (v1.2)

The other version has a more involved Active Discovery that lists any .conf found in the Collector config folder, with the exception of 'persistent_task.conf' as this file is continually being updated. This has the advantage that it will catch any new or renamed .conf files we add in in future:

K992D7 (v1.2)

The collection script of each simply reprints the content of each .conf file and alerts on changes, with a couple of exclusions for expected changes.

AppliesTo = hasCategory("collector")

They are grouped to appear within the 'Collector' datasource group on the devices alongside the collector-specific datasources.

5937d8f680943_ScreenShot2017-06-07at11_41_38.thumb.png.4b0ecc5c7515e22e86492725f1202b40.png

Edited by Antony Hawkins
Updated with v1.2 locators
Link to comment
Share on other sites

  • 5 weeks later...
  • 1 year later...

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

 Share