bmchelix-enrich-metric-names.yaml

# Use this changelog template to create an entry for release notes.

# One of 'breaking', 'deprecation', 'new_component', 'enhancement', 'bug_fix'
change_type: enhancement

# The name of the component, or a single word describing the area of concern, (e.g. receiver/filelog)
component: exporter/bmchelix

# A brief description of the change.  Surround your text with quotes ("") if it needs to start with a backtick (`).
note: Enrich metric names with datapoint attributes for unique identification in BMC Helix Operations Management

# Mandatory: One or more tracking issues related to the change. You can use the PR number here if no issue exists.
issues: [46558]

# (Optional) One or more lines of additional information to render under the primary note.
# These lines will be padded with 2 spaces and then inserted directly into the document.
# Use pipe (|) for multiline entries.
subtext: |
  This feature is controlled by the `enrich_metric_with_attributes` configuration option (default: `true`).
  Set to `false` to disable enrichment and reduce metric cardinality.
  Normalization is applied to ensure BHOM compatibility:
  - `entityTypeId` and `entityName`: Invalid characters replaced with underscores (colons not allowed as they are used as separators in entityId)
  - `metricName`: Normalized to match pattern `[a-zA-Z_:.][a-zA-Z0-9_:.]*`
  - Label values: Commas replaced with whitespaces

# If your change doesn't affect end users or the exported elements of any package,
# you should instead start your pull request title with [chore] or use the "Skip Changelog" label.
# Optional: The change log or logs in which this entry should be included.
# e.g. '[user]' or '[user, api]'
# Include 'user' if the change is relevant to end users.
# Include 'api' if there is a change to a library API.
# Default: '[user]'
change_logs: []