This document discusses observability and how it differs from monitoring. It defines observability as being able to know almost everything happening in a system. Monitoring traditionally focused on basic checks, but modern distributed systems are more complex. Observability is needed for visibility into these complex systems across regions and datacenters. It allows for clarity, prevention of issues, stability, optimization, and insights from data. Observability requires both tools and a culture change, with a focus on communication, ownership, and empowerment between engineers. It involves measuring what you build, ensuring the best approach, and benefits for other engineers. Both open source and commercial tools can help with logging, performance, metrics, debugging, and tracing for observability.

1. Deden Fathurahman — $dedenf
Jenius Site Reliability Engineer Lead
BTPN
Observability
Within DevOps Organization

2. Population, mn
@dedenf
> whoami
@dedenf
notes.dedenf.com
$dedenf
Deden Fathurahman
Jenius site reliability engineer

3. Anything that can go wrong will go wrong
Murphy’s law

4. What is Observability?

5. Observability are the state when we are
able to know almost everything that
happen in our system.
~ me

6. wait!
Is that monitoring in a different language?
no, not really.

7. So what's the difference between
Observability and monitoring?

8. > in the old days, monitoring are Ops domain
> most of the time it's limited to only checks
it checks whether the machine are up, or the
network are ok, or the applications are
running.

9. These days applications are complex and got deployed on
distributed system mindset
how can you monitor all of these system that running to more than 10
instances?
Today’s Challenge
Accross region, accross datacenter
Can you Observe all of these thing?
What kind of output these system generated?
Will the output going to be useful for the organization?

10. Why do we need to have
Observability?

11. • Clarity and transparency
• Measurement and Prevention
• Stability & Optimization
• Data Insight
Why do we
need
Observability?

12. Observability are beyond
monitoring

13. So, how do we build/adopt Observability?

14. Observability is not about the tools
tools can change over time
it is about the people, the people who build the
system, the people who put their love on their
products.

15. Are we there yet?
Yes. Good!
if it’s not there,
how to change it or how do we get there?

16. Build engineering culture in the organization that cares
about the business and its surrounding.
First
Convince and get the team on board in this journey
Change the mindset, break the habits to implement a
new culture.

17. The engineers must expand their horizon of thought and
help others to be great at their jobs.
What mindset or culture are we talking?

18. Let’s break it down
As an engineer :
What kinda thing I want to improve?
Can I measure what I want to build?
Is this the best way to achieve this?
Can other engineer get the benefits from what I want to build?

19. Communication and participation creates Ownership,
Empathy and Empowerment.

20. To get better at Observability, you need tools or solution depending on our
needs.
Tooling
- Logging
- Performance Monitoring
- Metrics
- Debugging
- System Tracing

21. New relic, datadog, pagetduty, Grafana, Mochajs, testify,
ginko, circleCI, travisCI, Gitlab-ci/ Runner, Docker, ELK,
Zipkin, Finagle, Jenkins, Spinnaker, ATLAS, Kubernetes, Istio,
Prometheus, Mesos, DC/OS, Hadoop, R, Spark, etc.
Tools
These are the tools that usually used by engineers, commercial, opensource or both.

22. Always practice open communication within the org, adopt
devops, embrace engineering culture.
Final Thought

23. Question?

24. Download now and experience a new way of life
jenius.co
m