MetricsHub
MetricsHub Enterprise 1.0.02
-
Home
- Introduction
Release Notes
MetricsHub Enterprise Edition v1.0.02
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[1] | Added support for escaped macros |
| #422[2] | Developed a JDBC Extension to enable support for SQL-based connectors |
| #432[3] | Standardized the log messages for all the criteria tests |
| #435[4] | [BREAKING_CHANGE] Added support for multiple variable values for the same connector |
| #468[5] | Added support for shared-characteristics for centralized resource configuration |
| #470[6] | Added support for host.id, host.name, and other attributes as arrays in resource configuration |
| #472[7] | Prevented sensitive configuration details from being displayed in error logs |
| #474[8] | Handled blank values when creating INSERT queries for internalDbQuery Sources |
| #498[9] | Improved monitoring jobs when invoking Jawk sources in connectors |
Fixed issues
| ID | Description |
|---|---|
| #478[10] | A NullPointerException occurs when processing HTTP detection criteria |
| #480[11] | IPMITool criteria and source fail due to invalid ipmitool command |
| #500[12] | Only one monitor is processed due to incorrect indexing |
| #502[13] | Incorrect link status check leads to an incorrect power consumption |
Documentation updates
| ID | Description |
|---|---|
| #462[14] | Reviewed Configure Monitoring documentation |
| #462[14] | Moved the CLI documentation to the Appendix section |
| #463[15] | Combined the Linux and Windows Prometheus quick starts into a unique Prometheus quick start |
| #484[16] | Documented the Prometheus/Grafana integration |
| #289[17] | 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[18] | Updated references to the deprecated loggingexporter |
MetricsHub Community Connectors v1.0.07
Changes and Improvements
| ID | Description |
|---|---|
| #112[19] | Windows Process: The process user name is now retrieved and selectable through configuration variables |
| #143[20] | Linux OS: The connector no longer reports services, as these are now handled by the LinuxService connector |
| #148[21] | Linux OS: Enhanced filesystem utilization calculation |
Fixed issues
| ID | Description |
|---|---|
| #140[22] | Platform mispelling in Linux & LinuxService connectors |
| #145[23] | IpmiTool: The hw.status metric is not collected because enclosure.awk reports OK, WARN, ALARM instead of ok, degraded, failed |
| #152[24] | Connectors reporting voltage metrics do not set the high.critical threshold |
Documentation updates
| ID | Description |
|---|---|
| #128[25] | Documented default connector variables |
| #129[26] | Replaced all references to sql with internalDbQuery |
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[27] | [BREAKING_CHANGE] Disabled Automatic Hostname to FQDN resolution |
| #427[28] | BMC Helix Integration: Added the StatusInformation internal text parameter to the connector monitor |
| #421[29] | Reduced Alert noise for hw.status{state="present"} |
| #414[30] | Added a link to MetricsHub Community Connectors 1.0.06 |
| #412[31] | The hw.status{state="present"} metric is no longer reported for cpu monitors discovered by Linux and Window connectors |
| #383[32] | Implemented a new engine method megaBit2Byte to align with OpenTelemetry unit standards |
| #374[33] | Default connector variables can now be specified in YAML connector files |
| #302[34] | Defined afterAll and beforeAll jobs in YAML connectors |
| #423[35] | Added the ability to filter monitors |
Fixed issues
| ID | Description |
|---|---|
| #436[36] | The log message for SNMP v3 credential validation is incorrect |
| #439[37] | Connector default variables are not serializable |
| #417[38] | JavaDoc references are incorrect |
| #410[39] | Protocol definition is applied to only one host in a multiple-host configuration |
| #368[40] | The hw.power{hw.type="vm"} metric is erroneously set to 0 |
| #456[41] | An exception occurs when monitoring ESXi through vCenter authentication |
MetricsHub Community Connectors v1.0.06
Changes and Improvements
| ID | Description |
|---|---|
| #125[42] | Disabled automatic detection for WindowsProcess, WindowsService, and LinuxService |
| #122[43] | Added default values for connector variables in WindowsService, LinuxService, WindowsProcess & LinuxProcess |
| #114[44] | The hw.network.bandwidth.limit metric is now displayed in bytes |
Fixed issues
| ID | Description |
|---|---|
| #120[45] | The hw.vm.power_ratio unit is incorrect. It should be 1 instead of Cel |
Search Results for {{siteSearch | truncate:'50'}}
{{resultArray.length}}
No results.