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

[8.17] [Monitoring] Make monitoring collection API public again (#205190) #205199

Merged
merged 1 commit into from
Dec 27, 2024

Conversation

kibanamachine
Copy link
Contributor

Backport

This will backport the following commits from main to 8.17:

Questions ?

Please refer to the Backport tool documentation

)

Related to elastic#186882

## Summary

elastic#186781 required all teams to
make sure that all Kibana APIs in their respective plugins were using
the appropriate access `internal` or `public`.

PR elastic#186882 flagged the
`/api/monitoring_collection/{type}` API endpoint as `internal`. The
effect of that change was the [appearance of deprecation
logging](elastic#186882 (comment))
in Kibana logs, because that endpoint is called from the [`kibana`
Metricbeat
module](https://github.com/elastic/beats/blob/main/metricbeat/module/kibana/kibana.go#L42C1-L46C1)
in order to monitor Kibana.

For this reason, we need to change the access mode of that API endpoint
back to `public`.

(cherry picked from commit 52cab45)
@kibanamachine kibanamachine merged commit 78f7db8 into elastic:8.17 Dec 27, 2024
11 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants