### MetricsHub
MetricsHub 1.0.00

Home
- Introduction

# Release Notes

## MetricsHub Enterprise Edition v1.1.00

#### What's New

ID | Description
--- | ---
M8BEE-37 | Added protocol CLIs to validate configurations, troubleshoot connectivity, and ensure successful metric extraction

#### Changes and Improvements

ID | Description
--- | ---
M8BEE-38 | Updated OpenTelemetry Collector Contrib to version 0.116.0

### MetricsHub Enterprise Connectors v103

#### What's New

ID | Description
--- | ---
EC-72 | Added performance and capacity metrics for Pure Storage FlashArray storage systems via REST API
EC-75 | Added performance and capacity metrics for NetApp FAS and AFF storage systems via ONTAP REST API
EC-86 | Added support for Citrix NetScaler via SNMP

#### Changes and Improvements

ID | Description
--- | ---
EC-10 | Enhanced detection criteria in the `EMC VPLEX Version 5`, `EMC VPLEX Version 6`, and `Huawei OceanStor (REST)` connectors
EC-57 | Pure Storage FA Series (REST Token Authentication): NVRAM modules are now reported as memory monitors
EC-88 | Added support for HPE ProLiant Gen 11 servers via iLO 6
EC-90 | HP iLO Gen 10 (REST): Split into two connectors: `HPE iLO 5 (ProLiant Gen10 and Gen10 Plus)` and `HPE iLO 6 (ProLiant Gen11)`
EC-91 | HP iLO Gen 9 (REST): Renamed to `HPE iLO4 (ProLiant Gen 8, Gen9)`
EC-100 | EMC uemcli (VNXe): Power and temperature metrics are now collected

#### Fixed Issues

ID | Description
--- | ---
EC-84 | Pure Storage FA Series: The `hw.parent.type` attribute is reported as `DiskController` instead of `disk_controller`
EC-95 | Dell EMC PowerStore (REST): Metrics are missing for physical disks, network cards, memory modules, fans and power supplies
EC-97 | Pure Storage FA Series (SSH): `hw.temperature` metrics are not collected
EC-98 | Dell iDRAC9 (REST): Incorrect JSON response handling leads to HTTP 404 error on network devices

### MetricsHub Community Edition v1.0.00

#### What's New

ID | Description
--- | ---
#424[1] | Added protocol CLIs to validate configurations, troubleshoot connectivity, and ensure successful metric extraction

#### Changes and Improvements

ID | Description
--- | ---
#519[2] | Updated connector semantics by replacing `leftConcat` with `prepend`, `rightConcat` with `append`, and `osCommand` with `commandLine`.
#521[3] | Updated OpenTelemetry Java dependencies to version `1.45.0`
#525[4] | Added the ability to enable or disable self-monitoring

#### Fixed Issues

ID | Description
--- | ---
#523[5] | The `hw.network.up` metric is not reported for connectors with `WARN` or `ALARM` link state

#### Documentation Updates

ID | Description
--- | ---
#546[6] | Integrated platform icons and enhanced connectors directory page
#541[7] | Moved use cases from the documentation to MetricsHub Use Cases[8]
#533[9] | Documented the self-monitoring feature
#529[10] | Created a Troubleshooting section in the user documentation

### MetricsHub Community Connectors v1.0.08

#### What's New

ID | Description
--- | ---
#137[11] | Added support for `MySQL` databases via `JDBC`

#### Changes and Improvements

ID | Description
--- | ---
#158[12] | Updated platforms for community connectors
#160[13] | Created Storage metric semantic conventions
#163[14] | `MIB2Switch` and `GenericSwitchEnclosure` connectors now support Arista platforms

#### Fixed Issues

ID | Description
--- | ---
#111[15] | LinuxIPNetwork: Fails to monitor some Ethernet interfaces

## MetricsHub Enterprise Edition v1.0.02

#### Changes and Improvements

ID | Description
--- | ---
M8BEE-35 | Replaced deprecated `loggingexporter` with `debugexporter` in `otel-config-example.yaml`

### MetricsHub Enterprise Connectors v102

#### Changes and Improvements

ID | Description
--- | ---
EC-87 | The `StatusInformation` of the `led` monitor now reports the `LedIndicator` value

#### Fixed Issues

