We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Is your feature request related to a problem? Jaeger indices are currently time indices and explicitly state time as part of the index name (https://opensearch.org/docs/latest/observing-your-data/trace/trace-analytics-jaeger/#setting-up-opensearch-to-use-jaeger-data)
This is something of an anti-pattern and is recommended to avoid in favour of data-streams
What solution would you like? Create jaeger based index pattern for use that has an explicit definition of data-stream
What alternatives have you considered? N/A
Do you have any additional context?
The text was updated successfully, but these errors were encountered:
YANG-DB
No branches or pull requests
Is your feature request related to a problem?
Jaeger indices are currently time indices and explicitly state time as part of the index name (https://opensearch.org/docs/latest/observing-your-data/trace/trace-analytics-jaeger/#setting-up-opensearch-to-use-jaeger-data)
This is something of an anti-pattern and is recommended to avoid in favour of data-streams
What solution would you like?
Create jaeger based index pattern for use that has an explicit definition of data-stream
What alternatives have you considered?
N/A
Do you have any additional context?
The text was updated successfully, but these errors were encountered: