NetXMS Support Forum

English Support => General Support => Topic started by: MarcusH on October 15, 2025, 10:02:31 AM

Title: Grafana with Infinity and server api
Post by: MarcusH on October 15, 2025, 10:02:31 AM
Hi,

Started migrating our Grafana to Infinity and new server api.
Saw the techtalk video on youtube and the blog post nice work.

One thing i noticed was that you use $__from/1000 and $__to/1000 for seconds and was having issue it not working, found that Grafana has these variables i guess they are cleaner to use ${__from:date:seconds} and ${__to:date:seconds}

Also trying to get relative time to work, i have dashboard on last 30min beacuse they are used on TV screens but some DCI just collects once a day and i have 12h relative on them, tried ${__from:date:seconds}-43200 but does not seem to work i get all 3 days that are in history.

is it supposed to calc before query or send it to api? URL is ?timeFrom=1760509472-43200&timeTo=1760511272

Running 5.2.6 and latest Inifinity
Title: Re: Grafana with Infinity and server api
Post by: MarcusH on October 15, 2025, 10:58:37 AM
Actually when i think about it would be great if there is a parameter for objects history that just returns latest value regardless of time. That would solve a lot of time related challenges we have in Grafana for dashboards with lots of values with first calculation option.

Edit:

found it maxRows=1
Title: Re: Grafana with Infinity and server api
Post by: MarcusH on October 20, 2025, 12:00:36 PM
Is it possible to create permanent auth token for new API server?
Title: Re: Grafana with Infinity and server api
Post by: Filipp Sudanov on October 20, 2025, 03:48:50 PM
You can issue a token from Users and groups by right-clicking on a user.
Title: Re: Grafana with Infinity and server api
Post by: MarcusH on October 21, 2025, 09:12:54 AM
I did that but after server restart everything got 401 unauthorized and i had to reissue token.
I see now that log states "New persistent authentication token issued for user grafana [10]" i guess something might be wrong with token save then.