Integrating with CA APM

Use the BMC Helix Intelligent Integrations CA Application Performance Management
(CA APM) connector to collect alerts, metrics, and topology data from CA APM, and
view the collected data in BMC Helix Operations Management and derive actionable
insights.

BMC Helix application	Type of data collected or viewed	Benefits
BMC Helix Operations Management	Events ( alerts received as events)	Use a centralized event view to monitor, filter, and manage events, and perform event operations in one place. Process events to help identify actionable events quickly from a large volume of event data. For more information, see Monitoring events and reducing event noise.
BMC Helix Operations Management	Metrics	Use alarm and variate policies to detect anomalies and eliminate false positives for more accurate results while monitoring the health of your system. For more information, see Detecting anomalies by using static and dynamic thresholds.
BMC Helix Discovery	Topology	Collect all CIs from CA APM as is in BMC Helix Discovery. Create services from the CIs collected from CA APM in BMC Helix Discovery in a format that can be consumed by BMC Helix AIOps. For more information, see Managing your IT infrastructure.
BMC Helix AIOps	Situations (created from events)	Improve the mean time to resolve (MTTR) based on the situation-driven workflow. Lower the mean time to detect or discover (MTTD) and the time required for investigating tickets. For more information, see Monitoring situations.
BMC Helix AIOps	Services (created from topology)	Monitor the overall health of a service. When the service gets impacted by any factor, view the events generated because of the impact, analyze the causes of the impact, and quickly remediate those events to restore the health of the impacted service. For more information, see Monitoring services.

Supported versions

BMC Helix Intelligent Integrations supports version 10.7 SP3 of CA APM for data collection.

Important
We do not certify later versions of CA APM because they are inaccessible.

Task 1: To plan for the connection

Depending on the location of the third-party product (SaaS, on-premises), choose one or more BMC Helix Intelligent Integrations deployment modes and review the corresponding port requirements. For information about various deployment modes and port requirements, see Deployment scenarios.
Based on the deployment mode, use the BMC Helix Intelligent Integrations SaaS deployment or the BMC Helix Intelligent Integrations on-premises gateway or both. For more information about the gateway, see Deploying the BMC Helix Intelligent Integrations on-premises gateway.
The on-premises gateway must be able to reach the third-party product on the required port (default is 8081).

In the preceding list, third-party product refers to CA APM.

Task 2: To configure the connection with CA APM

Depending on the deployment mode, perform one of the following steps to access BMC Helix Intelligent
Integrations:
- BMC Helix Intelligent Integrations SaaS – Log on to BMC Helix Portal, and click Launch on BMC Helix
  Intelligent Integrations.
- BMC Helix Intelligent Integrations on-premises gateway – Use the following URL to access BMC Helix
  Intelligent Integrations: https://<hostName>:<portNumber>/swpui
On the CONNECTORS tab, click in the SOURCES panel.
Click the CA APM tile.
Specify the following details for the source connection:
1. Specify a unique instance name.
  Best practice
  We recommend that you specify the instance name in the following format:
  <sourceType>_<sourceControllerServerName>{_<InstanceQualifier>}
  The instance qualifier helps you to distinguish the multiple instances configured from the same source server. For example, you can name your instances as CAAPM_Host_PROD, CAAPM, and so on.
2. Specify the CA APM host name.
3. Specify the CA HTTP or HTTPS port number depending on the connection protocol. The default port number is 8081.
4. Select the HTTPS option to use an https connection to the CA APM host. Select this option when the protocol is https.
5. Enter the user name and password for the CA APM host.
6. Enter the token.
  For more information about tokens, see APM REST API.
7. Click Proxy and specify if you want to configure a proxy server. If yes, specify the host name and port number (default value is 8888).
Click VALIDATE AND CREATE.
The specified connection details are validated and the corresponding source connection is created in the Source Connection list.
Select the source connection that you created from the list if it is not selected already.
Important
The destination host connection is created and configured automatically when the source connection is created.
Ensure that the options for the datatypes for which you want to collect data are selected.

Configure the collectors for the selected data types by clicking the respective data type in the Collectors section. Specify the parameters for the selected data type, as explained in the following table:

Important

In addition to the parameters described in the following table, you can use some other parameters to tailor the amount of data that you want to collect from CA APM. For more information, see Handling large data from CA APM.

The ✅️ symbol indicates that this field applies to the data type.

