Min Xia
Min Xia
Hi @skyduo , since we use main branch for prod release. These changes are on critical path of running ADOT collector. Do you think we can move this changes in...
Hi we only enabled Jaeger receiver in ADOT so far. will put this request in ADOT road map. @JohnWu20 @ntyrewalla
Hi George, to your questions, 1. Yes 2. Yes 3. You should remove it for your production env, it prints lots of debugging logs could affect your service performance
Did you see any log file in `C:\\ProgramData\\Amazon\\AWSOTelCollector\\Logs\\` directory? Just in case that CW/OTel Composite Agent didn't override the log file path successfully.
> @cijothomas Mostly my response above was for your statement. > @mxiamxia Given your requirements, it would be perhaps a little simpler to implement your own SDK, since it will...
>// TODO: Decide if support for RawMeasurements (measurements recorded using // the synchronous instruments) is necessary. It can be used to delegate the // aggregation from the application to the...
Thanks @saaish, we'll add this request in ADOT roadmap. @jhnlsn @alolita
The scope to resolve this issue is vague. Are we planing to only remove the OC metric reference in public API for unblocking Tracing GA? Because it's hard to replace...
Discussed it in SIG with @tigrannajaryan and @bogdandrutu , this issue is currently blocked by open-telemetry/oteps#89.
Thank you! Missed the collector SIG discussions for this week. Will join the discussions next week and provide more details about the proposal.