Skip to content

feat(opensearch): add opensearch plugin for trace querying#23

Open
moshloop wants to merge 1 commit into
mainfrom
feat/opensearch-trace-querying
Open

feat(opensearch): add opensearch plugin for trace querying#23
moshloop wants to merge 1 commit into
mainfrom
feat/opensearch-trace-querying

Conversation

@moshloop
Copy link
Copy Markdown
Member

What

  • New OpenSearch plugin enabling profile-based trace querying for Mission Control
  • Generic trace query interface supporting multiple index formats (Jaeger, OTEL)
  • React-based UI with real-time query preview and result inspection
  • Connection validation and secure credential handling

Why

  • Enables trace querying capabilities within Mission Control's plugin ecosystem
  • Supports multiple OpenSearch index formats through configurable profiles

Notes

  • Plugin integrates with Mission Control's plugin SDK
  • Can be deployed as a standalone binary module
  • Includes predefined profiles for Jaeger and OTEL formats

Introduce a new OpenSearch plugin that enables profile-based trace querying for Mission Control. The plugin provides:

- Generic trace query interface supporting multiple OpenSearch index formats (Jaeger, OTEL)
- Profile-driven filtering and customizable table views
- React-based UI with real-time query preview and result inspection
- Connection validation and secure credential handling
- Configurable tracing profiles with field mappings and query parameters

The plugin integrates with Mission Control's plugin SDK and can be deployed as a standalone binary module.

Refs #opensearch
@moshloop moshloop requested a review from yashmehrotra May 21, 2026 14:15
@moshloop
Copy link
Copy Markdown
Member Author

This is was an initial extraction from oipa-cli https://github.com/flanksource/oipa-cli/blob/main/internal/trace/profiles/jms.incoming.disbursements.yaml. The profiles are designed to expose different "views" with different search params on a common opensearch index. and potential replace jaeger ui with a more customized search and trace viewer

  • Need to decide on wether to the create a plugin per Profile with different log providers built-in, or per log backend plugin and the a profile "plugin" that makes a plugin-to-plugin call.

@adityathebe @yashmehrotra wdyt ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants