rickbansal-mulesoft otel-mule4-observability-agent issues

rickbansal-mulesoft / otel-mule4-observability-agent

12 stars 7 forks source link

issues

Newest

Newest Most commented Recently updated Oldest Least commented Least recently updated

Is there a JAVA 17 Support available

#17 ajayshankarj opened 2 weeks ago
0
Option to implement this for on-premise mule runtimes

#16 ajayshankarj opened 3 weeks ago
0
Option to choose insecure while connecting to HTTPS

#15 ajayshankarj opened 3 weeks ago
0
Cannot get an OpenTelemetry SDK connection before the SDK is initialized

#14 mspatagundi7 closed 8 months ago
6
Vulnerabilities Detected on Veracode Application Security Report

#13 karthik300300 opened 10 months ago
7
Getting the error while exporting traces to jaeger from mule application: io.opentelemetry.exporter.internal.grpc.OkHttpGrpcExporter: Failed to export metrics. The request could not be executed. Full error message: Failed to connect to localhost/127.0.0.1:4317

#12 himanshuhemu opened 1 year ago
0
Any way to store the Span ID in the trace context as it goes along?

#11 StephenGoodall opened 1 year ago
6
Failed to send traces in Hybrid and RTF implementation.

#10 ksawant17 closed 8 months ago
2
XML configuration example possible

#9 StephenGoodall closed 1 year ago
1
Message Processor Span Bypass

#8 shilpamallya closed 1 year ago
1
Required to have distributed traceability when using OTEL for Anypoint MQ publish-subscribe integrations

#7 pasrichavasudha closed 1 year ago
5
Getting error when Open Telemetry is configured with mule application

#6 AUAW closed 8 months ago
0
Feature/add support truststore

#5 yohanesws opened 2 years ago
1
You may be stepping on some headers

#4 jbsouthe opened 2 years ago
3
Logger issue

#3 bijuiv-ms closed 2 years ago
2
Issue with flow references

#2 bijuiv-ms closed 2 years ago
4
Test issue

#1 rickbansal-mulesoft closed 2 years ago
0