Observability Channel Welcome Message

Hi @channel, thanks for your interest to help us improving Traveloka incident handling towards your own domain (product/platform). We invited you here based on the last question on the survey 2 weeks ago. The main reasons for having this channel are:

establishing communication channel to share progress, problems, and plan
getting more reviewers for the ideas/deliverables/results
spreading the knowledge so that many people can maintain and iterate the solution (prevent SPOF)

So, you can also invite anyone else who you think are willing to contribute too.

The document is at: https://docs.google.com/document/d/1XIdW6ROLjlI1gIewB3irj7Fue5fULgj2AMK8f-YooDQ and we have prepared a Confluence space at: https://29022131.atlassian.net/wiki/spaces/IHP/overview. We will utilize this channel as a medium for us to explore best practice in System Observability, including and not limited to:

Incident Handling best practice
Post-mortem best practice
Monitoring best practice
Logging best practice
Alerting best practice
Improving RAS best practice

Also, everyone is free to share their takeaways on his/her team's past incidents about:

What helps you in detecting the incident
Gotchas during development that we must all beware of
Learnings that has been gained after the incident, etc
Low effort action that should have been applied to minimize incident impact

Please enjoy this forum and be open to new learnings from all our domains so that we can learn and apply those in our respective teams.