Skip to main content

Upgrade Notes

MetricsHub Enterprise​

Upgrading to v3.9.06​

New default error_mode for the filter and transform processors​

MetricsHub Enterprise v3.9.06 ships with version 0.158.0 of the OpenTelemetry Collector, in which the default error_mode of the filter processor and transform processor changed from propagate to ignore. Errors raised while evaluating filtering or transformation statements are now logged and ignored instead of being propagated up the pipeline.

If you configured a filter or transform processor in your otel-config.yaml file and rely on the previous behavior, explicitly set the error mode in the processor configuration:

processors:
  filter/example:
    error_mode: propagate
    # ...

Upgrading to v3.9.01​

Updating otel-config.yaml​

For seamless integration with BMC Helix, MetricsHub now natively enriches collected metrics with the required attributes, such as entityTypeId and entityName. As a result, configuring the transform processor with OTTL in the otel-config.yaml file is no longer necessary.

If you previously configured the BMC Helix integration, remove the transform processor from both the processors section and the metrics pipeline in your otel-config.yaml file to prevent conflicts.

Upgrading to v3.0.01​

Updating otel-config.yaml​

To guarantee the correct operation of MetricsHub Enterprise v3.0.01, you must replace the following service: section of your otel-config.yaml file:

service:
  telemetry:
    logs:
      level: info # Change to debug for more details
    metrics:
      address: localhost:8888
      level: basic

with this one:

service:
  telemetry:
    logs:
      level: info # Change to debug for more details
    metrics:
      level: basic
      readers:
        - pull:
            exporter:
              prometheus:
                host: '0.0.0.0'
                port: 8888

By default, the otel-config.yaml file is stored in:

  • /opt/metricshub/lib/otel/otel-config.yaml (Linux)
  • or C:\ProgramData\MetricsHub\otel\otel-config.yaml (Windows).

If you have any doubt, you can refer to the example files provided for the different operating systems:

  • /opt/metricshub/lib/otel/otel-config-example.yaml (Linux)
  • C:\Program Files\MetricsHub\otel\otel-config-example.yaml (Windows)

or download the latest otel-config-example.yaml example.

Upgrading to v2.0.00​

Support for multiple configuration files​

MetricsHub parses all the .yaml or .yml files with valid syntax found in the config/ directory, regardless of their names or intended purpose (e.g., resources-example.yaml, old-license.yaml).

To prevent configuration conflicts, duplicates, or unintended overrides:

  • Move backup or example files to a subfolder such as config/examples/ or config/backups/.
  • Disable unused files by renaming them with a non-YAML extension (e.g., .bak, .txt, or .disabled).
  • Regularly check the files stored in the config/ directory to ensure only intended configurations are loaded.