Integrating with TrueSight Operations Management to monitor events and services

TrueSight Operations Management is a software that enables you to monitor performance and availability of the infrastructure and applications that comprise your services, monitor events coming from the infrastructure devices, and monitor transactions from the applications that enable the services they deliver. As a tenant administrator, you use BMC Helix Intelligent Integrations to add, edit, and delete integrations with TrueSight Operations Management.

For conceptual information about BMC Helix Intelligent Integrations, see Integrating.

Enabling, disabling, or deleting integrations

Event slot update

BMC Helix Intelligent Integrations gets data updates that come in from the third-party solutions. If the data is updated in the third-party solutions, the changes are applied in BMC Helix Intelligent Integrations also. For example, if data for an event is updated in a third-party solution, the changes are applied in BMC Helix Intelligent Integrations and event slots get overwritten in BMC Helix Operations Management.

Before you begin

Ensure that you have downloaded and installed the Connector. You must choose the Base Connector connector type while downloading the connector. Without the Connector, you cannot proceed with the integration.

Important

Download the script on a docker-enabled Linux server.
The TrueSight Operations Management host must be accessible from your docker-enabled Linux server.

To integrate with TrueSight Operations Management

The page Integrating with Dynatrace to monitor events and services was not found -- Please check/update the page name used in the MultiExcerpt-Include macro
On the TrueSight Operations Management tile, click Configure.
Enter the following source details:
- Integration Name: Provide a name for the integration.
- Select Connector: Select a Connector. If no Connector is available, click the Add Connector icon to download and install a Connector.
- User Name and Password: Enter the administrator credentials for the product to be integrated.
- API URL: Add the following information:
  - If TrueSight Operations Management is deployed in a high-availability environment, enter the URL of the TrueSight Presentation Server load balancer.
  - If TrueSight Operations Management is not deployed in a high-availability environment, enter the TrueSight Presentation Server URL.
- Tenant Name: Enter the name of the tenant where TrueSight Operations Management is installed.
- Refresh Time for Event In Seconds: Enter the time interval in seconds to refresh the event data.
- Refresh Time for CI in Hours: Enter the time interval in hours after which the TrueSight Operations Management CI is refreshed.
- Select entities to be registered: Select one or all of the available entities to view their data. You can view the data in BMC Helix Dashboards .
Click Configure to configure the integration.
You can view the added integration from Integrations > Configured Integrations.
You can also see the data being received and view the following details on the integration tile:
- Name of the integration with its build number
- The incoming data. In this example, 25 CIs and 1,572 events are received
- The name of the user who modified the integration along with the time of the modification. In this example, it is the admin user
- The Connector status. In this example, the status is Active

To validate the TrueSight Operations Management integration

Perform the following actions to validate the integration:

Ensure that the status of the integration is Connected. The following statuses are also valid:
- Configuring
- Disabled
- Disconnected
Go to BMC Helix Operations Management > Events to ensure that you can see events in BMC Helix Operations Management.
For more information, see Event monitoring .
Business service data: In BMC Helix AIOps > Entities to view business services.
For more information, see Monitoring services.

TrueSight Operations Management event slot mapping

