💚 Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS

🤖 GitHub comments

🌐 Coverage report

Verification check for timeseries enablement - info datastream

hidden": "true",
      "time_series": {
        "end_time": "2023-10-16T15:26:19.000Z",
        "start_time": "2023-10-16T11:26:19.000Z"
      },
      "provided_name": ".ds-metrics-haproxy.info-default-2023.10.16-000002",

time_series mapping

Verification check for timeseries enablement in stats datastream

      "time_series": {
        "end_time": "2023-10-16T15:35:18.000Z",
        "start_time": "2023-10-16T11:26:19.000Z"
      },

metric_type mapping

uses incorrect aggregation functions in multiple dashboards and visualisation.

@agithomas, Can we briefly summarise the issues in the earlier aggregation and what was fixed. It's rather tricky to get a summary from the json file changes.

@agithomas, Can we briefly summarise the issues in the earlier aggregation and what was fixed. It's rather tricky to get a summary from the json file changes.

For all the fields that are having metric_type as counter, sum() function is used presently in the dashboard. This shows incorrect values in the dashboard compared to the /stats dashboard of haproxy.

All sum() functions are replaced with max() functions when field is having metric_type counter. This correction is also needed for TSDB compatibility for counter type fields to not show errors when using sum() function

Package haproxy - 1.8.6 containing this change is available at https://epr.elastic.co/search?package=haproxy