-
Notifications
You must be signed in to change notification settings - Fork 8.1k
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
[Stack Monitoring] support for integration package #138224
Conversation
Pinging @elastic/infra-monitoring-ui (Team:Infra Monitoring UI) |
@elasticmachine merge upstream |
@elasticmachine merge upstream |
💚 Build Succeeded
Metrics [docs]Async chunks
History
To update your PR or re-run it, just comment with: cc @klacabane |
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.
LGTM 👍🏼 Tested locally and couldn't see any issues in the UI.
Summary
This change should be tested with elastic/integrations#3965
Two updates required to support the kibana integration package:
Testing
localhost:5602
. Stack Monitoring should already have elasticsearch and kibana data, verify all kibana views are correctly populatedNote that the local kibana is not able to interact with the local package-registry when running http, this means we have to do all integration-related interaction on the kibana run by elastic-package (at :5601).
To enable ssl we can point the local kibana configuration to the certificates used by elastic-package (under
~/.elastic-package/profiles/{profile}/certs
), then start the process withNODE_EXTRA_CA_CERTS=~/.elastic-package/profiles/{profile}/certs/ca-cert.pem yarn start
. With that everything appears to work well except that any successful update to an agent policy from the local kibana is not picked up by the Agent, only the elastic-package updates go through. I didn't find the cause yet