New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SIG Observability Charter #1
Conversation
This SIG focuses on topics pertaining to the observation of cloud native workloads. Additionally, it produces supporting material and best practices for end-users and provides guidance and coordination for CNCF projects working within the SIG’s scope. This document is the result of working sessions: 2/14/2020, 8:00-9:00 am (US Pacific), 11:00-12:00 (US East) 2/21/2020, 9:00-10:00 am (US Pacific), 12:00-1:00 (US East) 2/28/2020, 8:00-9:00 am (US Pacific), 11:00-12:00 (US East)
|
||
This [SIG] focuses on topics pertaining to the observation | ||
of [cloud native][cn-def] workloads. Additionally, it produces supporting | ||
material and best practices for end-users and provides guidance and |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'd still prefer "good practices" over "best practices". Software engineering (not even talking about cloud native yet) is in itself a very young discipline. While established disciplines such as civil engineering benefit from centuries of insights what (absolutely) worked and what not, they are indeed in a position to declare a certain practice as the "best". I do, with all optimism mustered, not believe we are in this position. We can, however, identify and describe good practices: "this worked for X in context Y". WDYT?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
My 2 cents:
- I believe that it's super tiny detail (:
- I am not a native English speaker, but I never heard the term "good" practice in this context. We always say "best practices". It does not mean "super super optimal and for sure the best, and there is no way there is better" 🙃
- I believe we still aim for "best" practices even in the sense you described. I think about it this way: We are not the smartest in the world, but to our knowledge the X is the best practice in context of Y. If you think otherwise, tell us - we would love to learn. If the arguments win we move to Z, which will become new best practices! (: Can't see anything wrong with aiming for the best.
My vote is to leave best
as we are always aiming for best (best to our, CNCF and community knowledge).
|
||
This [SIG] focuses on topics pertaining to the observation | ||
of [cloud native][cn-def] workloads. Additionally, it produces supporting | ||
material and best practices for end-users and provides guidance and |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
My 2 cents:
- I believe that it's super tiny detail (:
- I am not a native English speaker, but I never heard the term "good" practice in this context. We always say "best practices". It does not mean "super super optimal and for sure the best, and there is no way there is better" 🙃
- I believe we still aim for "best" practices even in the sense you described. I think about it this way: We are not the smartest in the world, but to our knowledge the X is the best practice in context of Y. If you think otherwise, tell us - we would love to learn. If the arguments win we move to Z, which will become new best practices! (: Can't see anything wrong with aiming for the best.
My vote is to leave best
as we are always aiming for best (best to our, CNCF and community knowledge).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks great! Thank you!
observability data such as: | ||
- ML, model training, Bayesian networks, and other data science techniques | ||
that enable anomaly & intrusion detection. | ||
- Correlating resource consumption with costing data to reduce the total cost |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍
Thanks @michelleN, what would be the next step? Does it mean we can... start? 🎉 |
Still need a TOC Liaison to help me call for a vote. :) |
It looks like we have one :) |
9242c69
to
94d29b2
Compare
@@ -189,14 +189,12 @@ Examples include: | |||
_Note: all of the roles below are initial proposals and must be accepted by the TOC per formation process_ | |||
|
|||
- Proposed [Roles][sigroles] for SIG Observability | |||
- TOC Liaison: *Jeff Brewer*\* | |||
- TOC Liaison: [Brendan Burns](https://github.com/brendandburns) (bburns@microsoft.com) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Woop woop!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
❤️
- SIG Chairs: pending TOC guidance | ||
- _Nominated by the charter working group or self:_ Matt Young, Richard Hartmann, Steve Flanders, *Ricardo Aravena*\* | ||
- Tech Leads: pending TOC guidance | ||
- _Nominated by the charter working group or self:_ Bartłomiej Płotka, *Richard Hartmann*\*, Michael Hausenblas, Alois Reitbauer |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nominate: Tigran Najaryan
[Sergey Kanzhelev]: @ | ||
[Steve Flanders]: https://github.com/flands | ||
[Ted Young]: @ | ||
[Tigran Najaryan]: @ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
[Tigran Najaryan]: @ | |
[Tigran Najaryan]: https://github.com/tigrannajaryan/ |
Just last night the vote become official! Merging the charter now :) |
Updated settings.yml with my user info
This SIG focuses on topics pertaining to the observation of cloud native
workloads. Additionally, it produces supporting material and best
practices for end-users and provides guidance and coordination for
CNCF projects working within the SIG’s scope.
This document is the result of working sessions:
2/14/2020, 8:00-9:00 am (US Pacific), 11:00-12:00 (US East)
2/21/2020, 9:00-10:00 am (US Pacific), 12:00-1:00 (US East)
2/28/2020, 8:00-9:00 am (US Pacific), 11:00-12:00 (US East)