Kubernetes Helm nri-bundle logtype

Hello!

I am using the nri-bundle Helm Chart in version 1.9.1 to ingest logs from containers on my Kubernetes cluster into New Relic One. Now I discovered New Relic’s log parsing (https://docs.newrelic.com/docs/logs/log-management/ui-data/logs-parsing-built-rules-custom-parsing) and would like to use that to parse the access and error logs of my Nginx containers. However, the documentation does not describe a method that seems to be usable for the New Relic Integration for Kubernetes. How can I specify the logtype for my containers, ideally distinguishing stdout and stderr?

Thank you in advance,
Dennis

@dschridde Been awhile since you posted this topic and unfortunately there hasn’t been a response from the community yet. I will raise this back up to our support team so that you can hopefully can get some help soon. Thanks for your continued patience!

Joi

Hi @dschridde, apologies for the delay on this! I think if you follow the example here, you should be able to parse the access and error logs.

Let me know how that goes for you.

Sadly that does not work, since my nginx runs as a container and not on a machine. It outputs logs to stdout and stderr and not into files.

The nri-bundle Helm chart (https://github.com/newrelic/helm-charts) captures the log messages via Kubernetes’ internal log files (cf. https://github.com/newrelic/helm-charts/blob/master/charts/newrelic-logging/k8s/README.md#configuration-notes) and there appears to be no documented way to specify the logtype for individual containers in this case.

I created https://github.com/newrelic/helm-charts/issues/251 as a feature request.


New Relic edit

  • I want this, too
  • I have more info to share (reply below)
  • I have a solution for this

0 voters

We take feature ideas seriously and our product managers review every one when plotting their roadmaps. However, there is no guarantee this feature will be implemented. This post ensures the idea is put on the table and discussed though. So please vote and share your extra details with our team.

Thanks for the update @dschridde. I have submitted a feature request on my end for this as well and I’ve +1 this internally to try and get a bit of traction going. While there is no guarantee that this will be implemented, hopefully with will be on our future roadmap.