2. • I used to be a developer
• Then I became an Ops person
• Chief Trolling/Travel/Technical Officer @ Inuits.eu
• Everything is a Freaking DNS Problem
• DNS : devops needs sushi
• Buiding Clouds since before the Bookstore
• Organiser of #devopsdays, #cfgmgmtcamp, #loadays, ...
Who am I ?
@krisbuytaert
3. • Operational Metrics
• Application Metrics
• Business Metrics
• Travel time to home during Traffic Jams
• Time between last conference
• Legobricks ordered
• Sandwiches ordered by the team
Dashboard all the things
@krisbuytaert
4. • People edit a Dashboard
• People clone a Dashboard
• People create a new Dashboard
• People "improve" other people's Dashboards
• People delete other people's Dashboards
class {'chaos':
ensure => present
}
Dashboards Sprawl
@krisbuytaert
5. • No more hacking in production
No more manual changes?
@krisbuytaert
9. We are all JSON engineers
We are all YAML engineers
The average end user who wants to create his own dashboard
is not a devoops YAML Engineer
This is just too complex
Problems with Dashboard as Code
@krisbuytaert
10. • A dev Grafana
• Dashboard as Code
• Dashboard for Dirty Clickers
• A prod Grafana (read only)
• A way to promote from dev to prod
What we really need
@krisbuytaert
16. Step 3 : Check downstream Created Jobs
@krisbuytaert
17. Step 4 : Promote the (individual) Dashboard
@krisbuytaert
18. Step 5 : New dashboard is in prod
@krisbuytaert
19. • Usable for End Users
• Version controlled
• Reproducable
• Preventing dashboard Sprawl
• Can still be used for dashboards from "real" code. to do the promotions
Conclusion
@krisbuytaert