You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Nobl9 requires a few things that the OpenSLO spec does not support. However, for the use case of someone keeping the source of truth in OpenSLO and converting to Nobl9, we don't have a good way of providing those values, outside of manual updating.
Example:
The MetricSourceSpechere has Name and Kind that we need to add when assigning here
Proposal
It would be ideal to have a way to provide inline attributes that are not part of the OpenSLO spec to give hints to the converter to include in the output. We don't want to add these to the spec structs tho, since they are not part of the spec.
Another option is to use something like yk to merge the output with an override file, though this way is less than ideal since its brittle
The text was updated successfully, but these errors were encountered:
Problem to solve
Nobl9 requires a few things that the OpenSLO spec does not support. However, for the use case of someone keeping the source of truth in OpenSLO and converting to Nobl9, we don't have a good way of providing those values, outside of manual updating.
Example:
The
MetricSourceSpec
here hasName
andKind
that we need to add when assigning hereProposal
It would be ideal to have a way to provide inline attributes that are not part of the OpenSLO spec to give hints to the converter to include in the output. We don't want to add these to the spec structs tho, since they are not part of the spec.
Another option is to use something like yk to merge the output with an override file, though this way is less than ideal since its brittle
The text was updated successfully, but these errors were encountered: