Add support for timeseries panels #362
Conversation
|
|
rhowe
force-pushed
the
add-timeseries
branch
6 times, most recently
from
96844c0 to
1f9f002
Compare
rhowe
force-pushed
the
add-timeseries
branch
2 times, most recently
from
8d3c2cc to
0e5f0bd
Compare
|
@malcolmholmes sorry to be a pain, and I know grafonnet isn't exactly an active project these days but what are the chances of this PR getting a review? |
|
@rhowe Agreed, I would absolutely love having timeseries compatibility :) |
|
@malcolmholmes same here! this would be incredibly useful |
|
If you want this, please don't continue to spam a Grafana engineer with comments (yes, OK, I know, I started it, but we don't all need to do it). Just add a 👍 to the MR Also there's nothing stopping you taking the code from my branch and using it yourself, even if it's not in the main grafonnet repo. |
rhowe
force-pushed
the
add-timeseries
branch
2 times, most recently
from
f1b7e21 to
446015b
Compare
rhowe
force-pushed
the
add-timeseries
branch
2 times, most recently
from
b020d8f to
f7d5097
Compare
- jsonnet to 18 - cypress to 10.9 - grafana to 9.2.1
rhowe
force-pushed
the
add-timeseries
branch
2 times, most recently
from
a334037 to
9b935b5
Compare
This is based on the behaviour of Grafana 9.0.5
|
See new README. This repo is deprecated. The new Grafonnet has support for the timeseries panel (https://github.com/grafana/grafonnet) |
This is based on the behaviour of Grafana 9.0.5
It should address #358 and #352
Upgrade the e2e tests to work with Grafana 9.x
Fixes #363
Note that I haven't used cypress before and I work hard to avoid node, so this might not be quite right.
I added a
Makefiletarget for runningnpm installto allow upgrading Cypress without relying on a local Nodejs install.Somehow I missed the fact the repo had tests until I was too far down the rabbit hole writing the tests in a different style, hope that's OK.