• State Suggested Answer
  • Locked Locked
  • Replies 3 replies
  • Answers 2 answers
  • Subscribers 58 subscribers
  • Views 3819 views
  • Users 0 members are here
Options
Related
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Alarms Analysis Dashboard Question

Jason
over 6 years ago

I'm seeking some clarification on this Knowledgebase Article:
Alarm Analysis Cartridge plug in for Foglight and Foglight for Virtualization Enterprise. (144909)

The notes in this article state that in the 5.7.5.7 FMS release, the Alarm Analysis tab has been added to the Alarms Dashboard. (Note: The KB article also has attached the AlarmAnalysis-2_2_4 cartridge and it is indicated that this is a community maintained cartridge.)

I'm just trying to understand what the change that was introduced in 5.7.5.7 really amounts to. Is it that the cartridge remains unsupported by Quest but the official Foglight product has added only the "Alarms Analysis" tab to the official Alarms dashboard, enabling such if the unsupported cartridge happens to be installed?

If I disable the AlarmAnalysis cartridge (I've had it installed for quite some time), does the new Alarms Analysis tab go away, not function, etc? Or is the functionality of the AlarmAnalysis cartridge now integrated into the official product now making the AlarmAnalysis-2_2_4 cartridge no longer required to be installed separately?

Hopefully my question is clear and someone can clarify...

Thanks

Parents
  • 0 over 6 years ago

    You are welcome Jason.

    I took a look ClearandDeleteAlarms community cartridge ( https://stage.quest.com/community/products/foglight/m/administrators/22  ) and it only have one rule (AlarmClearAfterDays) and two registry variables (AlarmClearAfterDays and AlarmDeleteAfterDays)

    Start from FMS 5.7.1, we have a similar setup which use registry variables (AlarmPurgeAge) to control how long we keep the alarm but it only for purge not auto clear like this community cartridge did

    So you can still keep it if you like auto clear feature or uninstall it and use our build in purge feature

    Here are more information about this building feature (FGL-17243 )

    The server now contains a registry variable AlarmPurgeAge that sets the number of days that cleared alarms are allowed to remain in the system before they are purged during nightly maintenance. By default, Foglight keeps alarms in the system is 30 days, after that they are purged.

    Hope this helps

    Best Regards

    -Lee

Reply
  • 0 over 6 years ago

    You are welcome Jason.

    I took a look ClearandDeleteAlarms community cartridge ( https://stage.quest.com/community/products/foglight/m/administrators/22  ) and it only have one rule (AlarmClearAfterDays) and two registry variables (AlarmClearAfterDays and AlarmDeleteAfterDays)

    Start from FMS 5.7.1, we have a similar setup which use registry variables (AlarmPurgeAge) to control how long we keep the alarm but it only for purge not auto clear like this community cartridge did

    So you can still keep it if you like auto clear feature or uninstall it and use our build in purge feature

    Here are more information about this building feature (FGL-17243 )

    The server now contains a registry variable AlarmPurgeAge that sets the number of days that cleared alarms are allowed to remain in the system before they are purged during nightly maintenance. By default, Foglight keeps alarms in the system is 30 days, after that they are purged.

    Hope this helps

    Best Regards

    -Lee

Children
No Data