Nested or Dynamic API endpoints

[mcbloch]

Grafana is very handy to use with a json api. The problem now is that our data is flat and there are no nested objects.
So laps have the team-id and no name. Grafana as far as I know cannot do recursive requests which makes visualisations very hard to read.

There are a few solutions here.

• Add some nested data to the existing endpoints. For example add the team object to the requested lap. Could then be used with https://grafana.com/grafana/plugins/marcusolsson-json-datasource/.
• Add a query endpoint that can handle specific requests. This needs to be very specific and is not very easy to implement. Could be used with https://grafana.com/grafana/plugins/simpod-json-datasource/
• Add graphql. The client can then choose it's own structure. Could then be used with https://grafana.com/grafana/plugins/fifemon-graphql-datasource/.

The graphql seems the most sensible and powerful. Can also be used by other clients without the pollution of the basic rest api.
I'm going to start there, but suggestions, counter arguments and other options are welcome.

[Robbe7730]

Coming back to this, I think something like graphql would make the most sense

[NuttyShrimp]

I think we should move all our little scripts to transform our data from telraam to grafana into telraam itself and exposes this data via an /metrics endpoint