range 1m not working if Prometheus scrape is 30s. Better to create template variable range, type interval and set values like 2m,3m,5m,10m,15m,30m,1h,2h,4h,6h,12h,1d,4d,7d,14d,30d, 1m, 90s, plus auto tick most variables should be loaded
using “on time range change” instead of “on dashboards load. In reality variables are not available when panel is loaded.
missing variables for code and status.
Checklist
[ ] The Pull Request has tests
[X] A changelog file has been created under changelog/unreleased/kong or skip-changelog label added on PR if changelog is unnecessary. README.md
Summary
Checklist
changelog/unreleased/kong
orskip-changelog
label added on PR if changelog is unnecessary. README.md