mule-opentelemetry-module icon indicating copy to clipboard operation
mule-opentelemetry-module copied to clipboard

Mule Extension to generate OpenTelemetry traces and metrics

Results 26 mule-opentelemetry-module issues
Sort by recently updated
recently updated
newest added

[Global Config Span Tags](https://avioconsulting.github.io/mule-opentelemetry-module/#_global_config_span_tags) allows setting/overriding span tags for components using global configuration. With latest 1.2.0 release, tag values are only only possible to set using system properties. Any properties...

enhancement

When configuring OpenTelemetry config in the application to send traces to Elastic, Authorization header works only for below scenarios 1. Hardcoded text containing _'ApiKey '_ ` ` 3. Encrypting text...

bug

OTel context propagation using this module requires some modifications to the mule application code. Due to the restrictions in the runtime, auto-propagation cannot be supported (eg. #12). To help users,...

documentation

When using `db:data-source-connection` for DB Configs, database span attributes are not extracting all related information. We should find a way to extract information from datasource configuration. Global config: ``` ```...

enhancement

For all connectors/modules requiring config elements (eg. HTTP, DB etc), we extract information from global config object. This is done through the APIs provided by Mule. However this API isn't...

enhancement

Add support for creating spans for DB connector operations and capture any relevant data in tags, using standard defined open tracing tags if they exist.

enhancement

Add support for inbound propagation of the tracing context from JMS properties on inbound JMS messages. Also add optional support for creating spans for outbound JMS operations and capturing relevant...

enhancement

closes #195 ![image](https://github.com/user-attachments/assets/9e55cd23-20e7-4631-a92d-6e0276245419) Before Fix Trace - ![image](https://github.com/user-attachments/assets/dfe949f5-092d-4c31-82dd-e0f84791ceec) After Fix Trace - ![image](https://github.com/user-attachments/assets/e5b85328-d752-41a1-9300-83bb87e423ad)

When a flow/subflow from an imported mule configuration are invoked, the span of the target flow is not connected to the parent context. The target flow's span appears as a...

bug

Hey, is there any way to inject the trace id into the logs directly through the connector?

question