Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[newrelic-logging] cant disable prometheusAPI metric from fluentbit #1650

Open
KlockiLego opened this issue Mar 24, 2025 · 9 comments
Open
Labels
bug Categorizes issue or PR as related to a bug. triage/pending Issue or PR is pending for triage and prioritization.

Comments

@KlockiLego
Copy link

KlockiLego commented Mar 24, 2025

Helm: newrelic-bundle - nri-bundle-5.0.116

After installing the latest version of new relic, a lot of metrics are collected, while I am only interested in logs (metric data ingest 98%, log data 2% .....)

I cannot disable prometheusAPI metric collection from fluent-bit. Here I see that there has been some change: Updated newrelic-logging to default send Metrics #1619

Metrics that are collected and cause huge data ingest consumption:

fluentbit_filter_drop_records_total
fluentbit_filter_bytes_total
fluentbit_input_storage_chunks_up
fluentbit_input_records_total
fluentbit_output_errors_total
fluentbit_input_files_opened_total
fluentbit_output_chunk_available_capacity_percent
....
@KlockiLego KlockiLego added bug Categorizes issue or PR as related to a bug. triage/pending Issue or PR is pending for triage and prioritization. labels Mar 24, 2025
@workato-integration
Copy link

@KlockiLego
Copy link
Author

This is documented here:
https://docs.newrelic.com/docs/logs/forward-logs/kubernetes-plugin-log-forwarding/#fluent-bit

Unfortunately the number of data ingest is very large and it should be possible to disable sending these metrics

@Tcohn1
Copy link

Tcohn1 commented Mar 25, 2025

Thank you for the feedback. We are looking into this issue and will follow up with an update soon

@KlockiLego
Copy link
Author

Workaround:
Use: nri-bundle-5.0.112 (with newrelic-logging-1.23.7)

@voorepreethi
Copy link
Contributor

Hey @KlockiLego We have updated the scrape interval of Metrics from 10s to 60s. This will reduce the metrics count by 6. We are doing further analysis on priority and would get back to you .
Thank you

@KlockiLego
Copy link
Author

Thanks, but still this is a lot. I have 12 nodes and monthly data ingest was around 120 GB. Now will be 20 GB.

Can you describe exactly what these metrics are and what they are for?
Can you add an option to completely disable it?

I feel like I don't need it, so I use nri-bundle-5.0.112 (with newrelic-logging-1.23.7)

@workato-integration
Copy link

Work has been completed on this issue.

@KlockiLego
Copy link
Author

KlockiLego commented Apr 3, 2025

@voorepreethi, @Tcohn1 I think work is not completed....
This change/bug/feature caused that each node sends 1.66 GB data to new relics and client must pay for this data ingest.

@voorepreethi voorepreethi reopened this Apr 3, 2025
@Tcohn1
Copy link

Tcohn1 commented Apr 9, 2025

hey @KlockiLego , can you please provide additional details about your account so we can look into it. According to our estimation the additional GB for the metrics collected from fluent bit should be negligible.

Can you describe exactly what these metrics are and what they are for?

Thank you for the question. we are working on updating our docs to include these details.

Can you add an option to completely disable it?

The new UX is relying on this , therefore at this time disabling is not available.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Categorizes issue or PR as related to a bug. triage/pending Issue or PR is pending for triage and prioritization.
Projects
None yet
Development

No branches or pull requests

3 participants