Skip to content

Grafana: testing_draft

note: grafana public dashboard when we enter to the site we see that in that moment we are running the query. 1. 1. What if we use public dashboard? 1. What are the risks? 2. What if we use second grafana server ant there we share to public. 3. Or we can create second organisation like hostname:3000/?orgId=2 4. Who need to check this status pages?

Notes: - [x] Yes you could write documentation about this - [x] How we implement this - [x] Here we need: - [x] Install plugin on grafana and - [x] Create onCall engine :8080 This is for what?: - [ ] What settings is there for us to decide: -notes:

  • [ ] - [ ] We need to install plugin on grafana and that plugin we connect with onCall engine.
    • [ ] we need more details for this:

Public dashboard * Yeah great so we can use this but it does  of queries * I don't know that can we count these any other way but to just make the status page like for a 2-4weeks period and see that how much queries it does? * Depends the access * This is more about GCP api access * We run on permisess

-Should we use another Grafana page instead of our https://dash.attracs.com/ landing page where is everything? Just thinking that if we create a public dashboard to our dash.attracs.com is there then a risk that a hacker etc could access from public dashboard to our whole dash.attracs.com? - is there any documentation that how does grafana tell this to be done "best practices" Also: what url's can you do when you make a whole new Grafana page (example: dash.aholadigital.com, servicestatus.aholadigital.com etc?)