-
Notifications
You must be signed in to change notification settings - Fork 121
Update custom metrics field to be optional
#1065
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
Conversation
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.
Pull Request Overview
This PR updates the SLO spec to accommodate optional values for the 'field' property in custom metrics SLO configurations. The key changes include:
- Updating the CHANGELOG to note that the 'field' property is now optional.
- Replacing direct type assertions on the 'field' property with the helper function getOrNilString in internal/kibana/slo.go.
Reviewed Changes
Copilot reviewed 8 out of 8 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
| CHANGELOG.md | Added an entry to document making the 'field' optional |
| internal/kibana/slo.go | Modified retrieval of 'field' values to handle nil properly |
field to be optional
|
The Kibana spec still lists |
|
So do the published docs |
|
Closing in favor of a larger PR that updates to the latest client |
This PR updates the SLO spec to make
fieldoptional when dealing with a custom metrics SLO. I have had to make a very unfortunate hack to the client from what appears to be a bug in the generator. It would be good to merge this in now and we can try and fix the upstream issue soon. We are likely due for some more changes to this resource so I think we will need to fix this sooner rather than later.