Parameter name	Description	Data Type
Parameter name	Description	CA APM Alerts	CA APM Metrics	CA APM Topology
Collection Schedule	Select one of the following options to specify the data collection frequency: Duration: When you select this option, data collection happens constantly. Specify the schedule in minutes, hours, or day. Default: 5 minutes Example: Collection Schedule is set to 5 mins. Current time is 00:30. If you run the collector just after 00:30, data is collected every 5 mins, first at 00:30 and next at 00:35, and so on. Cron schedule: When you select this option, data collection happens periodically. Specify the schedule by using a cron expression. A cron expression is a string consisting of five subexpressions (fields) that describe individual details of the schedule. These fields, separated by blank spaces, can contain any of the allowed values with various combinations of the allowed characters for that field. Default: /5 * * * (evaluates to 5 minutes) Format: Minutes *Hours (24-hour format)* Day of Month Month Day of Week** Example: If you specify 10 15 3 7 * , data is collected at 15:10 hours every third day in the month of July. For more information about how this parameter affects data collection, see Data collection schedule.	✅️	✅️	✅️
Data Collection Window	Specify the historical time period (in minutes) from the current time for which the data should be collected. Default: 5 minutes Example: Collection Schedule is set to 5 mins. Data Collection Window is set to 5 mins. Current time is 00:30. If you run the collector just after 00:30, data is collected first at 00:30 for the interval 00:25 - 00:30, and next at 00:35 for the interval 00:30 - 00:35, and so on. For more information about how this parameter affects data collection, see Data collection window.	✅️	❌️	❌️
Data Latency	Specify the time (in minutes) by which the data time window should be shifted back on the timeline. This parameter is useful in delayed data availability situations. Default: 0 minutes Example: Collection Schedule is set to 5 mins. Data Collection Window is set to 10 mins. Data Latency is set to 2 mins. Current time is 00:30. If you run the collector just after 00:30, data is collected first at 00:30 for the interval 00:18 to 00:28 and next at 00:35 for the interval 0:23 to 00:33, and so on. For more information about how this parameter affects data collection, see Data latency.	✅️	✅️	❌️
Extract alerts for agents	Select one or more agents for which you want to collect alerts.	✅️	❌️	❌️
Host Regex	Specify a regular expression for hosts. Alerts from the hosts that match the regular expression are collected. For example, if you specify -pun as the regular expression, alerts are collected from the following hosts: austin-pun, hou-pun	✅️	❌️	❌️
Severity	Select one or more severity levels from the following list: Caution Danger No Data Ok This list of severities is updated automatically from CA APM.	✅️	❌️	❌️
Extract metrics from these hosts	Select one or more hosts from the list from which you want to collect metrics. This list of metrics is updated automatically from CA APM.	❌️	✅️	❌️
Agents, Host Regex	Specify a regular expression for agents, hosts, or a \| (pipe)-separated regular expression for extracting data from both agents and hosts. Metrics from the agents and hosts that match the regular expression are collected. Examples: Only for agents: If you specify .dotNet., metrics from all agents containing dotNet in their names are collected for all the hosts. Only for hosts: If you specify .clm.\|.. , metrics from all hosts containing clm* in their names and all their agents are collected. Both agents and hosts: If you specify . clm.\|.dotNet. , metrics from all hosts containing clm in their names and their agents containing dotNet in their names are collected. Note: If you have selected a set of hosts from the Extract metrics from these hosts field and specified a regular expression in this field, metrics are collected from the hosts that are selected from the field and the hosts that match the regular expression.	❌️	✅️	❌️
Metrics Regex	Specify a regular expression for metrics. The metrics that match this regular expression are collected. The regular expression must end in question mark (?). For example, if you specify Available Threads.\|.Bytes In Use? in this field, the data is collected for the Available Threads and Bytes In Use metrics.	❌️	✅️	❌️
Layers	Select one or more CA APM layers for which you want to extract data. This list of metrics is updated automatically from CA APM.	❌️	❌️	✅️

Click CREATE COLLECTORS to create the required collector streams for the selected data types.

Configure the distributors for the selected data types by clicking the respective data type in the Distributors section. Specify the parameters for the selected data type, as explained in the following table:

Parameter name	Description
Max Batching Size	Specify the maximum number of data items to send in a single POST request to the destination API. The batch size depends on the destination’s ability to buffer the incoming data. Default: 250
Max Batching Delay	Specify the maximum time (in seconds) to wait before building and processing a batch. Default: 3 seconds
Base Retry Delay	Specify the initial time (in seconds) for which to wait before retrying to build and process a batch. The waiting time increases in the following sequence: n¹, n², n³, and so on, where n indicates the number of seconds. Default: 2 seconds Example: Base Retry Delay is set to 2 seconds. Retry is performed after 2, 4, 8, 16, ... seconds.
Max Intra-Retry Delay	Specify the maximum limit for the base retry delay. Default: 60 seconds Example: Max Intra-Retry Delay is set to 60 seconds. Base Retry Delay is set to 2 seconds. Retries are performed 2, 4, 8, 16, 32,... seconds later.
Max Retry Duration	Specify the total time for retrying a delivery. For REST destinations, a delivery is a batch of data items in one POST request. Default: 5 minutes Example: Max Retry Duration is set to 8 hours. Base Retry Delay is set to 2 seconds. Requests are sent for 2+4+8+16+32+64+132... until 8 hours in total duration is reached. After that, no subsequent attempts are made to retry the delivery. The assumption here is that if there is an outage or other issue with the destination tool, recovery should take less than the value of the Max Retry Duration parameter to be completed.
Attributes To Be Dropped When Updating Events	Specify the event attributes that you do not want to be updated in BMC Helix Operations Management when events are updated. For example, if you do not want an event's severity, source address, source category, and subcategory to be updated in BMC Helix Operations Management, you need to specify those attributes in a comma-separated format: severity,source_address,source_category,source_subcategory. Important: You can obtain the event attribute names in BMC Helix Operations Management, by exporting any event data in JSON, BAROC, XML, or CSV format. The exported file contains all attributes of the event data, and from there you can identify the attributes to be dropped.

Click CREATE DISTRIBUTORS to create the required distributor streams for the selected data types.
Click one of the following buttons:
- SAVE STREAM: Click this button if you want to edit the integration details before creating the instance. After you save the stream, the connector that you just created is listed in the SOURCES panel. Move the slider to the right to start the data stream.
- SAVE AND START STREAM: Click this button if you want to save the integration details and start receiving data immediately.

Important
For a data stream, the Run Latency (max/avg), Items (Avg per Run), and Last Run Status columns on the
Streams page might show the status as No Runs during the data collection process. After completion of
the process, these columns are updated with an appropriate status.

For more information about the data streams, see Starting-or-stopping-data-streams.

Task 3: To verify the connection

In CA APM, on the SOURCES panel, confirm that the data streams for the connection you created are running. Data streaming is indicated by moving colored arrows.

A moving dark blue arrow ( ) indicates that the event stream is running. Event data will be pushed according to the configured Collection Schedule interval.
A moving red arrow ( ) indicates that the metric stream is running. Metric data will be pushed according to the configured Collection Schedule interval.
A moving light blue arrow () indicates that the topology stream is running. Topology data will be pushed according to the configured Collection Schedule interval.

To view data in BMC Helix applications

View data collected from CA APM in multiple BMC Helix applications.

View data collected from Prometheus in multiple BMC Helix applications.

To view events in BMC Helix Operations Management

In CA APM, select Monitoring > Events.
Filter the events by the CA_APM_Alert class.

Incoming events from CA APM are processed in BMC Helix Operations Management through a set of deduplication rules to determine whether the incoming event is a duplicate event or a new event. For more information, see Event-deduplication-suppression-and-closure-for-reducing-event-noise.

For more information about events, see Monitoring and managing events.

To view metrics in BMC Helix Operations Management

In BMC Helix Operations Management, select Monitoring > Devices.
Click the link for the required device.
On the Monitors tab, click the required monitor.
The Performance Overview tab shows the metrics graph.

For information about metrics, see Viewing collected data.

BMC Helix Intelligent Integrations identifies all the CA APM KPI metrics. All the KPI metrics are prefixed with KPI in BMC Helix Operations Management. You can use these metrics for baselining.

Click here to view the list of KPI metrics

