Roadmap

[yesoreyeram]

Infinity data source plugin roadmap

potential candidates for upcoming versions

• token refresh authentication
• prom/loki agent
• local time-shift
• Join results from multiple APIs

Version 2.0.0

• Pagination of API responses #601
• Server Side Transformations #614
• move backend experimental features out of beta

Version 1.0.0

• OAuth support
• Basic/experimental backend support for common JSON formats
• Support for Grafana unified Alerting
• Support for Grafana Server Side Expressions
• Support for Grafana Recorded queries

Version 0.10.0

• Client side query caching
• In JSON, Add support to access fields outside array ( use UQL instead )
• Dynamic interval variable
• Migrate string based legacy variables

Version 0.9.0

• Support for GROQ query language
• Filter data with UQL
• Dashboard variables in results filter #196
• Show corresponding curl command in Query inspector
• Forward OAuth identity support

[ebachman24]

Being able to handle paginated results would be incredible. Great work! looking forward to it.

[gdiana]

The backend stuff is great well done and many thanks.

I saw a GRAFANA post that looked at being able to update the backend csv file to import added new data. Can this be done or is it already available under the GRAFAN update source feature?

[kayjayeff]

Personally, I would really like to see the "refresh token" ability put into the next version. This is something that does not seem to be out there in any API plugin. I have run into multiple data sources that require an initial token and then the refresh. Infinity is a great and versatile plugin and adding that functionality would make it even moreso.

[Moktad]

Yeah same here but I'm trying to find a workaround to somehow refresh the token
Please let me know if you found something about it.

[KevinDW-Fluxys]

+1

[jHumeLPL]

• token refresh authentication
• local time-shift
• Join results from multiple APIs

Assuming these 3 features work the way I hope, I am really excited for all of them, especially the token refresh and the local time-shift.

I assume the token refresh is to make querying API's that require getting a new token before querying them easier.

I assume the local time-shift is to allow changing timestamp values coming in from the API from one time zone to another. In our case, there's an API we query and all of the timestamps it returns are in Eastern, but of course Grafana requires UTC time. We have found a way to "fix" it using several different Grafana Transforms in the Query Editor, but it is a huge pain and being able to do it at the data source layer, before hitting the Grafana Visualization/Variables would be far better.

And wow, the more I think about the Join results from multiple APIs idea, the more I like that as well... I can think of several uses of that for us.

Keep up the great work!