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

Introduce real-world examples and contexts for OpenSLO spec, definitions, features, etc. #174

Open
programmer04 opened this issue Sep 16, 2022 · 5 comments
Labels
documentation Improvements or additions to documentation enhancement New feature or request help wanted Extra attention is needed

Comments

@programmer04
Copy link
Member

Problem to solve

Some features of the spec introduce some more sophisticated features. Those without additional context may not be understood correctly by newbies or seems odd (e.g. taking a list as an input instead of a single item).

They aren't aware of how common the use case it is in a real-world scenario for a particular feature that is obvious for veterans in defining SLOs. For instance, having multiple objectives in one SLO is pretty common - tighter for internal use and looser for external use. Or defining multiple time windows - shorter for quick, internal feedback for teams, and longer for external use. There are countless examples like that.

By having them documented somewhere we also spread more awareness and educate people about SLO.

Proposal

Plenty of repositories have folder examples where such stuff is put. We should put heavily commented YAMLs that represent real-world scenarios. Also, additional text that describes more details, context, use cases, etc. Referencing literature e.g. SRE Books that are available online and acclaimed would be great too.

Next, we should link to them from the main page of the spec when more complicated features are specified. For instance by putting something like that

To learn more about use-case for this feature check [link-to-specifc-doc-from-example-dir].

Some minimal examples that use only basic features can be included in this example dir too.

@programmer04 programmer04 added the enhancement New feature or request label Sep 16, 2022
@fearfactor3
Copy link
Contributor

fearfactor3 commented Oct 8, 2022

I can start adding some of the real-world examples that we use and modify them for the example dir.

@programmer04
Copy link
Member Author

It's a great idea @fearfactor3! Please remember to add some short note for your definitions that answers the questions

  • What are you measuring?
  • Why are you measuring this?
  • How it helps with providing a reliable platform to end users?
  • Whatever seems right for you 🙂

I think it'll educate people and help with better understanding because we don't want to have a steep learning curve with SLOs.

What do you think?

@programmer04 programmer04 added documentation Improvements or additions to documentation help wanted Extra attention is needed labels Dec 9, 2022
@programmer04
Copy link
Member Author

I think the scope of this issue contains what you proposed in #40 @ian-bartholomew could we close it to avoid duplication?

@fearfactor3
Copy link
Contributor

@fpiwowarczyk - I've looked at your example and I like how you set it up. Do you mind if use your template for what I plan to do with this?

@fpiwowarczyk
Copy link
Member

@fearfactor3 no problem at all :) we can say it is opensource :D

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation enhancement New feature or request help wanted Extra attention is needed
Projects
Status: In Progress
Development

No branches or pull requests

3 participants