-
Notifications
You must be signed in to change notification settings - Fork 36
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
Generators #34
Comments
Yeah, this is something that we are talking about. It would be great to have olso be able to generate SLOs. |
@ian-bartholomew It generates some interesting discussion around spec constructs, as I mentioned in OpenSLO/OpenSLO#29 , there might need to be a bit more consistency in the constructs of the spec in order to be able to allow the spec to translate to actionable SLOs for platforms, and vice versa. Additionally, I think this may lead back to the discussion that led to you creating OpenSLO/OpenSLO#27 as well |
@its02003 yeah, you are correct. We have a number of prerequisites to address before we can do it |
Mind if we list those in this issue? We can build out the list as we identify more |
@ian-bartholomew thoughts on the idea of tracking the prerequisites here? |
@ian-bartholomew I added this as a pre-requisite on the issue. I think it might make sense to spend a moment defining what is considered unstable about the spec and when it might be considered "stable" |
Did the concept of platform specific generators ever come up with regards to oslo?
It would be nice to see a community supported set of assets for transforming OpenSLO compliant SLOs into operational measures on Splunk, Dynatrace, etc etc
I feel like most implementations will create these anyways, so why not make it open... thinking like a "galaxy" style or something. Happy to work out a few initial implementations if people think its a good idea to include in the scope of the project.
If not, would really love to hear why.
Prereqs before Generators can be discussed
The text was updated successfully, but these errors were encountered: