Observability within your DevOps Organization

by Deden Fathurahman

Slide 1

Slide 1 text

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

Slide 2

Slide 2 text

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

Slide 3

Slide 3 text

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

Slide 4

Slide 4 text

What is Observability?

Slide 5

Slide 5 text

Observability in engineering perspective are the state when we are able to know and see almost everything that happen in our system. ~ me

Slide 6

Slide 6 text

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

Slide 7

Slide 7 text

So what's the difference between Observability and monitoring?

Slide 8

Slide 8 text

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

Slide 9

Slide 9 text

These days applications are complex and got deployed on distributed system mindset. How you monitor all of these systems that running to more than 10 or 40 instances or more? Imagine you have lots of microservices running on it. Today’s Challenge Across the region, across the datacenter. Can you Observe all of these things? What kind of output these system generated? Will the output going to be useful for the organization?

Slide 10

Slide 10 text

Why do we need to have Observability?

Slide 11

Slide 11 text

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

Slide 12

Slide 12 text

Observability are beyond monitoring

Slide 13

Slide 13 text

So, how do we build/adopt Observability?

Slide 14

Slide 14 text

Observability is not all about the tools tools can change over time it’s about the people, the people who build the systems, the people who put their love on their products

Slide 15

Slide 15 text

Are we there yet? Yes. Good! if we’re not there, yet, how to change and how do we get there?

Slide 16

Slide 16 text

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 this new culture.

Slide 17

Slide 17 text

The engineers must expand their horizon of thought and help other engineer or team member to be great at their job. What mindset or culture are we talking?

Slide 18

Slide 18 text

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

Slide 19

Slide 19 text

Communication and participation create Ownership, Empathy & Empowerment

Slide 20

Slide 20 text

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

Slide 21

Slide 21 text

New relic, Datadog, Pagetduty, Grafana, Mochajs, Testify, Ginko, CircleCI, TravisCI, Gitlab Runner, Docker, ELK, Zipkin, Finagle, Jenkins, Spinnaker, ATLAS, Kubernetes, Istio, Prometheus, Mesos, DC/OS, Hadoop, R, Spark, Openshift, etc. Tools Some of the tools that usually used by engineers. commercial, opensource or both.

Slide 22

Slide 22 text

Always practice Agile within the org, adopt devops, embrace the engineering culture. Final Thought