ID | Description
--- | ---
EC-74 | HP Insight Management Agent - Drive Array: The `disk_controller` status is not reported
EC-77 | Redfish: Enclosures are duplicated for Dell iDRAC and HP
EC-78 | Dell OpenManage Server Administrator: The `hw.enclosure.energy` metric is not converted to Joules
EC-79 | Dell XtremIO REST API: The `hw.parent.type` attribute is reported as `DiskController` instead of `disk_controller`
EC-93 | Connectors reporting voltage metrics do not set the `high.critical` threshold

### MetricsHub Community Edition v0.9.08

#### Changes and Improvements

ID | Description
--- | ---
#379[16] | Added support for escaped macros
#422[17] | Developed a JDBC Extension to enable support for SQL-based connectors
#432[18] | Standardized the log messages for all the criteria tests
#435[19] | [BREAKING_CHANGE] Added support for multiple variable values for the same connector
#468[20] | Added support for shared-characteristics for centralized resource configuration
#470[21] | Added support for `host.id`, `host.name`, and other attributes as arrays in resource configuration
#472[22] | Prevented sensitive configuration details from being displayed in error logs
#474[23] | Handled blank values when creating INSERT queries for `internalDbQuery` Sources
#498[24] | Improved monitoring jobs when invoking Jawk sources in connectors

#### Fixed Issues

ID | Description
--- | ---
#478[25] | A NullPointerException occurs when processing `HTTP` detection criteria
#480[26] | IPMITool criteria and source fail due to invalid `ipmitool` command
#500[27] | Only one monitor is processed due to incorrect indexing
#502[28] | Incorrect link status check leads to an incorrect power consumption

#### Documentation Updates

ID | Description
--- | ---
#462[29] | Reviewed Configure Monitoring documentation
#462[29] | Moved the CLI documentation to the Appendix section
#463[30] | Combined the Linux and Windows Prometheus quick starts into a unique Prometheus quick start
#484[31] | Documented the Prometheus/Grafana integration
#289[32] | Documented the use cases: Monitoring network interfaces using SNMP, Monitoring a process on Windows, Monitoring a remote system running on Linux, Monitoring a service running on Linux, Monitoring the Health of a Service, and Pinging resources
#505[33] | Updated references to the deprecated `loggingexporter`

### MetricsHub Community Connectors v1.0.07

#### Changes and Improvements

ID | Description
--- | ---
#112[34] | Windows Process: The process user name is now retrieved and selectable through configuration variables
#143[35] | Linux OS: The connector no longer reports services, as these are now handled by the `LinuxService` connector
#148[36] | Linux OS: Enhanced `filesystem` utilization calculation

#### Fixed Issues

ID | Description
--- | ---
#140[37] | `Platform` mispelling in `Linux` & `LinuxService` connectors
#145[38] | IpmiTool: The `hw.status` metric is not collected because `enclosure.awk` reports `OK`, `WARN`, `ALARM` instead of `ok`, `degraded`, `failed`
#152[39] | Connectors reporting voltage metrics do not set the `high.critical` threshold

#### Documentation Updates

ID | Description
--- | ---
#128[40] | Documented default connector `variables`
#129[41] | Replaced all references to `sql` with `internalDbQuery`

## 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[42] | [BREAKING_CHANGE] Disabled Automatic Hostname to FQDN resolution
#427[43] | BMC Helix Integration: Added the `StatusInformation` internal text parameter to the connector monitor
#421[44] | Reduced Alert noise for `hw.status{state="present"}`
#414[45] | Added a link to MetricsHub Community Connectors 1.0.06
#412[46] | The `hw.status{state="present"}` metric is no longer reported for cpu monitors discovered by Linux and Window connectors
#383[47] | Implemented a new engine method `megaBit2Byte` to align with OpenTelemetry unit standards
#374[48] | Default connector variables can now be specified in YAML connector files
#302[49] | Defined `afterAll` and `beforeAll` jobs in YAML connectors
#423[50] | Added the ability to filter monitors

#### Fixed Issues

ID | Description
--- | ---
#436[51] | The log message for SNMP v3 credential validation is incorrect
#439[52] | Connector default variables are not serializable
#417[53] | JavaDoc references are incorrect
#410[54] | Protocol definition is applied to only one host in a multiple-host configuration
#368[55] | The `hw.power{hw.type="vm"}` metric is erroneously set to 0
#456[56] | An exception occurs when monitoring ESXi through vCenter authentication

### MetricsHub Community Connectors v1.0.06

#### Changes and Improvements

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

#### Fixed Issues

ID | Description
--- | ---
#120[60] | 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/424
- [2] https://github.com/sentrysoftware/metricshub/issues/519
- [3] https://github.com/sentrysoftware/metricshub/issues/521
- [4] https://github.com/sentrysoftware/metricshub/issues/525
- [5] https://github.com/sentrysoftware/metricshub/issues/523
- [6] https://github.com/sentrysoftware/metricshub/issues/546
- [7] https://github.com/sentrysoftware/metricshub/issues/541
- [8] https://metricshub.com/usecases
- [9] https://github.com/sentrysoftware/metricshub/issues/533
- [10] https://github.com/sentrysoftware/metricshub/issues/529
- [11] https://github.com/sentrysoftware/metricshub-community-connectors/issues/137
- [12] https://github.com/sentrysoftware/metricshub-community-connectors/issues/158
- [13] https://github.com/sentrysoftware/metricshub-community-connectors/issues/160
- [14] https://github.com/sentrysoftware/metricshub-community-connectors/issues/163
- [15] https://github.com/sentrysoftware/metricshub-community-connectors/issues/111
- [16] https://github.com/sentrysoftware/metricshub/issues/379
- [17] https://github.com/sentrysoftware/metricshub/issues/422
- [18] https://github.com/sentrysoftware/metricshub/issues/432
- [19] https://github.com/sentrysoftware/metricshub/issues/435
- [20] https://github.com/sentrysoftware/metricshub/issues/468
- [21] https://github.com/sentrysoftware/metricshub/issues/470
- [22] https://github.com/sentrysoftware/metricshub/issues/472
- [23] https://github.com/sentrysoftware/metricshub/issues/474
- [24] https://github.com/sentrysoftware/metricshub/issues/498
- [25] https://github.com/sentrysoftware/metricshub/issues/478
- [26] https://github.com/sentrysoftware/metricshub/issues/480
- [27] https://github.com/sentrysoftware/metricshub/issues/500
- [28] https://github.com/sentrysoftware/metricshub/issues/502
- [29] https://github.com/sentrysoftware/metricshub/issues/462
- [30] https://github.com/sentrysoftware/metricshub/issues/463
- [31] https://github.com/sentrysoftware/metricshub/issues/484
- [32] https://github.com/sentrysoftware/metricshub/issues/289
- [33] https://github.com/sentrysoftware/metricshub/issues/505
- [34] https://github.com/sentrysoftware/metricshub-community-connectors/issues/112
- [35] https://github.com/sentrysoftware/metricshub-community-connectors/issues/143
- [36] https://github.com/sentrysoftware/metricshub-community-connectors/issues/148
- [37] https://github.com/sentrysoftware/metricshub-community-connectors/issues/140
- [38] https://github.com/sentrysoftware/metricshub-community-connectors/issues/145
- [39] https://github.com/sentrysoftware/metricshub-community-connectors/issues/152
- [40] https://github.com/sentrysoftware/metricshub-community-connectors/issues/128
- [41] https://github.com/sentrysoftware/metricshub-community-connectors/issues/129
- [42] https://github.com/sentrysoftware/metricshub/issues/433
- [43] https://github.com/sentrysoftware/metricshub/issues/427
- [44] https://github.com/sentrysoftware/metricshub/issues/421
- [45] https://github.com/sentrysoftware/metricshub/issues/414
- [46] https://github.com/sentrysoftware/metricshub/issues/412
- [47] https://github.com/sentrysoftware/metricshub/issues/383
- [48] https://github.com/sentrysoftware/metricshub/issues/374
- [49] https://github.com/sentrysoftware/metricshub/issues/302
- [50] https://github.com/sentrysoftware/metricshub/issues/423
- [51] https://github.com/sentrysoftware/metricshub/issues/436
- [52] https://github.com/sentrysoftware/metricshub/issues/439
- [53] https://github.com/sentrysoftware/metricshub/issues/417
- [54] https://github.com/sentrysoftware/metricshub/issues/410
- [55] https://github.com/sentrysoftware/metricshub/issues/368
- [56] https://github.com/sentrysoftware/metricshub/issues/456
- [57] https://github.com/sentrysoftware/metricshub-community-connectors/issues/125
- [58] https://github.com/sentrysoftware/metricshub-community-connectors/issues/122
- [59] https://github.com/sentrysoftware/metricshub-community-connectors/issues/114
- [60] https://github.com/sentrysoftware/metricshub-community-connectors/issues/120

## Search Results for {{siteSearch | truncate:'50'}}

{{resultArray.length}}
{{parent.title}} {{parent.title}}

{{result.title}}

{{result.body | truncate:'400'}}

{{parent.title}}
{{result.title}}
{{result.body | truncate:'100'}}

No results.