Monitoring the Presentation Server environment


You can monitor the TrueSight Presentation Server environment, so that you are alerted when a service becomes unavailable.

Alerts are generated in the form of automated email or events, or both.Use the following table to understand the types of alerts generated for the monitored services:

Monitored service

Alerts generated
EventsAutomated
emails
Both
Remedy Single Sign-On server(tick)(tick)(tick)
Database (PostgreSQL) service(tick)(tick)(tick)
Index (Elasticsearch) server(error)(tick)(error)
Failover of high-availability installations(tick)(tick)(tick)

Components registered with the TrueSight Presentation Server

(Only when disconnects)

(tick)(error)(error)
Database backup(tick)(error)(error)

Self-monitoring email alerts

The monitored services are checked every 10 seconds for availability and an email is generated after five unsuccessful retries.

By default, self-monitoring email alerts are not configured. You can configure self-monitoring email from the command line.

To configure self-monitoring email alerts

  1. From a command prompt, go to the <Presentation Server installation directory>\TrueSightPServer\truesightpserver\bin directory.
  2. Run the following commands to set up the email alerts:

    CommandValueExample
    tssh properties set mailer.enabledtrue to enable email alerts; false to disable email alerts.tssh properties set mailer.enabled true
    tssh properties set mail.to.addressesThe email address or a comma separated list of email addresses to send the alerts to.tssh properties set mail.to.addresses user@xyz.com
    tssh properties set mail.from.addressThe "From" email address that you want to be displayed in the email alerts.tssh properties set mail.from.address admin@xyz.com
    tssh properties set mail.server.hostnameThe email server host name.tssh properties set mail.server.hostname mail.xyz.com
  3. Run the following command to apply the properties:
    tssh properties reload

  4. (Optional) Run the following command to view the properties that are set:
    tssh properties list

Note

After you receive a self-monitoring email alert, restart the entire TrueSight Presentation Server services and not just the affected service.

Go to the <Presentation Server installation directory>\TrueSightPServer\truesightpserver\bin directory and run the following commands:
tssh server stop
tssh server start

Self-monitoring events

The Events page of the TrueSight console displays self-monitoring events for the following conditions:

  • Unavailability of the Remedy Single Sign-On server
  • Unavailability of the database (PostgreSQL) service
  • Unavailability of components registered with the TrueSight Presentation Server
  • Failover on high-availability-enabled installations

Note

  • Only users with the Super Admin role can view self-monitoring events.
  • The self-monitoring events gets closed automatically after the service is restored.

Self-monitoring events are indicated by theicon. The event severity determines the color of the icon.

Click an event timestamp to view details about the event.

Tip

The text Self-Monitoring is prefixed to self-monitoring events. On the Events page, enter Self-Monitoring in the search box to display only self-monitoring events.

Monitoring the Presentation Server PostgreSQL database performance

The TrueSight Presentation Serveruses PostgreSQL as the back end database for storing information about the components configured in it.

You can use the PATROL for PostgreSQL KM to monitor the information about TrueSight Presentation Server configured components.

The following table lists the recommended attributes to monitor:

Important

The parameter values listed in the following table are for reference only. These values are the results of the tests performed in the BMC lab and might vary depending on the configuration.


AttributeDescriptionObserved value

InstanceAvailability
(Instance availability status)

Displays the PostgreSQL environment's configuration status.0-OK

PGR_DB
(Database availability status)

Displays the status of the database availability.0-OK

DBNumElementsWaiting
(Number of elements waiting for lock)

Displays the number of elements waiting to get a lock.0 (average)

DBNumOfLockedElements
(Number of locked elements)

Displays the number of locked database elements.1 (average)

DBCacheUsage
(Database cache usage)

Displays the amount of cache memory usage in the PostgreSQL database.99.5% (average)

SpaceUsedMB
(Space used in MB)

Displays the amount of space used (MB) in the tablespace of PostgreSQL database.80MB space utilization for pg_default tablespace (average)

Monitoring the Presentation Server Elasticsearch performance

The TrueSight Presentation Server stores events in Elasticsearch. You can use the PATROL for Elasticsearch KM to monitor the Elasticsearch database by using the standard process monitor KPIs.

Following are a few observations from the BMC lab testing:

  • Approximately, 100K events were stored in the Elasticsearch database every day.
  • Events are marked for deletion from the system under the following conditions:
    • Closed events are marked for deletion 24 hours after the closure.
    • Aged events are marked for deletion 30 days from the creation date.
  • Internal processes in Elasticsearch clear the marked for deletion entries periodically.
  • An average of 5 million documents are stored per day.
    The number of documents that can be stored in Elasticsearch depends on the number of received events and event operations, such as closing of events. 

The following table lists the recommended attributes to monitor:

Important

The parameter values listed in the following table are for reference only. These values are the results of the tests performed in the BMC lab and might vary depending on the configuration.


AttributeDescriptionDepends onObserved value

Document Count

Total number of documents across all nodes.

The number of events in the system and number of event operations

5 million (average)

Documents Deleted

Number of documents deleted across all nodes.

The rate of closure and pruning of events

1 million (average)

Query Cache Count

Number of items in the query cache across all nodes.

Depends on the number of event operations.

9 million (approximately)

Query Rate

Rate of queries served in one millisecond (used as indicator to measure efficiency of queries).

Depends on the number of event operations.

15 queries per millisecond (approximately)

Average Response Time of a Query

Average response time of a query in milliseconds.

Depends on the number of event operations.

0.2 milliseconds (approximately)

Related topics

TrueSight Operations Management overview

Monitoring and managing events

Configuring and managing the Presentation Server


Was this page helpful? Yes No Submitting... Thank you

Comments