-
Notifications
You must be signed in to change notification settings - Fork 100
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
Support otel metrics mapping #1397
Support otel metrics mapping #1397
Conversation
Signed-off-by: YANGDB <[email protected]>
Signed-off-by: YANGDB <[email protected]> Signed-off-by: YANGDB <[email protected]>
… Support-OTEL-Trace-mapping # Conflicts: # schema/traces/README.md # schema/traces/traces.mapping # schema/traces/traces.schema
… Support-OTEL-Trace-mapping Signed-off-by: YANGDB <[email protected]> # Conflicts: # schema/traces/README.md # schema/traces/traces.mapping # schema/traces/traces.schema
… Support-OTEL-Trace-mapping # Conflicts: # schema/traces/traces.schema
…butes Signed-off-by: YANGDB <[email protected]>
… Support-OTEL-Trace-mapping
…L compliant) Signed-off-by: YANGDB <[email protected]>
…L compliant) Signed-off-by: YANGDB <[email protected]>
…to Support-OTEL-Metrics-mapping # Conflicts: # schema/metrics/README.md # schema/metrics/metrics.schema
Signed-off-by: YANGDB <[email protected]>
…to Support-OTEL-Metrics-mapping
Signed-off-by: YANGDB <[email protected]>
…to Support-OTEL-Metrics-mapping
rename metrics type to kind Signed-off-by: YANGDB <[email protected]>
…to Support-OTEL-Metrics-mapping
Signed-off-by: YANGDB <[email protected]>
…to Support-OTEL-Metrics-mapping
Signed-off-by: YANGDB <[email protected]>
…to Support-OTEL-Metrics-mapping
Signed-off-by: YANGDB <[email protected]>
…to Support-OTEL-Metrics-mapping
Signed-off-by: YANGDB <[email protected]>
…to Support-OTEL-Metrics-mapping
Signed-off-by: YANGDB <[email protected]>
…to Support-OTEL-Metrics-mapping
Signed-off-by: YANGDB <[email protected]>
…to Support-OTEL-Metrics-mapping
src/main/kotlin/org/opensearch/observability/index/ObservabilityMetricsIndex.kt
Outdated
Show resolved
Hide resolved
Signed-off-by: YANGDB <[email protected]>
…to Support-OTEL-Metrics-mapping
@YANG-DB what if user's use data_prepper -> Opensearch without the observability plugin? Without the plugin user will not have the template and thus data stream creation would most likely fail... how would we handle this case? What i'm getting at is what if observability plugin is added later? Should we have this template live somewhere global? Is that even possible? |
Q: 'what if user's use data_prepper -> Opensearch without the observability plugin?' |
Ok makes sense I am not sure how that will work though... but let's create an issue either here or data prepper repo to track that edge case - where do you think it belongs? |
its an issue for data-prepper... |
Signed-off-by: YANGDB <[email protected]>
…to Support-OTEL-Metrics-mapping
Signed-off-by: YANGDB <[email protected]>
…to Support-OTEL-Metrics-mapping
Please take care of build failures. |
Signed-off-by: YANGDB <[email protected]>
…to Support-OTEL-Metrics-mapping
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The BWC tests are failing as link to 2.6.0 artifact is not working. This may be due to build failures in jenkins ci [caused by other plugins or upstream]
/** | ||
* once lifecycle indicate start has occurred - instantiating system index creation | ||
*/ | ||
override fun afterStart() { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
When does this get triggered?
Is this after node startup or cluster startup.
If it is after node startup, is to ok to create an index if other nodes are still booting up.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is triggered from the observability plugin class that implements the cluster listener and registers the node started method - anyhow the index will not be created since the plugins are responsible of creating the index by posting data to the named index that follows the index pattern stated in the template created by this api
return emptyList() | ||
} | ||
|
||
override fun onNodeStarted() { | ||
ObservabilityIndex.afterStart() |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If we are triggering this method ourselves, why do we want to extend LifecycleListener in ObservabilityIndex class.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
correct - I'll update this...
Not relevant anymore once integration was introduced into 2.x. branch |
Description
Simple Schema for Observability - SSO - will support the 3 major Observability types:
SSO will comply with the OTEL schema and continue supporting proprietary index structure
Content
In addition to the simple schema for Observability metrics signal definition, this PR creates the following during Plugin initiation:
Issues Resolved
Check List
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.