You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The command succeeds, but produces an empty snapshot when targeting local on-premise instance (tested Grafana v9 and v10):
Note: The command succeeds and produces a correct snapshot showing the dashboard when using Grizzly v0.3.1 or earlier (with the grr preview .. command. The grr preview command was reintroduced in v0.4.1 as grr snapshot.
All of them are included in the repository mentioned.
This issue is reported as a bug, but it might simply be that I haven't yet learned the new approach to snapshotting introduced in v0.4.1. Please let me know in that case :-)
The text was updated successfully, but these errors were encountered:
Grizzly Version
v0.6.1
Expected Behavior
The command
grr snapshot ...
should deploy local dashboards as snapshots to the instance specified inGRAFANA_URL
.Actual Behavior
The command errors when targeting Grafana Cloud:
The command succeeds, but produces an empty snapshot when targeting local on-premise instance (tested Grafana v9 and v10):
Note: The command succeeds and produces a correct snapshot showing the dashboard when using Grizzly v0.3.1 or earlier (with the
grr preview ..
command. Thegrr preview
command was reintroduced inv0.4.1
asgrr snapshot
.Steps to Reproduce
Repository with minimum reproducible files: https://github.com/mikaello/grizzly-snapshot-reproduction
In essence:
jb install
grr preview -e 1000 dashboards.jsonnet
, confirm that it is workinggrr snapshot -e 1000 dashboards.jsonnet
, notice error message or blank dashboard deployed (depending on target environment)In addition to the CLI tools
jb
andgrr
(in two different versions), you need the following files:All of them are included in the repository mentioned.
This issue is reported as a bug, but it might simply be that I haven't yet learned the new approach to snapshotting introduced in v0.4.1. Please let me know in that case :-)
The text was updated successfully, but these errors were encountered: