The Grafana Champions programme is one of those things that sounds like it needs an invitation and a decade of credentials. It does not. The published bar is four core contributions a year, and the definition of a contribution is broad enough that a fair number of people reading this have already cleared it without realising the programme exists.
Here is what the requirement actually is, what counts, what you get, and the part of the commitment that is easy to skim past.
Grafana describe it as an initiative for community leaders and experts who drive innovation, collaboration and knowledge-sharing in the Grafana community. In practice it is a recognition programme with a working relationship attached: Grafana amplify what you make, and you get a direct line to their team and to other people doing the same thing.
It is selective without being exclusive. The public directory lists 80+ champions across 31 countries, with 300+ contributions logged. The real figure moves - as of mid-2026 it is a little over a hundred. So: not a closed shop, but not a badge everybody has either.
Figures and requirement wording from the Grafana Champions programme page, checked 2026-08-28.
The headline criterion is: engage in at least four core contributions annually. Four things, in a year. That is the bar.
| Counts as a core contribution | Shape |
|---|---|
| Blog posts | Written, on your own site or anywhere else |
| Podcasts | Appearing on them, or running one |
| Code contributions | To Grafana or the ecosystem around it |
| Conference speaking | Talks, and organising or hosting meetups |
Video content and sustained help in the community - forums, Reddit, the usual places people actually ask questions - are the other routes people arrive through. If you have ever written up how you solved a Grafana problem because you could not find the answer anywhere, that is the thing. Four of those in twelve months is not a demanding pace.
This is the part worth saying plainly, because it puts people off unnecessarily. The programme does not ask you to promote the product or stay positive about it. Criticism is a contribution: writing about what does not work, what is missing, what you think was designed wrong. That is more useful to the community and to Grafana than another launch-day walkthrough, and it is the difference between a champions programme and an affiliate scheme.
Three other expectations sit alongside the contributions, and the first is the one people underestimate:
| Benefit | Why it is worth something |
|---|---|
| Featured blog posts and social amplification | The most valuable one by a distance if you make content. Distribution is the hard part of publishing, and having the vendor share your work reaches an audience you cannot buy your way to. |
| Private Slack with champions and Grafana staff | Answers to the questions that are not in the documentation, from the people who wrote it. Also the fastest route to knowing what is coming. |
| Event invitations | Access to events with the Grafana team and other practitioners. The networking is the point. |
| Exclusive swag store | It is swag. Pleasant, not a reason to join. |
Honestly: it depends entirely on whether you were going to make the contributions anyway.
If you already write, speak or make videos about observability, the programme costs you almost nothing incremental and gives you distribution plus a direct channel to the people building the thing. That is a straightforwardly good trade, and the amplification compounds - work that would have reached your own audience reaches theirs.
If you would be producing four contributions a year in order to qualify, think harder. Content made to satisfy a quota reads like content made to satisfy a quota, and the monthly meeting commitment is real. The programme rewards people who were already doing the work; it is a poor reason to start doing it.
The practical route in. Contribute first, apply second. Four pieces of genuinely useful work - a write-up of something you fixed, a talk at a local meetup, a fix upstream - and you are describing an existing track record rather than a plan. Pick problems you actually hit; those are the ones other people are searching for and cannot find answers to.
Nine minutes on the backstory, the programme, and what it actually asks of you.
Most of what I know about Grafana and Zabbix came from doing this in production and then explaining it badly until it got clearer. If you are standing up observability, auditing something that grew organically, or trying to get two platforms to talk to each other, that is the work I do at KorFlux.