[ 
https://issues.apache.org/jira/browse/NIFI-12115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17771686#comment-17771686
 ] 

Joe Witt commented on NIFI-12115:
---------------------------------

[~exceptionfactory] I am leaving unresolved but for 2.x line it is resolved.  
Please wrap up the support/1.x merge and then resolve. THanks

> Add ListenOTLP Processor for Collecting OpenTelemetry
> -----------------------------------------------------
>
>                 Key: NIFI-12115
>                 URL: https://issues.apache.org/jira/browse/NIFI-12115
>             Project: Apache NiFi
>          Issue Type: New Feature
>          Components: Extensions
>            Reporter: David Handermann
>            Assignee: David Handermann
>            Priority: Major
>             Fix For: 2.0.0, 1.latest
>
>          Time Spent: 3h
>  Remaining Estimate: 0h
>
> The OpenTelemetry framework provides a common set of standards for collecting 
> and transmitting observability information including logs, metrics, and 
> traces. The [OLTP Specification 
> 1.0.0|https://opentelemetry.io/docs/specs/otlp/] defines protocol definitions 
> for sending and receiving telemetry information over gRPC and HTTP.
> A new Processor should be implemented to support collecting OpenTelemetry. 
> The Processor should support both OLTP/gRPC and OLTP/HTTP transmission. 
> Support for OLTP/HTTP should include content type detection and handling for 
> either Protobuf or JSON encoding to enable collection from a wide variety of 
> sources. The OLTP Specification describes standard REST resource paths for 
> telemetry requests types that the Processor should accept. The Processor 
> should also support HTTPS transmission with a configurable Client 
> Authentication policy to enable mutual TLS when necessary.
> Similar to other listening Processors, the ListenOTLP Processor should 
> support output batching that preserves the original format of Export Service 
> Requests, but merges arrays of resources with shared types. The initial 
> version should write output in JSON, following the OLTP Specification, with 
> internal conversion from Protobuf.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to