Event slots in TrueSight Operations Management	Corresponding event slots in BMC Helix Operations Management
`event_handle`	`_handle`
`mc_ueid`	`_identifier`
`mc_host_address`	`source_address`
`mc_host`	`source_hostname`
`mc_location`	`location`
`TSOM,<integration_ID>,mc_host`	`source_identifier`
`mc_object`	`object`
`mc_object_class`	`object_class`
`pn_object_id`	`object_id`
`mc_event_category`	`category`
`mc_event_subcategory`	`sub_category`
`date_reception`	`creation_time`
`mc_priority`	`priority`
`mc_long_msg`	`details`
`mc_owner`	`user_assigned`
`repeat_count`	`_repeat_count`
`mc_notes`	`_notes`
`mc_operations`	`_operations`
`mc_smc_id`	`_ci_id`
`mc_smc_alias`	`alias`
`mc_object_owner`	`_tenant_id`
`mc_using_organization`	`_tenant_name`
`mc_bad_slot_names`	`_badslot_names`
`mc_bad_slot_values`	`_badslot_values`
`mc_abstraction`	`_abstraction`
`mc_abstracted`	`_abstracted`
`mc_associations`	`_associations`
`mc_cause`	`_cause`
`mc_effects`	`_effects`
`mc_event_relations`	`_relations`
`mc_relation_source`	`_relation_source`
`mc_timeout`	`_timeout`
`p_agent`	`p_publish_hostname`
`pn_thresh_above`	`al_thresh_above`
`pn_baseline_type`	`al_baseline_type`
`pn_end_time`	`al_end_time`
`pn_last_time`	`al_last_time`
`pn_object_class_id`	`object_class`
`mc_parameter`	`al_parameter_name`
`mc_parameter_value`	`al_parameter_value`
`mc_parameter_unit`	`al_parameter_unit`
`pn_thresh_duration`	`al_thresh_duration`
`pn_thresh_id`	`al_thresh_id`
`pn_thresh_type`	`al_thresh_type`
`pn_extremeness`	`al_extremeness`
`pn_alarm_id`	`al_alarm_id`
`pn_highest_severity`	`al_highest_severity`
`pn_is_predicted`	`al_is_predicted`
`pn_old_severity`	`al_old_severity`
`pn_predict_to_occur_time`	`al_predict_to_occur_time`
`pn_predicted_severity`	`al_predicted_severity`
`pn_avg_value`	`al_avg_value`
`pn_baseline_daily_high`	`al_baseline_daily_high`
`pn_baseline_daily_low`	`al_baseline_daily_low`
`pn_baseline_hourly_high`	`al_baseline_hourly_high`
`pn_baseline_hourly_low`	`al_baseline_hourly_low`
`pn_baseline_weekly_high`	`al_baseline_weekly_high`
`pn_baseline_weekly_low`	`al_baseline_weekly_low`
`pn_event_score`	`al_event_score`
`pn_pts_exceeded`	`al_pts_exceeded`
`pn_pts_total`	`al_pts_total`
`mc_parameter_threshold`	`al_parameter_threshold`
`pn_device_name`	`al_agent_name`

TrueSight Operations Management enum mapping

Enums in TrueSight Operations Management	Corresponding values in BMC Helix Operations Management
`MC_EVENT_CATEGORY`	`CATEGORY`
`MC_PRIORITY`	`PRIORITY`
`MC_EVENT_SUBCATEGORY`	`SUB_CATEGORY`
`APM_APP_SEVERITY`	`SEVERITY`
`array`	`name`

Frequently asked questions on the TrueSight Operations Management integration

This section provides answers to frequently asked questions.

Why do I see a difference between the number of entities available in the third-party solution and the number of entities fetched in BMC Helix AIOps?

After the specified time interval, BMC Helix AIOps fetches all CIs and event data from the third-party products, even if the data is already fetched in the previous cycle. Therefore, the CIs and events fetched in BMC Helix AIOps appear to be more than the number of CIs and events present in the third-party product. This situation causes no impact on performance.

Why are event classes not created in BMC Helix AIOps?

Event classes might not be created because of an event slot conflict or because the enums in custom classes were not created. To resolve this issue, see Troubleshooting the TrueSight Operations Management integration.

Why can't I see events with read-only or internal slots in BMC Helix AIOps?

To view these events, you must add the read-only or internal slots to the event_slot_mapping.json file. For more information, see Troubleshooting the TrueSight Operations Management integration.

Are events from the TrueSight Infrastructure Management remote cell propagated to BMC Helix AIOps?

No. Events from the TrueSight Infrastructure Management remove cell are not propagated to BMC Helix AIOps.

Why are the TrueSight Infrastructure Management events missing if the integration was disabled for more than three days?

By default, the BMC Helix Intelligent Integrations collects the historical event data for the last three days (72 hours) only from TrueSight Infrastructure Management. If you disable the TrueSight Infrastructure Management integration and enable it after three days, the maximum historical event data collected is available only for the last three days. For example, If you disabled the integration on July 10th, enabled it on July 20th, you will see the historical data is from July 17th to July 20th only (for the last three days or 72 hours). Any historical event data before the last three days is not collected.