-
Notifications
You must be signed in to change notification settings - Fork 462
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
Update title and description based on guidelines for Elastic Agent based Observability integrations #1901
Comments
I recommend we change "Apache" to "Apache HTTPD" or "Apache HTTP Server" to distinguish it from other Apache packages like "Apache Tomcat". |
Here is the spreadsheet with new Titles and Descriptions. Please review and update the codebase accordingly. Thanks! |
Will keep here a list of packages requiring promotion Progress can be followed through this project: https://github.com/elastic/integrations/projects/1 |
Pinging @elastic/integrations (Team:Integrations) |
All PR merged, @akshay-saraswat I think this can be closed now 🎉 |
(note that not all packages have been promoted to production already) |
Release to production will be managed separately, closing this as all required changes have been merged. |
Set description to "Collect logs from journald with Elastic Agent." Relates: elastic#1901
Set description to "Collect logs from journald with Elastic Agent." Relates: #1901
Set description to "Collect logs from journald with Elastic Agent." Relates: elastic#1901
In 7.16, we are planning to introduce the unified integrations view. The primary goal of this view is to improve the discoverability for all data ingest options at Elastic. As part of this initiative, we'd like to improve the titles and descriptions of each integration card and do so in a uniform way.
Guidelines
These are the general guidelines we plan to use for the integration cards
Elastic Agent example
Here's an example for how agent can leverage these guidelines, but please follow the guidelines as you see fit.
The text was updated successfully, but these errors were encountered: