Bmchelix Exporter
contrib
Maintainers: @bertysentry, @NassimBtk, @MovieStoreGuy
Source: opentelemetry-collector-contrib
Supported Telemetry
Overview
This exporter supports sending metrics to BMC Helix Operations Management through its metric ingestion REST API.Getting Started
The following settings are required:endpoint: is the BMC Helix Portal URL of your environment, at onbmc.com for a BMC Helix SaaS tenant (e.g.,https://company.onbmc.com), or your own Helix Portal URL for an on-prem instance.api_key: API key to authenticate the exporter. Connect to BMC Helix Operations Management, go to the Administration > Repository page, and click on the Copy API Key button to get your API Key. Alternatively, it is recommended to create and use a dedicated authentication key for external integration.
Optional Settings
The following settings can be optionally configured:timeout: (default =10s) Timeout for requests made to the BMC Helix.enrich_metric_with_attributes: (default =true) When enabled, creates enriched metrics by appending datapoint attribute values to the metric name. This provides more detailed identification in BMC Helix Operations Management but increases metric cardinality. Set tofalseto reduce the number of unique metric series.retry_on_failuredetails hereenabled(default = true)initial_interval(default = 5s) Time to wait after the first failure before retrying; ignored ifenabledis false.max_interval(default = 30s) The upper bound on backoff; ignored ifenabledis false.max_elapsed_time(default = 300s) The maximum amount of time spent trying to send a batch; ignored ifenabledis false. If set to 0, the retries are never stopped.
Setting Required Attributes for Metrics
To ensure metrics are correctly populated in BMC Helix, the following attributes must be set either at the Resource level, or at the Metric level:entityName: Unique identifier for the entity. Used as display name ifinstanceNameis missing.entityTypeId: Type identifier for the entity.instanceName: Display name of the entity.
Note: IfTo ensure the necessary attributes are present, it is recommended to leverage the transform processor with OTTL, and include it in the configuration of the telemetry pipeline. The minimal pipeline most often looks like:entityNameorentityTypeIdis missing, the metric will not be exported.
OTEL metrics --> (memory limit) --> transform processor --> bmchelix exporter.
Transformer Example for Hardware Metrics
You can use the following OpenTelemetry Transformation Language (OTTL) configuration to map these attributes dynamically:Configuration
Example Configuration
Last generated: 2026-04-13