[
https://issues.apache.org/jira/browse/NIFI-10110?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
brian updated NIFI-10110:
-------------------------
Description:
It would be great if we had a way to trace data as it flows through NiFi and
identify bottlenecks in our flows. Distributed tracing offers advantages where
we can trace data as it moves through various systems (which can include other
NiFi instances/clusters) and enable teams to determine the level of visibility
through sampling.
Ideally, we make taking advantage of tracing as easy as possible by adding it
at the AbstractProcessor level or by providing annotations that can be added to
the various processors.
The biggest question will be how to properly handle span context and dealing
with batching, which the otel spec provides some insight into that
https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/overview.md#links-between-spans
Java lib: [https://github.com/open-telemetry/opentelemetry-java-instrumentation]
Messaging system spec draft:
[https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/trace/semantic_conventions/messaging.md]
Messaging spec PRs:
[https://github.com/open-telemetry/oteps/pulls?q=is%3Apr+is%3Aopen+messaging]
was:
It would be great if we had a way to trace data as it flows through NiFi and
identify bottlenecks in our flows. Distributed tracing offers advantages where
we can trace data as it moves through various systems (which can include other
NiFi instances/clusters) and enable teams to determine the level of visibility
through sampling.
Ideally, we make taking advantage of tracing as easy as possible by adding it
at the AbstractProcessor level or by providing annotations that can be added to
the various processors.
Java lib: https://github.com/open-telemetry/opentelemetry-java-instrumentation
> Add in OpenTelemetry integration to support distributed tracing
> ---------------------------------------------------------------
>
> Key: NIFI-10110
> URL: https://issues.apache.org/jira/browse/NIFI-10110
> Project: Apache NiFi
> Issue Type: New Feature
> Components: Core Framework
> Reporter: brian
> Priority: Major
> Labels: opentelemetry, tracing
>
> It would be great if we had a way to trace data as it flows through NiFi and
> identify bottlenecks in our flows. Distributed tracing offers advantages
> where we can trace data as it moves through various systems (which can
> include other NiFi instances/clusters) and enable teams to determine the
> level of visibility through sampling.
> Ideally, we make taking advantage of tracing as easy as possible by adding it
> at the AbstractProcessor level or by providing annotations that can be added
> to the various processors.
> The biggest question will be how to properly handle span context and dealing
> with batching, which the otel spec provides some insight into that
> https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/overview.md#links-between-spans
> Java lib:
> [https://github.com/open-telemetry/opentelemetry-java-instrumentation]
> Messaging system spec draft:
> [https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/trace/semantic_conventions/messaging.md]
> Messaging spec PRs:
> [https://github.com/open-telemetry/oteps/pulls?q=is%3Apr+is%3Aopen+messaging]
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
