Forum Discussion

Joe_Williams's avatar
11 months ago
Solved

Config Backup Reports

We are migrating from a legacy tool to LogicMonitor for Configuration Backups, but just noticed one issue. There isn’t a built in way to report on when the last config was backed up and when the last config checked to see if there is a new one to backup. Some clients want to see this VS “no alarms”.

  • Yeah, API might be your only option. Time to send a feature request to the black hole.

5 Replies

  • You can do a dashboard with a NOC style widget(s).  Have one show “retreival check” problems and another that could show “change detected” info.  While it wont show those dates mentioned above it does give a graphical representation of the bigger picture.

    One thing to note here our Common Configs have actually had the default alerting changed from the ConfigSources they replaced to no longer alert on retrieval failures.  So, if you are using our Common ConfigSources they will not by default do that, they do still alert on the difference tests though. 

    Also as an aside, we have finally gotten our Common ConfigSource documentation published:

    https://www.logicmonitor.com/support/common-config-monitoring 

  • You can do a dashboard with a NOC style widget(s).  Have one show “retreival check” problems and another that could show “change detected” info.  While it wont show those dates mentioned above it does give a graphical representation of the bigger picture.

  • Yeah, API might be your only option. Time to send a feature request to the black hole.

  • The Last Checked and Last Updated timestamps contain this. Last Checked is the last time LM checked for a change to the config. The Last Updated indicates the last time LM pulled the config into LM and stored it.

    In my screenshot here, the config was changed on 6/26 at 23:09. As of 12:03 on 6/27, the config has been inspected and found not to differ from the config fetched at 23:09 on 6/26.

  • So yeah, no actual way to report on it other than something through the API.

    Which then makes it harder to show the client we are actually backing up their configs.