Monitoring Packages

Monitoring an application can require many policies, configuration files, executables, and other HPOM configurations. Now you can bundle all of these objects into a single package, allowing you to:

• check in your customized package to the version control system as a new release move your customized package to a Quality Assurance environment
• synchronize multiple production servers with the click of a mouse
  
  

Assign Monitoring Packages to nodes

MIDAS Administrator stores the application name, description, and other attributes pertaining to a monitoring package, which enables you to:

• easily identify which applications are on which nodes
• reduce the effort you spend making assignments
• easily view the monitoring for a selected application
  
  

Distribution Scheduling

• schedule distribution to nodes for a preselected time
• monitor distributions to confirm they actually completed
• automatically restart failed distributions
  
  

Desired State Verification

All the effort you put into creating high-quality monitoring applications is wasted if that instrumentation is not on the target nodes in the right release status.

MIDAS Administrator:

• knows which instrumentation is supposed to be on each managed node
• periodically checks to ensure the desired state is intact
• automatically sends error reports to responsible administrators

MIDAS Best Practice documents will help you get the most value out of Administrator very quickly. The following documents are currently being prepared and will be available on the release date. Each document has one or more use cases that were used in the design of MIDAS Administrator.

• Building Monitoring Packages
• Release Management
• Desired State Verification