Whitepaper on cloud-native observability about tag-observability HOT 15 CLOSED

We would need to define the categories for the landscape first. Observability is a too broad and abstract term.

from tag-observability.

I've finished reorganizing the sessions. Several comments were added to the doc with a brief explanation about the newly added sessions.
@mhausenblas @sferlin @danielkhan (or anyone else interested), feel free to review and to ping me on slack if there are any doubts.

from tag-observability.

The coordination and collaboration is happening in Google Doc and Slack, using this issue for high level tracking.

from tag-observability.

Hi all, hope you are all great!

Thanks everybody for help and feedback. It's finally time to claim that v1.0 version of the whitepaper we started long time ago!

To do so we have to perform final touches and review. For that, we created this document, which is now open for review. The aim is to have the final version of whitepaper with addressed TODOs done by 1st August. After that we will share it wider, save as official v1 and open WIP version for v1.1, so we can continuously evolve it with more content and updates community can bring next months! (:

Final review document holds the latest whitepaper version (copied from this version) available for collaborative review and addressing TODOs. Feel free to add comments & suggestions. For bigger suggestions (e.g. further details or new sections), we might pull them new GH issues for whitepaper v1.1. The doc also outlines all feedback items we got so far to consider. Feel free to help in any of those TODOs and, generally, in final review of this paper 🤗

Thanks! 💪🏽

from tag-observability.

That sounds like a really good idea to me and I'm happy to contribute to this.

from tag-observability.

+1 to this.

A good first step may be a landscape, just to have all "players", from open-source and cloud-native, all the way to hosted SaaS options.

from tag-observability.

I am also happy to contribute to this.
Is there any reason to use different categories than the categories defined in the official CNCF landscape's Observability & Analysis category?
Monitoring, logging and tracing can cover most aspects of the term, maybe Chaos Engineering is a bit of an outlier, but also can be included if this SIG would want to cover that as well.

from tag-observability.

@mhausenblas, @sferlin, @ArthurSens, and @danielkhan met today to agree on a rough outline and schedule.

We plan to have the draft ready for review by January 19th and a final version in February.
@ArthurSens already kicked off a google doc and we will continue to work in this doc.

from tag-observability.

It's worth mentioning that the organization of the sessions was inspired by the whitepaper that is under work by the SIG-Security

from tag-observability.

"Goals" and "Target Audience" ready for review :)

from tag-observability.

"Introduction" ready for review 🙂

from tag-observability.

A couple of thoughts...

• In the current structure, there is so much emphasis on different signals (metrics, traces, logs and more) but not a lot of structure to explain how observability goals make you change the way you collect these signals. For example, you collect things consistently with the same labels (dimensions) and later can narrow down the data by filtering the same labels.
• Context propagation is very critical component in observability from the perspective of propagated labels and trace/request context. The paper may need a section dedicated to context (both in-process and on wire).
• The paper should include a high-level section what observability enables. For example, response time to an incident can be improved from hours to minutes. Observability can help onboarding new engineers in relative large systems. Observability can contribute to the efficiency of your infrastructure and help you optimize (not just performance-wise but also costs-wise). It can help identifying malicious cases and security attacks. A section with a list of various things observability can contribute would be great.
• The paper also can have a more compelling section of software lifecycle and how observability fits. From development, to deployment, to production, observability has unique contributions. A high-level overview would be great to capture.

from tag-observability.

Thank you for the feedback, Jaana.

• Context propagation is very critical component in observability from the perspective of propagated labels and trace/request context. The paper may need a section dedicated to context (both in-process and on wire).

I could not participate as it got unexpectedly busy but I can take a stab on this within the next two weeks if no one else is already working on this.

from tag-observability.

Hi everyone,

I would love to contribute to this. I see the last actions were last taken in April 2021. Where is the Whitepaper at in the process?

from tag-observability.

Is "Make your Kubernetes cluster - and the apps running on it - obseravable" mentioned above still a goal of the observability whitepaper?

from tag-observability.