Configuring Self-Health Monitoring for Remedy SSO PostgreSQL
After you install BMC PATROL for PortgreSQL, you must configure the individual components. We strongly recommend you to use a monitoring policy to configure the KM and setup the thresholds.
For more information on creating a monitoring policy, see Defining a monitoring policy.
Configuring the monitoring policy
Use the following table to choose the values while setting up the extended monitoring policy:
Variable | Value |
---|---|
Environment name | Specify an environment name of your choice. For example, TrueSight. |
PostgreSQL host | Specify the hostname of the Remedy SSO server. |
PostgreSQL port | Specify the Remedy SSO port number. The default port is 5438. |
Username | Specify the admin user name that you configured with Remedy SSO. The default user name is postgres. |
Password | Specify the admin user password that you configured with Remedy SSO. |
PostgreSQL database name | Specify the database name that you installed with Remedy SSO. The default database name is rsso. |
JAVA Home | Specify the JAVA_HOME path or the JRE installation directory. For Remedy SSO, the default JRE path is:
|
Local OS Account | Specify the remote host user you used when you installed the Remedy SSO server. |
Local OS Password | Specify the user account you used when you installed the Remedy SSO server. |
Setting up the thresholds for Remedy SSO PostgreSQL
In addition to configuring the monitoring solution, the policy must also include the thresholds settings to monitor the health of the database. The following table contains a list of threshold values that can be used to monitor the health of the Remedy SSO PostgreSQL database.
Knowledge Module | Application Class | Parameter | Threshold value |
---|---|---|---|
PATROL for PostgreSQL 1.0 | PGR_DB | Status | 1 - Not OK |
PGR_TS_METRICS | SpaceUsedPCT | <90% |
Comments
Log in or register to comment.