-
Notifications
You must be signed in to change notification settings - Fork 496
elastic_agent: changes for unified integration UI #2015
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
💚 Build Succeeded
Expand to view the summary
Build stats
Test stats 🧪
🤖 GitHub commentsTo re-run your PR in the CI, just comment with:
|
Pinging @elastic/ingest-management (Team:Ingest Management) |
Pinging @elastic/elastic-agent (Team:Elastic-Agent) |
Pinging @elastic/integrations (Team:Integrations) |
The elastic_agent packages collects logs and metrics from the Elastic Agent, see https://github.com/elastic/integrations/tree/master/packages/elastic_agent/data_stream I assume this should be mentioned in the title? |
@akshay-saraswat I'm going to change this to: |
Yes please! Thank you |
What does this PR do?
Align package title and description for improved Unified Integration UI display.
Checklist
I have reviewed tips for building integrations and this pull request is aligned with them.I have verified that all data streams collect metrics or logs.changelog.yml
file.If I'm introducing a new feature, I have modified the Kibana version constraint in my package'smanifest.yml
file to point to the latest Elastic stack release (e.g.^7.13.0
).Author's Checklist
How to test this PR locally
Related issues
Screenshots