signed requests ?
that was an adaptor so that the json plugin would work with rrd
So in my server you can generate presigned urls
much like s3 signed urls
which have an expiry
the main point is you can embed/link graphs from a different web application
ack (signed)
Awesome work - now please follow the grafana procedure to sign your plugin
it is waiting in the review queue
it has been a long time missing piece
you can look at my grafana plugin's github actions if you like for automatically signing new releases
but they were broken
but I managed to fix them lol
It just won't work until someone from grafana approves my account I think
so at least now i think it plugged an obvious hole
my yak shave mission is almost done lol
I would also like to do a port of https://github.com/oetiker/RrdGraphJS to work with my rrdsrv
so i can draw them in the original rrdtool styles, but i guess that can wait
just gradually overnight running in remote control mode, the memory usage is creeping up
lets have a PR :)
Tbh, i wasn't quite sure what the purpose of the return values in xport are
I guess xport is historically a port of json graph output?
I thought it was fun rrdsrv found a bug in itself the first night i left it running
so it did its job
andrewchambers: any news from grafana (signing)?
1 reply
random thoughts about rrdtool 2.0:
- I was thinking a bit about ways to maintain a fixed sized file while adding more compression, dunno if anyone has done any work on that?
- I think if the graphing tool/code was stand alone it could be reused while making a smaller core of rrdtool. Though i guess most of the hard stuff is shared with xport, around aligning values.