ConnectionStatus
Historical Metric Count
IsClamped
Metric Count
Raw Metric Count
Transaction Tracing Events Per Interval
Transaction Tracing Events Limit Exceeded
Error Snapshot Events Per Interval
Error Snapshot Events Limit Exceeded
Metrics Appended To Query Per Interval
Metrics Converted From Spool to Query Per Interval
SmartStor Disk Usage (mb)
Agent Metric Cache Size
Cached Metric Count
Items Iterated Per Interval
Items Matched Per Interval
Metrics Created Per Interval
Metrics Received from DB Per Interval
Sort Duration (ms)
Converting Spool To Data
Data Append
Reperiodizing
Number of Dropped Per Interval
Number of Inserts Per Interval
Number of Queries Per Interval
Number of Traces in Database
Number of Traces in Insert Queue
TT Database Disk usage (mb)
Total Data Insertion Duration Per Interval (ms)
Total Index Insertion Duration Per Interval (ms)
Total Query Duration Per Interval (ms)
Baseline Volume Free (mb)
Log Volume Free (mb)
SmartStor Archive Volume Free (mb)
Traces Volume Free (mb)
Metric Data Points Sent per Interval
Queued Metric Data Points
CPU Capacity (%)
GC Capacity (%)
Harvest Capacity (%)
Heap Capacity (%)
Incoming Data Capacity (%)
SmartStor Capacity (%)
Number of Connection Tickets
Number of Dependent Calculator Input Metrics
Number of Non Dependent Calculator Input Metrics
Number of metric Data Queries per Interval
Number of Queued Async Data Queries
Number of Registered Async Data Queries
Number of Registered Async MG Queries
Number of Registered Async Path Queries
Number of Transaction Trace Action Sessions
Number of Transaction Trace Session Clients
Number of Virtual Metrics
AlertID
Query memory in transit (bytes)
Agent Connection Status
Number of Evaluated Metrics
Backend Heuristics
Browser Heuristics
CPU Heuristic
Console Summary Alert
Frontend Errors Heuristic
Frontend Heuristics
Frontend Response Time Heuristic
JDBC Heuristic
JMS Heuristics
JVM Heuristics
Thread Pool Heuristic
Total Number of Evaluated Metrics
Total Number of Evaluated Metrics
<calculator name>
Count Per Interval
GC Duration (ms)
Pools
Alert Action Processing Time (ms)
Calculator Queries Wait Time (ms)
Non Calculator Queries Delivery Time (ms)
Non Calculator Queries Excess Time (ms)
Metrics From All Agents
Spooling Data File Write Time (ms)
Spooling Preparation Time (ms)
Active Incoming Threads
Active Outgoing Threads
Corrupted Messages Per Interval
Number of Mailboxes
Queued Messages
Metric Matches Per Interval
Queued Queries Per Interval
Cache Queries Duration (ms)
Cache Queries Per Interval
SmartStor Queries Duration (ms)
SmartStor Queries Per Interval
Blocked Count
Blocked Time (ms)
CPU Time (ms)
User Time (ms)
Wait Count
Wait Time (ms)
Warning Count
Harvest Duration (ms)
SmartStor Duration (ms)
Harvest Capacity
Harvest Duration
Collector Metrics Received Per Interval
Skew Time (ms)
Collector Number of Async Queries per Interval
Collector Async Queries Duration (ms)
Collector Number of Sync Queries per Interval
Collector Sync Queries Duration (ms)
Collector Number of Sync Queries by CLW per Interval
EM Live Metric Clamped
EM Historical Metric Clamped
Max Number of Agent Connection Limit Exceeded Per Interval
Number of Events Processed
Number of Events Processed Limit Exceeded
Number of Collector Metrics
Data Points Retrieved From Disk Per Interval
Data Points Returned Per Interval
Metrics Read From Disk Per Interval
Metrics Returned Per Interval
Queries Exceeding Max Data Points Read From Disk Limit Per Interval
Queries Exceeding Max Data Points Returned Limit Per Interval
Converting Spool to Data Metric
Overall Capacity (%) Metric
SmartStor Capacity (%) Metric
Heap Capacity (%) Metric
Write Duration (ms) Metric
Number of Agents Metric
Number of Metrics
Historical Metric Count Metric
Number of Historical Metrics
AT Events Received Per Interval
AT Stories Created Per Interval
Average Process Time of Simple Alert Status Changes
Average Process Time of Topology Changes
Average Process Time Of UVB Variance Intensity Changes
Average Processing Time of AT Editor
Average Processing Time of AT Story Controller
Average Response Time of Graph Rest Call
AWS S3 4xx Errors
Percent Authorization Error
Percent Network Error
Percent Server Other Error
Percent Throttling Error
Percent Timeout Error
CPU Percentage
DTU Percentage
Failed Connections
Failed Requests
Internal Server Errors
Other Errors
Server Busy Errors
Percentage Used
Percentage CPU Usage
HTTP ERROR
HTTP Server Error
Calculator Harvest Time
GC Duration
Ping Time
Skew Time
CPU Core Util Percent
CPU Total Util Percent
Database Average Response Time
Database Edge Count
Disk Usages Percentage
EM CPU Used
Memory In Use Percent
Number of Active Workers
Processing Queue Size of AT Contextualizer
Smartstor Duration
Swap In Use Percent
Total Active Container Count
All Web Server Availability Status
Apache Availability Status
Apache Current Number Of Idle Workers
Apache Current Percentage CPU Load
Apache Requests Per Interval
Microsoft IIS Availability Status
Microsoft IIS GET Requests Per Interval
Microsoft IIS Locked Errors Per Interval
Microsoft IIS POST Requests Per Interval
Microsoft IIS Total Bytes Transfered Per Interval
Application Errors
AWS Status Value
Backend Errors
Browser Page Errors
Browser Page Load Time
CPU Utilization
Docker Agent Connection Status
Docker Container Ready State
Docker Status Value
Expressjs Errors
Frontend Errors
Frontend Stalls
Heap Used Percent
JMS Consumer Errors
JMS Consumer Stalls
JMS Producer Errors
Memory Utilization
MVC Controller Errors
Dropped Packets
Errors
Pod Status
Response Time Variance Intensity
Servlet Errors
Servlet Stalls
Spring Controller Errors
Spring Service Errors
Struts2 Action Errors
Test Alert
Transaction Errors
WebAPI Controller Errors
WebService Client Errors
WebService Server Errors
Rule Failures
Total 4xx Response
Backend Tier Risks
CPU Tier Risks
Memory Tier Risks
TibcoBW6 Process Errors Per Interval
TibcoBW6 Process Stall Count
Caution Alerts
Caution Triage Map Alerts
Danger Alerts
Danger Triage Map Alerts
Normal Alerts
Normal Triage Map Alerts
Total Alerts
Total Triage Map Alerts
Number of Active Windows
Number of Active Workers
Number of Backend Call Alerts Run in Summary Metric Calculators
Number of BTC Alerts Run in Summary Metric Calculators
Number of Frontend Alerts Run in Summary Metric Calculators
Number of Idle Workers
Historical cache loading time in ms
Historical snapshots
Historical total weight
Average Response Time (ms)
Concurrent Invocations
Edge Count
Errors Per Interval
History Size
Responses Per Interval
Stall Count
Vertex Count
Average Decoration Time (ms)
Average Process Time (ms)
Events Clamped
Events Per Interval
Events Ignored
Events Per Interval
AT cache call duration in ms
AT cache snapshots
Cached agents
Cached agents data points
Cached entry-points
Cached entry-points data points
Context cache call duration in ms
Context cache weight
Experience chart build duration in ms
Experience chart snapshots
Refresh time duration in ms
Datapoints Per Interval
Number of agents
Number of metrics
Number of metrics clamped per interval
Request Duration (ms)
Aggregated Edge Changes Produced
Aggregated Status Changes Produced
Edge Changes Processed
Edges To Store Queue
Graphs To Process Queue
Model Graphs Clamped
Status Changes Processed
Status Changes To Database Clamped
Status Changes To Database Queue Size
Notifications currently queued
Notifications sent per interval
Unclassified Errors Per Interval
Average AppMap Time Per Interval (ms)
Edges Served Per Interval
Full invocations Per Interval
Incremental invocations Per Interval
Vertices Served Per Interval
Average Response Time Per Interval (ms)
Invocations Per Interval
Responses Per Interval
Alerts Served Per Interval
Average DAO Time Per Interval (ms)
Average Lucene Time Per Interval (ms)
Index Updating Tasks In Queue Count
Index Writer Docs Count
Index Writer RAM Size (KB)
NRTCachingDirectory Size (KB)
Processed Changes Per Interval
Submitted Changes Per Interval
Submitted Searches Per Interval
Alert Snapshot Components Processed
Alert Snapshots Clamped
Alert Snapshots Processed
Status Changes Produced
Timeslice Metrics Skipped (Long Name)
Timeslice ResultSet Metrics Processed
Timeslice ResultSets Clamped
Timeslice ResultSets Processed
Discarded Graphs
Discarded Traces
Edges Created
Fast Transactions Processed
Filtered Traces
Mapped Traces
Mapping Usage (%)
Number of Attributes in Correlation Buffer
Number of Correlation Keys in Correlation Buffer
Number of Edges in Correlation Buffer
Number of Graphs in Correlation Buffer
Number of Transactions in Correlation Buffer
Number of Vertices in Correlation Buffer
Processing Usage (%)
Slow Transactions Processed
Slow Transactions Processed Because Queue Full
Uncorrelated Transaction Processed
Ignored Contexts Per Interval
Timedout Per Interval
Current Ignored Vertices
Average Story Id Retrieval Time (ms)
Rejected Contexts Per Interval
Reporter Processing Queue Size
DB Persist Time (ms)
Total Metrics Baselined (count)
Current Size
Hit Count
Miss Count
Total Capacity
Processed
Processing Time(ms)
Processing Delay(ms)
Rejected
Geo Processing Time(ms)
Number of Map Entity Metric Groupings
Bytes Sent Per Interval
Clamped Connections Per Interval
Smarstor Data Volume Free (mb)
In Use (mb)
In Use Post GC (mb)
Total (mb)
Calculator Harvest Time (ms)
Number of Calculator-generated Metrics
Number of Calculators
Total Async Query Duration (ms)
Total Async Query Wait Duration (ms)
Total Sync Query Duration (ms)
Azure - Blob Storage - Percent Authorization Error
Azure - Blob Storage - Percent Network Error
Azure - Blob Storage - Percent Server Other Error
Azure - Blob Storage - Percent Throttling Error
Azure - Blob Storage - Percent Timeout Error
Azure - Database - CPU Percentage
Azure - Database - DTU Percentage
Azure - Database - Failed Connections
Azure - Event Hub - Failed Requests
Azure - Event Hub - Internal Server Errors
Azure - Event Hub - Other Errors
Azure - Event Hub - Server Busy Errors
Azure - File Storage - Percent Authorization Error
Azure - File Storage - Percent Network Error
Azure - File Storage - Percent Server Other Error
Azure - File Storage - Percent Throttling Error
Azure - File Storage - Percent Timeout Error
Azure - Queue Storage - Percent Authorization Error
Azure - Queue Storage - Percent Network Error
Azure - Queue Storage - Percent Server Other Error
Azure - Queue Storage - Percent Throttling Error
Azure - Queue Storage - Percent Timeout Error
Azure - Service Bus - Queues - Percentage Used
Azure - Service Bus - Topics - Percentage Used
Azure - Table Storage - Percent Authorization Error
Azure - Table Storage - Percent Network Error
Azure - Table Storage - Percent Server Other Error
Azure - Table Storage - Percent Throttling Error
Azure - Table Storage - Percent Timeout Error
Azure - VM - Percentage CPU Usage
Azure App Service - HTTP ERROR
Azure App Service - HTTP Server Error
Collector - GC Duration
Collector - Ping Time
Collector - Skew Time
Database Average Response Time
Disk Usages Percentage
Memory In Use Percent
MOM - Collector Metrics Received Per Interval
MOM - GC Duration
Apache Availability Status
Apache Current Percentage CPU Load
Microsoft IIS POST Requests Per Interval
Network - Dropped Packets
Network - Errors
Pod Status
WebService Client Errors
WebService Server Errors
Total 4xx Response
Total Number of Evaluated Metrics
Estimated Seconds Left
Procesed Records Total
Processed Records Per Interval
Remaining Percents
numBusyConnections
numConnections
numIdleConnections
numUnclosedOrphanedConnections
threadPoolNumTasksPending
Collection Count Per Interval
GC Duration (ms)
Committed (mb)
Max Available (mb)
Bytes Received Per Interval
Delivery Suspended Per Interval
Input Buffers Allocated
Messages Received Per Interval
Messages Sent Per Interval
Output Buffers Allocated
Messages Delivered Per Interval
Metric Matches Per Interval
DOI API Average Response Time
DOI API Calls Per Interval
Errors While Posting Alerts Per Interval
Ingested Alerts Per Interval
Number of Alerts
Number of Collectors
Number of Dashboards
Number of Management Modules
Number of Processors
Number of Providers
Number of Universes
Requests Per Interval
Served Per Interval
Errors Serving Vertices From Database Per Interval
Number of Vertices Not Found in Cache per Interval
Number of Vertices Served From Database per Interval
Requests With Vertices Not Found in Cache per Interval
Requests With Vertices Served From Database per Interval
Incoming Query Requests Per Interval
Outgoing Traces Served Per Interval
Query Average Request Response Time (ms)
Query Errors Found Per Interval
Query Requests With No Traces Found Per Interval
Overall Capacity (%)
EM CPU Used (%)
Agent Clusters Metric Load
Number of Agent Clusters
Number of Metric Groupings
Cross-Cluster Data Viewer Clamped metric
Disallowed Agents Clamped metric
Max Number of Agent Connection Limit Exceeded Per Interval metric
Metrics From External Agents
Metrics Queued (%)
Number of Applications
Number of Cross-Cluster Data Viewers
Number of Disallowed Agents
Number of Events Processed
Number of Metrics Handled
Number of Unique Applications
Number of Workstations

