Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Observability within your DevOps Organization

Observability within your DevOps Organization

how your organization could look up your engineering, how to get better at it.
the mindset and tools

Deden Fathurahman

September 20, 2018
Tweet

Other Decks in Technology

Transcript

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

    View full-size slide

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

    View full-size slide

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

    View full-size slide

  4. What is Observability?

    View full-size slide

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

    View full-size slide

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

    View full-size slide

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

    View full-size slide

  8. > 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

    View full-size slide

  9. 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?

    View full-size slide

  10. Why do we need to have
    Observability?

    View full-size slide

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

    View full-size slide

  12. Observability are beyond
    monitoring

    View full-size slide

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

    View full-size slide

  14. 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

    View full-size slide

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

    View full-size slide

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

    View full-size slide

  17. 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?

    View full-size slide

  18. 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?

    View full-size slide

  19. Communication and participation
    create Ownership, Empathy &
    Empowerment

    View full-size slide

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

    View full-size slide

  21. 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.

    View full-size slide

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

    View full-size slide

  23. Download now and experience a new way of life
    jenius.com

    View full-size slide