add flow based use case integration #149
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: YANGDB <yang.db.dev@gmail.com>
YANG-DB
requested review from
bowenlan-amzn,
khushbr,
praveensameneni,
ananzh and
AMoo-Miki
as code owners
YANG-DB
added
enhancement
Signed-off-by: YANGDB <yang.db.dev@gmail.com>
Signed-off-by: YANGDB <yang.db.dev@gmail.com>
Signed-off-by: YANGDB <yang.db.dev@gmail.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
The Otel Flow Use Case Widget for OpenSearch Dashboards uses Vega for complex visualization of Use case user flow interactions.
It's designed to map out use-case steps and associate them with specific dashboards and allow filter carry over to drive the flow ahead
The flow data arrives from the OpenTelementry collector pipline which exports the signals into data preper
Vega Integration
Vega's integration allows for customized, interactive flow creation, enabling detailed visual analysis and linking different dashboards representing steps in the flow.
Data Model
This vega flow component is build using a flow specification which describes the different steps which compose the flow, in our otel example case,
it has the following structure:
Issues Resolved
List any issues this PR will resolve, e.g. Closes [...].
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.