Hello,
Since the update from 24.10.15 to 24.10.18, the graph date picker is broken on our instance.
Quick time ranges like “Last 3 hours” are working normally but if we want to zoom on a graph or set a manual time range, it fails 100%.
The issue comes from the Javascript not selecting the right start/end date for the API call.
In browser console we’ve got messages like :
moment-timezone-with-data.min.js:1 Moment Timezone has no data for 2026-02-03 09:48. See http://momentjs.com/timezone/docs/#/data-loading/.
moment-timezone-with-data.min.js:1 Moment Timezone has no data for 2026-02-03 10:24. See http://momentjs.com/timezone/docs/#/data-loading/.
moment-timezone-with-data.min.js:1 Moment Timezone has no data for 2026-02-03 09:48. See http://momentjs.com/timezone/docs/#/data-loading/.
moment-timezone-with-data.min.js:1 Moment Timezone has no data for 2026-02-03 10:24. See http://momentjs.com/timezone/docs/#/data-loading/.
d3.min.js:1 Error: <rect> attribute x: Expected length, "NaN".
d3.min.js:1 Error: <rect> attribute width: Expected length, "NaN".
API calls being :
https://xxx/centreon/api/internal.php?object=centreon_metric&action=metricsDataByService&ids=1947_28951&start=1770118132&end=1770118132&type=ng
https://xxx/centreon/api/internal.php?object=centreon_metric&action=statusByService&ids=1947_28951&start=1770118132&end=1770118132&type=ng
Here is the response for the “metricsDataByService” API call :
[
{
"global": {
"host_name": "client-prod",
"service_description": "CPU_Load",
"title": "CPU_Load graph on client-prod",
"start": "1770118132",
"end": "1770118132",
"vertical-label": "Value",
"base": 1000,
"width": 550,
"height": 140,
"scaled": 1,
"multiple_services": false
},
"metrics": [
{
"index_id": 7504036,
"metric_id": 170526,
"metric": "cpu_mhz",
"metric_legend": "cpu_mhz",
"unit": "",
"hidden": 0,
"min": null,
"max": null,
"virtual": 0,
"ds_data": {
"ds_min": "1",
"ds_max": "1",
"ds_minmax_int": "0",
"ds_last": "1",
"ds_average": "1",
"ds_total": "0",
"ds_tickness": 1,
"ds_color_line_mode": "1",
"ds_color_line": "#6666ff",
"ds_invert": null
},
"legend": "cpu_mhz",
"stack": 0,
"warn": null,
"warn_low": null,
"crit": null,
"crit_low": null,
"ds_color_area_warn": "#ff9a13",
"ds_color_area_crit": "#e00b3d",
"ds_order": 0,
"data": [
null
],
"prints": [
[
"Last:nan"
],
[
"Min:nan"
],
[
"Max:nan"
],
[
"Average:nan"
]
],
"last_value": 0,
"minimum_value": null,
"maximum_value": null,
"average_value": null
},
{
"index_id": 7504036,
"metric_id": 167171,
"metric": "cpu",
"metric_legend": "cpu",
"unit": "%",
"hidden": 0,
"min": 0,
"max": 100,
"virtual": 0,
"ds_data": {
"compo_id": 6,
"host_id": null,
"service_id": null,
"name": "CPU",
"ds_order": 1,
"ds_hidecurve": null,
"ds_name": "cpu",
"ds_color_line": "#FF0000",
"ds_color_line_mode": "0",
"ds_color_area": "#FFFFFF",
"ds_color_area_warn": null,
"ds_color_area_crit": null,
"ds_filled": null,
"ds_max": "1",
"ds_min": "1",
"ds_minmax_int": null,
"ds_average": "1",
"ds_last": "1",
"ds_total": null,
"ds_tickness": 1,
"ds_transparency": null,
"ds_invert": null,
"ds_legend": null,
"ds_jumpline": "0",
"ds_stack": null,
"default_tpl1": null,
"comment": null
},
"legend": "cpu",
"stack": 0,
"warn": 75,
"warn_low": 0,
"crit": 90,
"crit_low": 0,
"ds_color_area_warn": "#ff9a13",
"ds_color_area_crit": "#e00b3d",
"ds_order": 1,
"data": [
null
],
"prints": [
[
"Last:nan"
],
[
"Min:nan"
],
[
"Max:nan"
],
[
"Average:nan"
]
],
"last_value": 0,
"minimum_value": null,
"maximum_value": null,
"average_value": null
}
],
"times": [
"1770118140"
],
"acknowledge": [],
"downtime": []
}
]
We’ve tried to update to latest 25.10 but issue is still there.
We’ve got another Centreon instance but by comparing settings, we cannot find any difference that could explain this broken graph behavior (same timezones settings, same SSO login, same Apache/PHP settings, etc).
What can we try to fix this very annoying bug ?
Regards.
Mathieu
