Skip to content
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

Merged
merged 5 commits into from Apr 7, 2020
Merged

SIG Observability Charter #1

merged 5 commits into from Apr 7, 2020

Conversation

halcyondude
Copy link
Collaborator

@halcyondude halcyondude commented Mar 3, 2020

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
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)
@halcyondude halcyondude requested a review from amye Mar 3, 2020
@halcyondude halcyondude self-assigned this Mar 3, 2020
@halcyondude halcyondude added this to Backlog in TAG Observability Kanban via automation Mar 3, 2020
@halcyondude halcyondude moved this from Backlog to In Progress in TAG Observability Kanban Mar 3, 2020
@halcyondude halcyondude moved this from In Progress to Pending Review in TAG Observability Kanban Mar 3, 2020

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
Copy link
Collaborator

@mhausenblas mhausenblas Mar 3, 2020

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?

Copy link
Collaborator

@bwplotka bwplotka Mar 3, 2020

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

observability-charter.md Show resolved Hide resolved

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
Copy link
Collaborator

@bwplotka bwplotka Mar 3, 2020

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

observability-charter.md Outdated Show resolved Hide resolved
observability-charter.md Outdated Show resolved Hide resolved
observability-charter.md Outdated Show resolved Hide resolved
observability-charter.md Outdated Show resolved Hide resolved
observability-charter.md Outdated Show resolved Hide resolved
observability-charter.md Outdated Show resolved Hide resolved
Copy link
Collaborator

@bwplotka bwplotka left a comment

Amazing work @halcyondude 💪 👍

Thanks for this, some suggestions, mostly tiny typos. Otherwise LGTM.

observability-charter.md Outdated Show resolved Hide resolved
observability-charter.md Outdated Show resolved Hide resolved
observability-charter.md Show resolved Hide resolved
observability-charter.md Outdated Show resolved Hide resolved
observability-charter.md Outdated Show resolved Hide resolved
observability-charter.md Outdated Show resolved Hide resolved
observability-charter.md Outdated Show resolved Hide resolved
observability-charter.md Outdated Show resolved Hide resolved
observability-charter.md Show resolved Hide resolved
observability-charter.md Outdated Show resolved Hide resolved
Copy link
Collaborator

@bwplotka bwplotka left a comment

👍

observability-charter.md Show resolved Hide resolved
observability-charter.md Show resolved Hide resolved
observability-charter.md Show resolved Hide resolved
observability-charter.md Show resolved Hide resolved
observability-charter.md Show resolved Hide resolved
observability-charter.md Show resolved Hide resolved
Copy link
Member

@michelleN michelleN left a comment

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
Copy link
Member

@michelleN michelleN Mar 12, 2020

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍

@bwplotka
Copy link
Collaborator

@bwplotka bwplotka commented Mar 19, 2020

Thanks @michelleN, what would be the next step? Does it mean we can... start? 🎉

@amye
Copy link
Contributor

@amye amye commented Mar 19, 2020

Still need a TOC Liaison to help me call for a vote. :)

@halcyondude
Copy link
Collaborator Author

@halcyondude halcyondude commented Apr 1, 2020

Still need a TOC Liaison to help me call for a vote. :)

It looks like we have one :)

@halcyondude halcyondude force-pushed the sig-observability-charter branch from 9242c69 to 94d29b2 Compare Apr 1, 2020
@@ -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)
Copy link
Collaborator

@RichiH RichiH Apr 1, 2020

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Woop woop!

Copy link
Collaborator

@bwplotka bwplotka Apr 1, 2020

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
Copy link

@flands flands Apr 1, 2020

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]: @

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
[Tigran Najaryan]: @
[Tigran Najaryan]: https://github.com/tigrannajaryan/

@halcyondude
Copy link
Collaborator Author

@halcyondude halcyondude commented Apr 7, 2020

Just last night the vote become official! Merging the charter now :)

https://lists.cncf.io/g/cncf-toc/message/4515

@halcyondude halcyondude merged commit 733973a into master Apr 7, 2020
TAG Observability Kanban automation moved this from Pending Review to Done / Merged Apr 7, 2020
bwplotka pushed a commit that referenced this issue Jun 30, 2021
@halcyondude halcyondude deleted the sig-observability-charter branch Mar 7, 2022
halcyondude pushed a commit that referenced this issue Apr 7, 2022
Updated settings.yml with my user info
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
TAG Observability Kanban
  
Done / Merged
Development

Successfully merging this pull request may close these issues.

None yet

9 participants