To view topology in BMC Helix Discovery

In BMC Helix Discovery, select Explore > Data.
In the search box at the top-right corner, search for the CA APM host name.
Click External Elements.
Click the entity name to view its topology.

The following figures show the topology for the dotNetPaymentBackend service in the CA APM UI and in the BMC Helix Discovery UI:

Viewing Situations in BMC Helix AIOps

Before you view situations in BMC Helix AIOps, ensure that the following prerequisites are met:

CIs are present in BMC Helix Discovery or BMC Helix AIOps for the events that are being collected from the Splunk Enterprise report.
Create a Business Service model in one of the following applications:
- BMC Helix Discovery. For more information, see Managing models.
- BMC Helix AIOps. For more information, see Creating service models.
Perform one of the following tasks:
- To view ML-based situations, the AIOps Situations feature is enabled in BMC Helix AIOps. For more information, see Enabling the AIOps features.
- To view policy-based situations, the correlation policy is created in BMC Helix Operations Management. For more information, see Creating and enabling event policies.

To view Situations

In BMC Helix AIOps, go to the Situations page.
This page shows the Situations created from the events that are ingested into BMC Helix Operations Management.
Click the required Situation to view the messages contained in the Situation and other details such as priority and severity of the message.

For information about Situations, see Monitoring situations.

Viewing services in BMC Helix AIOps

Before you view a service in BMC Helix AIOps, create a service model (for example, BackEnd_Model) for the dotNetPaymentBackend topology collected in BMC Helix Discovery. For instructions, see Managing models.

To view services in BMC Helix AIOps

In BMC Helix AIOps, go to the Services page.
This page shows the business service for the BackEnd_Model business service model.
To view the impact on the service, hover over the service.
The impact score in percentage and Situations, events, incidents, or configuration items (CIs) associated with a service are displayed.
Click the service to view the health summary, causal analysis, health insights, and other key metrics of interest.

For more information about services, see Monitoring services.

Handling large data from CA APM

Use the hostGroupingCount parameter to handle large data coming from CA APM and avoid errors such as the data collection API not responding properly. Divide CA APM hosts into groups by using this parameter. The number of hosts in each group is equal to the value that you specify for this parameter.

The CA APM connector fetches data for one group of hosts first and then for another group until all the groups are processed.

For example, if there are 10 hosts in CA APM and you set this parameter value to 5, the connector fetches data for the first group of 5 hosts and then for the next group of 5 hosts.

To edit the hostGroupingCount parameter:

Click Configure Mediator adjacent to CA APM .
Expand the CA APM section.
Enable the Edit JSON option.
You can see the JSON format of CA APM configuration parameters.
Edit the value of the hostGroupingCount parameter as required.
The default value for this parameter is 5, the minimum value is 1, and the maximum value is 100,000.
Click VALIDATE to validate the settings.
Click SAVE & CLOSE.

Marking devices for deletion in BMC Helix Operations Management

If the devices in BMC Helix Operations Management are not collecting any metrics data for a particular time period, you can mark them for deletion by using the shouldSupportTopologyLifecycle and itemExpiryDuration parameters.

For example, if you want to mark devices for deletion that do collect any metrics data in 5 hours in BMC Helix Operations Management, set the shouldSupportTopologyLifecycle parameter to true and set the value of itemExpiryDuration parameter to 5 hours.