Project is being sunset

[MikeGoldsmith]

See OSS lifecycle and practices

This project has outlived its useful lifespan, and will be archived in the future.

If you are actively using this exporter, please comment on this issue with your use case.

[wushujames]

Is this repo the code that implements https://docs.honeycomb.io/send-data/kubernetes/send-data-honeycomb-network-agent/ ?

If so, is there a replacement for this repo, that will still implement https://docs.honeycomb.io/send-data/kubernetes/send-data-honeycomb-network-agent/ ?

[MikeGoldsmith]

Hi @wushujames - no, this is a different tool. The Honeycomb Kubernetes Agent is here.

[wushujames]

Hi @wushujames - no, this is a different tool. The Honeycomb Kubernetes Agent is here.

Thanks for the response @MikeGoldsmith. Sorry, I'm still confused. What you said doesn't match what the docs seem to pointing to.

In the docs at https://docs.honeycomb.io/send-data/kubernetes/send-data-honeycomb-network-agent/, it says to do this:
$ helm repo add honeycomb https://honeycombio.github.io/helm-charts $ helm repo update $ helm install network-agent honeycomb/network-agent --namespace honeycomb

If I follow the repos, the helm install network-agent leads me to this: https://github.com/honeycombio/helm-charts/tree/main/charts/network-agent

And the README.md says

The Helm chart installs the Honeycomb Network Agent in a Kubernetes cluster.

Which is this repo.

So the Honeycomb docs for Send Data with the Honeycomb Network Agent (No Code) seem to lead back to this repo. But as you said above, this repo is being sunset.

Which set of docs is correct? The docs at https://docs.honeycomb.io/send-data/kubernetes/send-data-honeycomb-network-agent/ or the sunsetting announcement?

Thanks! I haven't yet tried any of this, but the Send Data with the Honeycomb Network Agent (No Code) functionality sounds really useful and I was planning on trying it in the upcoming months. That's why I wanted to know more about whether it was being sunsetted or not.

[MikeGoldsmith]

Ah, I think I misunderstood your original message and thought you were looking for the Honeycomb Kubernetes Agent, which I linked to.

The Honeycomb Network Agent is being sunset due to low adoption and alternative tools being available. For example, the OpenTelemetry eBPF tool that does similar work.

Are you currently using the Honeycomb Network Agent or looking into options?

I will update our documentation to indicate this tool is being sunset.