457 views

How can we monitor SA MM environment

Hello,

 

We use SA MM at Linux env. and want to monitor SA status and performance.

We have a lot of different monitoring tools 

How can we monitor SA?

We will create an alarm? 🙂

0 Likes
3 Replies
Vice Admiral Vice Admiral
Vice Admiral

Hi Serkan,

For an overall monitoring of Server Automation you may run the run_all_probes.sh script which will check the status of all SA components.

You could run it with the following command:

/opt/opsware/oi_util/bin/run_all_probes.sh run

You can create a custom script that could execute run_all_probes.sh periodically (i.e. cronjob) and send an email alert if there are any failures in the output

You may also monitor specific SA core components.

For more information on how to monitor specific components please refer to the section "Monitoring SA Core components" on page 285 of the Server Automation Administration Guide.

Here is a link to the document:

https://softwaresupport.hpe.com/group/softwaresupport/search-result/-/facetsearch/document/KM01663663

I hope this answers your question.

Best regards,

Nikola

Micro Focus Customer Support

If you find that this or any post resolves your issue, please be sure to mark it as an accepted solution.
0 Likes

Hi Nikola,

 

How about performance monitoring? Sometimes we saw run_all_probes.sh results are ok but SA is too slow? We had to restart services.

How can we investigate performance problems?

 

Regards

0 Likes
Vice Admiral Vice Admiral
Vice Admiral

Hi Serkan,

The performance problems could have different and sometimes complex root causes so there is no tool for complete monitoring.

You could monitor the SA logs for some common problems.

For example, you could monitor for out of memory errors with a command similar to this one:

find /var/log/opsware/ -type f -exec grep "OutOfMemory" '{}' \; -print

Or you could monitor the twist logs for slow SQL queries that exceed the warning threshold of 10 seconds, the warning looks like below:

2017-01-05 09:25:33,911 WARNING Thread-12 [com.opsware.twist.utils.SQLHelper] [checkForElapsedTimeWarning] SQL elapsed time (13.064 seconds) exceeds warning threshold (10 seconds)
java.sql.SQLException: SQL was successful but the elapsed time threshold was exceeded

If you experience performance issues it is best to open a case with the Server Automation support team to investigate them further.

Best regards,

Nikola

Micro Focus Customer Support

If you find that this or any post resolves your issue, please be sure to mark it as an accepted solution.
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.