In this article:
Introduction to Expansion Packages
AvailabilityGuard expansion packages enable you to add new functionality to the
product. For example, you can run your own scripts or commands, or gather data
specific to your environment. Then, you can generate custom comparisons and risk signatures based on the collected data.
Users may define 4 types of Expansion Packages:
|
Type |
Description |
|
Data Collection |
User-defined data collection: Collect additional configuration data from hosts |
|
Comparison |
User-defined comparison: Define new comparison categories based on data gathered in Data Collection packages |
|
Risk Detection |
User-defined risk signatures: Create custom AvailabilityGuard tickets (Wizard-based / SQL Query-based / Java based) |
|
Reporting |
User-defined reports: Create custom AvailabilityGuard reports – SQL queries against the AvailabilityGuard Database Views |
Diagram 1 illustrates how expansion packages co-exist with the built-in functionality and dependencies
Diagram 1: Expansion Packages dependency
Managing Expansion Packages
Expansion Packages can be added, modified or removed from the Expansion Packages page of the Configuration tab. In addition, Expansion Packages can be exported and imported to an EPX file, which is an XML file documenting the package details.
You're invited to share your expansion packages and download packages from our community pages.
Comments
0 comments
Please sign in to leave a comment.