The OpenSearch Catalog is designed to make it easier for developers and community to contribute, search and install artifacts like plugins, visualization dashboards, ingestion to visualization content packs (data pipeline configurations, normalization, ingestion, dashboards).
Today the Integrations catalog are becoming more popular due to its simple installation and opinionated schema governed by the Otel protocol.
Each integration has a TryMe button that has a small dataset which functions as a mock data-points for the dashboard to show some minimal visual appearance.
The need for a comprehensive documentation and instruction (including scripts or live docker image) of how to actually add the agent on top of the observed service, how to map the resulting logs into the Otel (simple schema) format and the actual setup of the agent that will be responsible of the data shipping is not covered and very much missing.
What solution would you like?
This is a proposal for the content of such getting-started template and format that will lead to a catalog of getting started component that are accompanied with the following :
Documentation of the agent
Instruction for setting up the agent
Documentation service's log format
Instruction for transforming the log's format into Otel designated format
Documentation of the agent's shipping method and recommendations
Instruction for setting up the agent's logs delivery
Each such component will have the following relationships:
Associated Integrations
Associated index name / index mapping (related to the signal type)
Associated Docker-compose (live sample) that showcase all the instructions and can be run and ingest data using some build in mock that activate the monitored service
Do you have any additional context?
Here is the suggested getting-started format that can be later processed by a UX visualization and allow customer interaction.
Is your feature request related to a problem?
Today the Integrations catalog are becoming more popular due to its simple installation and opinionated schema governed by the Otel protocol. Each integration has a
TryMe
button that has a small dataset which functions as a mock data-points for the dashboard to show some minimal visual appearance.The need for a comprehensive documentation and instruction (including scripts or live docker image) of how to actually add the agent on top of the observed service, how to map the resulting logs into the Otel (simple schema) format and the actual setup of the agent that will be responsible of the data shipping is not covered and very much missing.
What solution would you like? This is a proposal for the content of such
getting-started
template and format that will lead to a catalog of getting started component that are accompanied with the following :Each such component will have the following relationships:
Do you have any additional context? Here is the suggested
getting-started
format that can be later processed by a UX visualization and allow customer interaction.Workflow
: list of steps including description and scripts to follow for making the service's log ingested correctlystatics
: list of visual logo to show with this component's UX dialogrelatedAssets
: list of related components that are associated with this service such as integrations, alerts, queries