MetricsHub
MetricsHub Enterprise 1.0.01

Release Notes

MetricsHub Enterprise Edition v1.0.01

MetricsHub Enterprise Edition v1.0.01

Changes and Improvements

ID Description
M8BEE-29 Removed Otel collector resourcedetection processor to prevent localhost system resource attributes from being overridden
M8BEE-32 Moved the localhost resource configuration to the data center 1 resource group in metricshub-example.yaml

MetricsHub Enterprise Connectors v101

Changes and Improvements

ID Description
EC-9 The hw.network.bandwidth.limit metric is now reported in bytes

Fixed issues

ID Description
EC-73 Dell iDRAC9 (REST): Some network link physical addresses are incorrect

MetricsHub Community Edition v0.9.07

Changes and Improvements

ID Description
#433[1] [BREAKING_CHANGE] Disabled Automatic Hostname to FQDN resolution
#427[2] BMC Helix Integration: Added the `StatusInformation` internal text parameter to the connector monitor
#421[3] Reduced Alert noise for `hw.status{state=“present”}`
#414[4] Added a link to MetricsHub Community Connectors 1.0.06
#412[5] The `hw.status{state=“present”}` metric is no longer reported for cpu monitors discovered by Linux and Window connectors
#383[6] Implemented a new engine method `megaBit2Byte` to align with OpenTelemetry unit standards
#374[7] Default connector variables can now be specified in YAML connector files
#302[8] Defined `afterAll` and `beforeAll` jobs in YAML connectors
#423[9] Added the ability to filter monitors

Fixed issues

ID Description
#436[10] The log message for SNMP v3 credential validation is incorrect
#439[11] Connector default variables are not serializable
#417[12] JavaDoc references are incorrect
#410[13] Protocol definition is applied to only one host in a multiple-host configuration
#368[14] The `hw.power{hw.type=“vm”}` metric is erroneously set to 0
#456[15] An exception occurs when monitoring ESXi through vCenter authentication

MetricsHub Community Connectors v1.0.06

Changes and Improvements

ID Description
#125[16] Disabled automatic detection for WindowsProcess, WindowsService, and LinuxService
#122[17] Added default values for connector variables in `WindowsService`, `LinuxService`, `WindowsProcess` & `LinuxProcess`
#114[18] The `hw.network.bandwidth.limit` metric is now displayed in bytes

Fixed issues

ID Description
#120[19] The `hw.vm.power_ratio` unit is incorrect. It should be 1 instead of Cel
release notes monitoring observability opentelemetry otel
Links:
  • [1] https://github.com/sentrysoftware/metricshub/issues/433
  • [2] https://github.com/sentrysoftware/metricshub/issues/427
  • [3] https://github.com/sentrysoftware/metricshub/issues/421
  • [4] https://github.com/sentrysoftware/metricshub/issues/414
  • [5] https://github.com/sentrysoftware/metricshub/issues/412
  • [6] https://github.com/sentrysoftware/metricshub/issues/383
  • [7] https://github.com/sentrysoftware/metricshub/issues/374
  • [8] https://github.com/sentrysoftware/metricshub/issues/302
  • [9] https://github.com/sentrysoftware/metricshub/issues/423
  • [10] https://github.com/sentrysoftware/metricshub/issues/436
  • [11] https://github.com/sentrysoftware/metricshub/issues/439
  • [12] https://github.com/sentrysoftware/metricshub/issues/417
  • [13] https://github.com/sentrysoftware/metricshub/issues/410
  • [14] https://github.com/sentrysoftware/metricshub/issues/368
  • [15] https://github.com/sentrysoftware/metricshub/issues/456
  • [16] https://github.com/sentrysoftware/metricshub-community-connectors/issues/125
  • [17] https://github.com/sentrysoftware/metricshub-community-connectors/issues/122
  • [18] https://github.com/sentrysoftware/metricshub-community-connectors/issues/114
  • [19] https://github.com/sentrysoftware/metricshub-community-connectors/issues/120
No results.