-
Notifications
You must be signed in to change notification settings - Fork 726
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
Set basePath in Metricbeat when using stack monitoring #8311
Conversation
buildkite test this -f t=Test.*StackMonitoring -m s=7.17.25,s=8.15.4 |
buildkite test this -f p=gke,t=Test.*StackMonitoring -m s=8.16.0,s=7.17.25,s=8.15.4 |
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.
Looks good 👌
@@ -29,6 +29,7 @@ func NewMetricBeatSidecar( | |||
baseConfigTemplate string, | |||
namer name.Namer, | |||
url string, | |||
basePath string, |
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.
NewMetricBeatSidecar(..)
and buildMetricbeatBaseConfig(..)
start to have a lot of parameters. At some point, it might be reasonable to introduce a struct?
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.
I think fundamentally basePath should not be in the common stack monitoring code. But I wanted a quick fix we could include in the release. Ideally one would want a bit more more modular code where we can have application/module specific settings in the specific controllers.
Ensure stack monitoring works when Kibana is configured with a basePath parameter. (cherry picked from commit eadb46d)
💚 All backports created successfully
Questions ?Please refer to the Backport tool documentation |
Fixes #8310