This is an experience report. A colleague and I have been working on leveling-up the observability story within Fastly’s engineering org. I suspect a lot of you are thinking about starting, or in the middle of, similar initiatives. I thought it would be useful to talk about the interesting successes and failures we’ve had. I’ll step through the life of the project, highlighting interesting discoveries along the way, and then summarize the key takeaways at the end. As it turns out, the technical challenges were actually the easy ones: the hard parts have been largely social and political.
To understand our operating context, I guess it’s necessary to understand a little bit about Fastly the company. Fastly is an edge cloud and content delivery network. We started in 2011 and have a slightly different take on the market: we use beefier machines in our POPs, and a relatively modern software stack, to provide a more featureful and programmable edge product.
Fastly has historically been an engineering org of mostly senior engineers. This was by design, and allowed great product and technical velocity at the outset, and continued as we grew to our current size of about 120 engineers. But like any technical decision, there are both benefits and risks.
Teams of senior engineers bring their experience with them. They also operate quite autonomously. This has the inevitable result of a heterogeneous mix of designs, implementations, and support tooling—including monitoring.
Our monitoring universe grew organically, and organic growth of software tends to be append-only. Initially ad-hoc dashboards, proving their value through the course of time, would become canon. Incident-driven alerts specialized to specific or quixotic symptoms would be created but, of course, rarely audited. Over a period of years, these patterns produced highly-specialized monitoring regimes: essentially local optima that worked well in the small, but didn’t benefit from coherence in the large.
To be clear: this is desirable, to a degree. But even organic gardens need to be weeded sometimes.
Concretely, we want to be able to answer these questions for all of our production systems:
We want to make sure that any engineer in the organization can answer these questions for any service, with only an introductory understanding of our architecture.
Goals are obviously important to direct design and development efforts. Non-goals are even more important, to scope the work and keep the project tractable.
Observe that the questions we want to answer are focused on the present moment. Answering them accurately requires some degree of historical data, but not a lot. Marcus did some investigation of how our existing monitoring systems were used by internal customers. The vast majority of collected metrics were queried only over the last few hours or days. And despite collecting thousands of metrics for each host or service, only a tiny fraction of them were queried with any regularity. The actual usage patterns—which were hugely different than the usage patterns that teams said they had—helped us to define reasonable limitations. We would have only short data retention in the initial few versions of the infrastructure, on the order of weeks. Anything longer would be a separate initiative, after the initial rollout.
We’re also laser-focused on internal systems, owned and operated by the engineering org. We won’t build a system that serves other use cases, or is subject to other SLAs. One common example is surfacing data to customers. In our industry, for online multi-tenant systems, there’s a pretty clear line of demarcation between operational telemetry for our own systems, and (for lack of a better phrase) customer metrics, data showing us the experience of our customers. We already had reasonably mature systems in place for the latter, and didn’t want to expand the scope or risk profile to include them in our work.
It’s also important to understand the role of metrics in the broader context of observability, especially relative to the other two pillars of logging and tracing. Metrics are a great fit for reactive requirements like dashboards and alerts, and can provide a good system overview, but aren’t great for investigation. Metrics are complementary to a good logging pipeline, and our system shouldn’t try to supplant those use cases.
Having identified and scoped the problem, my colleague Marcus and I formed a project team to do the work. We both had pretty extensive domain knowledge: Marcus in Fastly, me in Prometheus, and both of us in observability work in general. This would be our primary, though not exclusive, focus for about a year.
After a domain survey and technology review, we settled on the following plan:
We would start by paving out the infrastructure using the tracer bullet methodology. That is, build a working solution quickly, but correctly, in the production environment, and using designs and techniques that are production-quality. This requires good familiarity with all of the tools, but it avoids a messy “productionization” step between prototype and final product.
To validate our plan would work, we’d pick a couple of services that would cover a reasonable cross-section of use cases. Some would be third-party, and we’d deploy the exporters; some would be in-house, and we’d either instrument them ourselves, or pair with the teams to instrument them. Finding friendly and enthusiastic internal alpha customers was crucial: they give us necessary context, and a testing ground for our theoretical workflows. If, after a short timebox, our alpha customers are happy, we have reasonable justification to carry on.
The initial spike took just under a month, and was a success. The roadblocks we hit in our infrastructure were surmountable, and our alpha customers were happy and enthusiastic.
The next step, then, was to inventory the company, and priority-rank teams and services by whatever criteria made sense. For us, this was a mix of production criticality and some notion of friendliness—better to have the folks eager to help earlier on, while we iron out the kinks. We created a burndown chart (really, a spreadsheet) with progress for each service. Of course, it grew over time, as we found more and more services hiding in the cracks. Each service progressed through stages: kickoff, instrumentation, production wire-up, dashboarding and alerting, and finally done. Time to start grinding it out!
Here’s where things get interesting. This was based on a mostly-successful strategy I witnessed at SoundCloud. We went with an embedded expert/consultant model, where I would personally rotate through teams in sequence, and essentially pair with them for a period of one to two weeks. The key realization was that the technical details are pretty rote and not difficult; the problem is actually social and educational. That is, getting engineers to understand first how the Prometheus model works, but more importantly why the things we’re doing are important and necessary. Since many teams have been operating in successful, locally-optimized silos for a long time, this boils down to a practice of empathy.
Step one is to help you instrument your code. In many cases, this was an hour or two of pair programming, followed by a round or two of PR review. Prometheus has a good local testing story, which was a big selling point for some engineers.
One small mistake I made: trying to lay out the process exhaustively, before the fact. Much of that guidance would change, as we went through the process with different teams. What worked a lot better was allowing common patterns to emerge naturally, and document them post-facto. This requires more high-touch work at the outset, but that turns out to be inevitable, anyway.
The documentation portal became an important center of mass. It was a GitHub wiki, with a roughly even split between narrative HOWTO-style guides, and a FAQ of specific questions as they arose. There was also a large section of case studies, describing the observability path of several teams; this was helpful for the many engineers who are most successful following the examples of others. But the real benefit of the portal, I think, was being able to sprinkle every observability-related conversation on e.g. Slack with deep links to answers or more information. This socializes and reinforces the documentation site as a source of authority, making people more able to help themselves in the future.
Once the code was instrumented and deployed, the next step was to get it plumbed into the Prometheus. Often, this required deploying Prometheus info a new corner of our infrastructure. This was easily the most time-consuming and trickiest technical part of the project, especially at the beginning, when we were still discovering and defining best practices. Our heterogeneous services had heterogeneous deployment models, and it took a long while to have good answers for all of them. Even once that was mostly done, new teams would invariably require exceptions. Over the life of the project, I think we were most often bottlenecked when trying to realize our design or architectural vision against the organic nature of our actual infrastructure.
These challenges were the most tractable consequence of a natural tension I alluded to earlier: between letting engineers choose the best tool for their job in isolation i.e. local optimization, and standardizing on common models and practices i.e. global optimization. The discussion of which to favor and why needs to happen continuously and transparently, with everyone involved in the engineering org. My experience is that most orgs don’t address the concern directly enough, and naturally bias toward local optimization in service to development velocity.
This should be understood as technical debt: fine to do, as long as it’s scoped, and done with a proper accounting of the costs. Indefinite deferral becomes exponentially more difficult to unwind, and, left unchecked, can derail teams or entire engineering orgs for years. And so, I think in a very real sense, leveling up your observability story can be understood as paying down technical (observability) debt accrued in service to velocity.
Once the metrics are being collected, it’s time to do something useful with them. This generally means a basic service dashboard and set of alerts, to answer our initial questions:
Many teams had built both in other products, which were generally straightforward to port over. That porting process gives us an opportunity to weed our garden of years of cruft. I asked each team these core questions, and tried to make sure we’d only build things that would answer them. A good dashboard is a carefully curated set of visualizations, in service to specific goals—not everything that could possibly or theoretically be relevant.
Similarly, alerts tended to grow over time, often in response to specific incidents. But a good set of alerts is similarly minimal, focused on high-level service metrics, not low-level technical details. For example, it’s almost always incorrect to alert on e.g. CPU load; much better to prefer alerts on e.g. 90th quantile request latency, or the time a job spends waiting in queues.
How this work got done was on a spectrum, based on interest and available resources on a team. On one extreme, the team could take care of it themselves entirely: there was (eventually) comprehensive, step-by-step documentation for both concerns on the documentation portal. On the other extreme, especially at the beginning of the project, I would often volunteer to prototype both a dashboard and initial set of alerts for the team, and ask them for review and feedback when I was done. And, in the middle, we could model it as another pairing session, where I would teach them the power of PromQL and the horrors of Grafana. (No shade, Grafana. Y’all doin’ the Lord’s work.)
It’s easy enough to do research and compile a set of best practices. It’s even easy to enumerate that reasoning in a clear way, on demand, in classes, or in pairing sessions. What’s difficult is convincing engineers with workflows that have historically worked for them that it’s worth trying something different, in service to higher-order goals. This is the real challenge of any org-wide hearts-and-minds project. And it’s why embedding (or something akin to it) is essential.
Every conversation I have when embedded begins as a fun little exploration, a dance, where I try to identify the context of the other person. I need to do this before I start giving any information. I have a lot of choices for the type and amount of information to give, essentially where to start the conversation, and starting it in the wrong place can be a disaster.
If the goal is to persuade, engineers—or, really, humans—by and large need to be met where they are. The promise of greener pastures is tempered by the pain of the journey to them. We can improve this ratio by making the promise greater, or more real; we can do that by delivering immediate and clear benefit in the form of the new ways. We can also improve the ratio by making the costs lesser; we can do that by shouldering some or much of the initial burden. In truth I think a successful enterprise must do both.
Getting by with something you already know is always easier, preferable, to learning something new. So to change the behavior of an entire org you have to motivate an excitement, de-program the fear, and help people escape the trap of learned helplessness. The only way this works is by establishing a connection, demonstrating understanding, and practicing empathy.
We have a few major departments within engineering, and each department has several teams, each with three to ten engineers. Service ownership is often indistinct, with many services in maintenance mode, without clear stewards. This isn’t a bad thing! It just means someone in my position needs to do the work to identify owners, and get work prioritized. At the beginning, with eager alpha customers, this is easy. But as things drag on, and the easy wins are won, buy-in at the top of the org chart is essential.
Teams can and will ignore carrot-based motivation, and sometimes need nudging with a stick. Ultimately, that can only come from senior leadership. Without a clear mandate and deadlines, and org-wide refactor like this devolves into a forever project, with 100% probability. (Even with a clear mandate and deadlines, some percentage of teams will always lag behind.)
Now, a few difficult or unexpected twists.
We anticipated that empathy would be important, but we didn’t anticipate just how important it would be. In particular, fighting learned helplessness was tricky, and there were no shortcuts.
A few teams didn’t want to buy in until the system was considered production stable. That’s understandable, but it’s difficult to square with the fog-of-war and progressive reification of patterns that we had to traverse, especially regarding infrastructural patterns. Describing the system as “a Google-style beta” seemed to satisfy most of these teams and get them on-board.
We also underestimated the importance of socializing infrastructural and on-call knowledge in the SRE team, where both Marcus and I were based. Two is the perfect team size for quickly developing and deploying a project like this, but two engineers isn’t enough to run the system in perpetuity. We should have brought in additional support earlier in the process, even informally, to expand the pool of engineers who were knowledgable about the system.
Alerting in the world of Prometheus is still a no-man’s land. Alertmanager is a powerful but half-finished product. We’ve patched it up around the edges to make it servicable, but it needs a great deal of love and attention before it reaches the level of engineering maturity that Prometheus clearly demonstrates.
Now, some things that worked really well, most of which I’ve mentioned in passing already.
A team of two was hugely productive. I think this is the perfect team size for a project of this scope in an organization the size of Fastly. Communication overhead costs are real and worth optimizing for.
The embedding/consultant model was successful, and I think is essential for any project of this scope. Neither carrots nor sticks, in isolation or in combination, can substantively change practices. Real change requires connection, understanding, and empathy.
Prometheus itself is a marvel of engineering: simple, stable, resource-efficient. It’s highly adaptable to a large number of deployment scenarios, and seems to play well in all of them. We’re very pleased with the choice.
GitOps-style resource management, where a Git repo is the source of truth for infrastructural configuration, definitely has rough edges, especially where it interfaces with Grafana, which has only just started being retrofit to support this style of workflow. But overall it’s been well-understood, especially by our engineers, and it seems to be the most correct pattern for infrastructure management. If you’re working on a project in this space, you should probably use GitOps to manage change. If you’re writing tools to serve this space, you need a strong story around repository-sourced resources. This means online reading resources from disk, a compact resource declaration format, robust (i.e. non-fatal) syntax and sanity checks, and so on.
So we’re in the final stretches now—famous last words, huh?—but all signs are positive. Hopefully I’ve given you some food for thought, and you can learn from our successes and mistakes.