-
Notifications
You must be signed in to change notification settings - Fork 304
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
HPCC-31025 Add support for multiple trace exporters #18149
Conversation
https://track.hpccsystems.com/browse/HPCC-30125 |
@rpastrana I realised I didn't update the schema or readme to include "exporters". I will do that later. |
316a1b3
to
c0b8cbb
Compare
https://track.hpccsystems.com/browse/HPCC-31025 |
I tested by adding a jlog exporter twice. Would probably benefit form more testing. |
Another problem is that exporter: type=none should suppress the creation of the jlog exporter. Actually this needs a little more discussion. |
see notes on implementation in the jida |
helm/hpcc/values.schema.json
Outdated
}, | ||
"batch": { | ||
"type": "boolean", | ||
"description": "If true, trace data is processed in a batch, if false when it is available" |
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.
Minor, but the last part doesn't make sense to me: ", if false when it is available"
{ | ||
//Groups several spans together, before sending them to an exporter. | ||
//MORE: These options should be configurable from batch/@option | ||
opentelemetry::v1::sdk::trace::BatchSpanProcessorOptions options; //size_t max_queue_size = 2048; |
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.
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.
@ghalliday looks good.
I'm not crazy about the config option name "createDefaultLogExporter" from the config point of view it should be more along the lines of "EnableDefaultLogExporter". subtle difference but I felt it was worth mentioning.
Also, there's a few sample config values files in helm/examples/tracing that would need to be updated, perhaps replaced:
- jlog-collector-fulloutput.yaml
- otlp-grcp-collector-default.yaml
- otlp-http-collector-default.yaml
Adding a new one showing off multiple exporters might also be helpful
Signed-off-by: Gavin Halliday <[email protected]>
Signed-off-by: Gavin Halliday <[email protected]>
Signed-off-by: Gavin Halliday <[email protected]>
@rpastrana I think I have addressed your comments, and resolved the clashes with your GRPC PR which I merged. |
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.
@ghalliday looks good.
Type of change:
Checklist:
Smoketest:
Testing: