SignalFx, a Splunk company | Poland
TALK: 5 reasons why teams don’t buy in the observability hype
Session level: intermediate
Many articles on observability express the opinion that observability is yet another buzzword concocted only because people in software companies got bored with monitoring and logs. Guess what: calling it “observability” didn’t help. Now we are bored and fatigued with observability requirements, despite having observability related tasks all over our backlogs: adding new metrics, trying to understand what just happened in a system, cleaning up logs, debugging issues in production, fixing dashboards (isn’t that third time this month?). Does the work around observability really need to be tedious, boring and repetitive?
- You won’t get observability by accident or as a byproduct. In highly dynamic and complex environment, achieving observability can be difficult.
- Many teams deal with similar problems implementing monitoring and tracing. Even simply knowing the concepts and the vocabulary to describe common challenges can help you find and evaluate solutions.
- The observability tooling supports automation. With scale, there comes a time to use it.