-
Notifications
You must be signed in to change notification settings - Fork 3.7k
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
Add OpenTelemetry Proto Metrics Reader Extension #17668
base: master
Are you sure you want to change the base?
Add OpenTelemetry Proto Metrics Reader Extension #17668
Conversation
We already an extensions named as Since the extension supports ingestion data in the opentelemetry proto format, maybe we can rename it as `druid-opentelemetry-metric-extensions' or sth else. |
Right now, this extension supports ingestion of protobuf OTLP Metrics events. Let me know if this makes sense. |
From the general software design principle, it makes sense to leave a room to add trace and span logs in future. However, from reality, I would like to argue that if Druid is the right choice for span logs. For span logs, scan queries or point queries are mainly involved, and because Druid lacks rerverted index, bloom filter index, serving these needs would not be a good idea. And now, i also don't see Druid has any plan on the the index or storage layer to support these scenarios. |
@FrankChen021, As per your suggestion, I have renamed the extension. |
}); | ||
break; | ||
} | ||
// TODO Support HISTOGRAM and SUMMARY metrics |
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.
We donot add todo's in the production code.
Just mention that we donot support histogram and summary and document it as part of the readme.
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.
removed the ToDos and added the supported metrics and data types in readme.
case STRING_VALUE: | ||
return value.getStringValue(); | ||
|
||
// TODO: Support KVLIST_VALUE, ARRAY_VALUE and BYTES_VALUE |
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.
Same comment as above.
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.
removed the ToDos and added the supported metrics and data types in readme.
@@ -0,0 +1,442 @@ | |||
/* |
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.
- Could you please add a proto file to the test/resources and try to read it from from there ? It can be a new test case as well .
- Add tests cases for unsupported columns/data types
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.
- Added
- The test cases are already present for unsupported metric/data types
Fixes #17644.
Description
Release note
druid-opentelemetry-extensions
, has been added to enable ingestion of metrics in OpenTelemetry Protocol (OTLP) format.This PR has: