24.4 enhancements and patches

Use slot placeholders while importing .csv in advanced enrichment policies

When you import data from a .csv file to create an advanced enrichment policy, you can add dynamic slot values in the Lookup data table slots by using slot placeholders (%<slotName>%).

With this enhancement, you do not have to manually add values for the Lookup data table slots in the .csv file. For example, instead of adding the host name, you can add the %source_hostname% placeholder. The host name is automatically resolved when the data is imported in BMC Helix Operations Management.

For more information, see Actions-for-advanced-and-time-based-enrichment.

View the current date and time for exported events

When events exported from BMC Helix Operations Management are ingested again, the timestamp slots use the current date and time for ingestion. The ingested date and time appear in the format that you configured in your user preferences.

For more information, see Exporting-events.

Search policies regardless of the character case

Use any character case in the search query while searching for event policies. This feature gives you more flexibility in searching for policies by not restricting the search query to search according to the character case.

For more information, see Creating-and-enabling-event-policies.

Run automation on closed events

The Trigger Automation option is available for closed events in addition to open events. Automations on events are useful when you perform probable cause analysis in BMC Helix AIOps.

For more information, see Performing-event-operations.

Eliminate false alarms by using poll counts

Use poll counts in alarm policies to eliminate false alarms that do not indicate a real problem. Alarm duration might not be an accurate indicator for a threshold breach. To avoid such false alarms use the polls count when you configure an alarm. 

For more information, see the following topics:

• Alarm-policies
• Constructing-alarm-generation-conditions
• Alarm-policy-management-endpoints-in-the-REST-API

Close autoanomaly events manually

Use the Close Event option on the Events page and the POST/events/operations/close endpoint to manually close autoanomaly events in addition to other events. This feature helps you conveniently clean up nonactionable autoanomaly events without waiting for the system pruning cycle of 90 days to close them.

For more information, see the following topics:

• Performing-event-operations
• Event-management-endpoints-in-the-REST-API

Filter Agents for monitoring solutions and monitoring solution versions

Use the Monitoring Solution Name and Monitoring Solution Version options to filter PATROL Agents. By using these options, you can quickly and efficiently search for specific PATROL Agents with refined results.

For more information, see Viewing-and-filtering-Agents.

Update custom slots for closed events

Use the Modify Event option on the Events page and the PATCH/events endpoint to update custom slots for closed events. This feature helps you update closed events through custom slots to record actions taken on events.

For more information, see the following topics:

• Performing-event-operations
• Event-management-endpoints-in-the-REST-API

Search events regardless of character case

The global search on the Events page is case-insensitive, giving you the flexibility to use any character case in the search query to search for events.

For more information, see Filtering-events.

Updated the UI to remove the information icon from the policy configuration summary text

On the Create Event Policy page, the information icon in the policy configuration summary text has been removed for the advanced and dynamic enrichment policy configurations.