New component: Kentik Network Telemetry Receiver

[i3149]

The purpose and use-cases of the new component

Kentik is a company which collects both passive and active network data. Passive examples are netflow and npm both of which are best seen as metrics, while active is the network synthetic product which performs web transactions and produces a har file result for each test run which should map to a trace.

These signals can be exported from Kentik via a http stream of Cap'n Proto buffers. We would like to create an otel receiver for this feed and allow any otel collector to work with Kentik data. New Relic provides an example of how this data can be integrated.

Example configuration for the component

receivers:
  kentik:
    endpoint: 0.0.0.0:9000 # Where to listen for the HTTP push from Kentik.
    auth: # Required. An email and an API token is required in the header authentication
      email: <X-Auth-Email>
      token: <API_TOKEN>
    region: US # defaults to US, can override for other Kentik regions. 

Telemetry data types supported

Metrics, Traces

Is this a vendor-specific component?

• This is a vendor-specific component
• If this is a vendor-specific component, I am proposing to contribute and support it as a representative of the vendor.

Code Owner(s)

@i3149

Sponsor (optional)

@astencel-sumo

Additional context

There is an existing OSS tool to translate the binary feed from kentik at https://github.com/kentik/ktranslate. We'd like to get away from having users run 2 binaries (ktranslate + otel collector) but there's an argument to be made that ktranslate should just be updated to emit otel. In practice, we find getting 1 binary running correctly is hard enough.

[andrzej-stencel]

Thanks @i3149 for raising this. Ideally, the Kentik platform would support OTLP natively. If you can join a Collector SIG meeting, we could discuss the possibility of this vs. creating Kentik receiver.

[github-actions]

This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping @open-telemetry/collector-contrib-triagers. If this issue is still relevant, please ping the code owners or leave a comment explaining why it is still relevant. Otherwise, please close it.

[github-actions]

This issue has been closed as inactive because it has been stale for 120 days with no activity.