-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Move our Grafana dashboards to spacemeridian.grafana.net #105
Comments
Station dashboard was migrated https://spacemeridian.grafana.net/d/F2UmmYnVk/station?orgId=1 |
Next is to migrate the alerts. @bajtos let's discuss this in the kickoff call, or do you have an idea how we could best do this? |
SGTM 👍🏻
Not from the top of my head 😞 |
@bajtos should we go ahead and remove the datasources from the PL instances? I don't see why not, now that we have ported all dashboards |
IMO, we need to migrate the alerts first, as these alerts are reading data from the datasources, right? |
great point! |
Then I'll unsassign myself for the time being :) |
I migrated Spark alerts to SpaceMeridan's Grafana instance. I am assigning the issue back to you, @juliangruber, so that you can perform the final cleanup. I don't have admin permissions to PL Grafana. Therefore, I cannot perform actions like deleting data sources. In addition to "Remove Station/Spark/Voyager datasources", I think we should also remove our dashboards and alerts. WDYT? |
All completed |
Public Dashboards
Out of scope:
Internal DevOps Dashboards
Filecoin Station GitHub releases(not used)Cleanup
Remove Station/Spark/Voyager datasources from Protocol Labs Grafana account - see https://protocollabs.grafana.net/connections/datasources:
Close or rework older Grafana-related tasks:
The text was updated successfully, but these errors were encountered: