This documentation supports an earlier version of BMC Helix Operations Management.To view the documentation for the latest version, select 23.3 from the Product version picker.

23.1 enhancements and patches


Review the BMC Helix Operations Management enhancements and patches for features that will benefit your organization and to understand changes that might impact your users.


For a list of recent updates and enhancements across multiple versions, see Release-notes-and-notices.

BMC applies upgrades as described in BMC Helix Upgrade policy. BMC applies upgrades and patches during Maintenance windows.

Related topics





23.1.02


Audit the user activities performed on alarm policies in BMC Helix Dashboards

As an administrator, use BMC Helix Audit Dashboard in BMC Helix Dashboards to track and monitor the activities performed on all alarm policies.

For more information, see the following topics:

audit_trail_dashboard.png


Use rotating API keys for secure data streaming

Use rotating API keys instead of a static API key in BMC Helix Operations Management to ensure that the metric, event, and log ingestion from PATROL Agents is more secure.

For more information, see Using-rotating-API-keys-for-secure-data-streaming.


Perform conditional event enrichment based on the time frame status

Perform conditional event enrichment based on the time frame status. Use the IsActiveTimeFrame function in advanced enrichment policies to enrich events based on whether or not a time frame is currently active.

For more information, see the following topics:


Store large values in event slots

Store large values in event slots by using the Long data type. Use this data type to store event slot values that do not fit in the Integer data type and to ensure that the devices that are associated with large event values run optimally.

For more information, see Slot-data-types.


Specify a dynamic delay in time-based policies

Use the Timeout action in time-based policies to specify a dynamic delay to see if an event remains open, and raise the event severity to notify an escalation to operators. Select the slot value of an incoming event as the duration after which the policy is executed. Previously, you could specify only a static delay.

For more information, see the following topics:


Copy event details from the events view

Copy details of an event from the events view on the Events page. This process saves navigation time to the Event details page to copy the event details.

Copy event details from the events view.png

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


Filter attributes to restrict data collection

Restrict data collection from your environment by filtering attributes so that you can limit the amount of collected data to make it easier to focus on the data that you are interested in. You can filter attributes without creating or updating any monitor policies.

For more information, see Restricting-data-collection-for-monitor-attributes.


23.1.01


Eliminate manual payload creation for event ingestion

Eliminate creating the payload for event ingestion manually by exporting events in the JSON format and ingesting them in BMC Helix Operations Management by using the event ingestion API.

For more information, see the following topics:


Navigate securely to the Event Details page

Securely navigate to the Event Details page of an event on any tenant by using the Event Details page URL. Use the ToBase64 function in advanced enrichment policies to convert a string to a Base64 value. For example, encode the event ID to a Base64 value by using the ToBase64 function.

For more information, see the following topics:


View an event timestamp in a specific date format

Use the ToFormattedTimeStamp function to view the epoch timestamp details of an event in a specific date format for better readability of timestamp values.

For more information, see Return-functions.


23.1.00


The following video (2:22) provides a high-level summary of the new features and enhancements in version 23.1 of BMC Helix Operations Management.

icon-play@2x.pnghttps://youtu.be/uB7tidKB4Sw

Use the same policy configurations across classes

Specify multiple classes in the event selection criteria of a single event policy to use the same policy configurations across different classes.

For more information, see the following topics:


REST API for deleting custom event slots

Use the PATCH/events/classes endpoint to delete custom event slots of out-the-box-classes. Previously, you could use this endpoint to delete custom slots of only custom classes.

For more information, see the following topics:


Configure a schedule for event policies

Schedule event policies to run at a specific time by using time frames. You can also use REST APIs to manage time frames. 

Event policy time frame.png

For more information, see the following topics:


Notes to indicate alarm event closure

On the Event Details page in BMC Helix Operations Management, view the reason for alarm event closure on the Logs and Notes tab when an entity or a PATROL Agent is deleted.

Logs and notes on entity deletion.png

For more information, see the following topics:


Simplified service blueprint creation process

The service blueprint creation process is simplified.

When you create a service blueprint from an available CI, BMC Helix AIOps does the following:

  • Creates the service blueprint without any errors.
  • Defines the filter criterion by default for the start node.
  • Automatically re-computes the blueprint if you assign another CI node as the start node. You don’t have to establish the relationships between nodes manually.

When you create a service blueprint from an available CI kind, BMC Helix AIOps defines the filter criterion by default for the first node.

For more information, see Modeling service blueprints.


View propagated health score for services

The health of a parent service is dependent on the health of other dependent services. If a dependent service is impacted, its health score is propagated to all services dependent on the parent service. Even if a parent service is not impacted directly and has no events, the service severity and the health score shows the propagated impact from a dependent service. If more than one dependent service is impacted, the lowest health score is displayed.

If the parent service is not impacted and the health score is propagated from a dependent service, a (Propagated) label is displayed right next to the health score.

On the Services page in the tile view, Impacted Entities shows the count of the impacted dependent services.

For more information, see Monitoring services

Services Page_HeatMap_Propagated_BHOM.png


 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*