Skip to content

Conversation

Nicusor97
Copy link

@Nicusor97 Nicusor97 commented Oct 3, 2025

Lower the severity of a noisy diagnostic log in the azure_kusto output plugin from info to debug to reduce log spam after upgrading to Fluent Bit 4.0.10.

Starting with Fluent-Bit 4.0.10 we noticed this log being generated by the engine and after further investigation it seems to be more a debug log.

[2025/10/03 09:00:08] [ info] [output:azure_kusto:azure_kusto.1] azure_kusto: before calling azure storage api :: value of set io_timeout is 0
[2025/10/03 09:00:33] [ info] [output:azure_kusto:azure_kusto.1] azure_kusto: before calling azure storage api :: value of set io_timeout is 0
[2025/10/03 09:01:04] [ info] [output:azure_kusto:azure_kusto.1] azure_kusto: before calling azure storage api :: value of set io_timeout is 0
[2025/10/03 09:01:08] [ info] [output:azure_kusto:azure_kusto.1] azure_kusto: before calling azure storage api :: value of set io_timeout is 0
[2025/10/03 09:01:13] [ info] [output:azure_kusto:azure_kusto.1] azure_kusto: before calling azure storage api :: value of set io_timeout is 0
[2025/10/03 09:01:28] [ info] [output:azure_kusto:azure_kusto.1] azure_kusto: before calling azure storage api :: value of set io_timeout is 0
[2025/10/03 09:01:33] [ info] [output:azure_kusto:azure_kusto.1] azure_kusto: before calling azure storage api :: value of set io_timeout is 0
[2025/10/03 09:01:43] [ info] [output:azure_kusto:azure_kusto.1] azure_kusto: before calling azure storage api :: value of set io_timeout is 0
[2025/10/03 09:01:48] [ info] [output:azure_kusto:azure_kusto.1] azure_kusto: before calling azure storage api :: value of set io_timeout is 0
[2025/10/03 09:01:53] [ info] [output:azure_kusto:azure_kusto.1] azure_kusto: before calling azure storage api :: value of set io_timeout is 0
[2025/10/03 09:02:03] [ info] [output:azure_kusto:azure_kusto.1] azure_kusto: before calling azure storage api :: value of set io_timeout is 0
[2025/10/03 09:02:08] [ info] [output:azure_kusto:azure_kusto.1] azure_kusto: before calling azure storage api :: value of set io_timeout is 0
[2025/10/03 09:02:13] [ info] [output:azure_kusto:azure_kusto.1] azure_kusto: before calling azure storage api :: value of set io_timeout is 0
[2025/10/03 09:02:28] [ info] [output:azure_kusto:azure_kusto.1] azure_kusto: before calling azure storage api :: value of set io_timeout is 0
[2025/10/03 09:02:33] [ info] [output:azure_kusto:azure_kusto.1] azure_kusto: before calling azure storage api :: value of set io_timeout is 0
[2025/10/03 09:02:58] [ info] [output:azure_kusto:azure_kusto.1] azure_kusto: before calling azure storage api :: value of set io_timeout is 0
[2025/10/03 09:03:08] [ info] [output:azure_kusto:azure_kusto.1] azure_kusto: before calling azure storage api :: value of set io_timeout is 0
[2025/10/03 09:03:13] [ info] [output:azure_kusto:azure_kusto.1] azure_kusto: before calling azure storage api :: value of set io_timeout is 0
[2025/10/03 09:03:18] [ info] [output:azure_kusto:azure_kusto.1] azure_kusto: before calling azure storage api :: value of set io_timeout is 0
[2025/10/03 09:03:23] [ info] [output:azure_kusto:azure_kusto.1] azure_kusto: before calling azure storage api :: value of set io_timeout is 0
[2025/10/03 09:03:28] [ info] [output:azure_kusto:azure_kusto.1] azure_kusto: before calling azure storage api :: value of set io_timeout is 0
[2025/10/03 09:03:33] [ info] [output:azure_kusto:azure_kusto.1] azure_kusto: before calling azure storage api :: value of set io_timeout is 0
[2025/10/03 09:04:08] [ info] [output:azure_kusto:azure_kusto.1] azure_kusto: before calling azure storage api :: value of set io_timeout is 0
[2025/10/03 09:04:28] [ info] [output:azure_kusto:azure_kusto.1] azure_kusto: before calling azure storage api :: value of set io_timeout is 0
[2025/10/03 09:04:33] [ info] [output:azure_kusto:azure_kusto.1] azure_kusto: before calling azure storage api :: value of set io_timeout is 0
[2025/10/03 09:04:48] [ info] [output:azure_kusto:azure_kusto.1] azure_kusto: before calling azure storage api :: value of set io_timeout is 0
[2025/10/03 09:05:08] [ info] [output:azure_kusto:azure_kusto.1] azure_kusto: before calling azure storage api :: value of set io_timeout is 0
[2025/10/03 09:05:13] [ info] [output:azure_kusto:azure_kusto.1] azure_kusto: before calling azure storage api :: value of set io_timeout is 0
[2025/10/03 09:05:28] [ info] [output:azure_kusto:azure_kusto.1] azure_kusto: before calling azure storage api :: value of set io_timeout is 0
[2025/10/03 09:05:33] [ info] [output:azure_kusto:azure_kusto.1] azure_kusto: before calling azure storage api :: value of set io_timeout is 0
[2025/10/03 09:05:48] [ info] [output:azure_kusto:azure_kusto.1] azure_kusto: before calling azure storage api :: value of set io_timeout is 0
[2025/10/03 09:06:03] [ info] [output:azure_kusto:azure_kusto.1] azure_kusto: before calling azure storage api :: value of set io_timeout is 0
[2025/10/03 09:06:08] [ info] [output:azure_kusto:azure_kusto.1] azure_kusto: before calling azure storage api :: value of set io_timeout is 0

Enter [N/A] in the box, if an item is not applicable to your change.

Testing
Before we can approve your change; please submit the following in a comment:

  • Example configuration file for the change
  • Debug log output from testing the change
  • Attached Valgrind output that shows no leaks or memory corruption was found

If this is a change to packaging of containers or native binaries then please confirm it works for all targets.

  • Run local packaging test showing all targets (including any new ones) build.
  • Set ok-package-test label to test for all targets (requires maintainer to do).

Documentation

  • Documentation required for this feature

Backporting

  • Backport to latest stable release.

Fluent Bit is licensed under Apache 2.0, by submitting this pull request I understand that this code will be released under the terms of that license.

Summary by CodeRabbit

  • Chores
    • Lowered a diagnostic log message to debug level during Azure storage ingestion to reduce noise in default info logs.
    • Keeps normal operational logs cleaner while retaining detailed diagnostics when debug logging is enabled.
    • No functional or behavioral changes to ingestion workflows.
    • No configuration changes required; existing setups continue to work as before.

Copy link

coderabbitai bot commented Oct 3, 2025

Walkthrough

Adjusted a diagnostic log message in azure_kusto_create_blob from info to debug in plugins/out_azure_kusto/azure_kusto_ingest.c. No control-flow, API-call behavior, or public/exported interfaces were changed.

Changes

Cohort / File(s) Summary of changes
Logging verbosity adjustment
plugins/out_azure_kusto/azure_kusto_ingest.c
Changed a diagnostic log level from info to debug before the Azure storage API call.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

I twitch my ears at logs that flow,
From info down to debug’s glow.
A softer whisper in the night,
Same burrow, same steady byte.
I nibble bytes and keep it neat—
Less chatter, still a clean hop-beat. 🐇

Pre-merge checks and finishing touches

❌ Failed checks (1 warning)
Check name Status Explanation Resolution
Docstring Coverage ⚠️ Warning Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%. You can run @coderabbitai generate docstrings to improve docstring coverage.
✅ Passed checks (2 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title Check ✅ Passed The title succinctly identifies the affected plugin (out_azure_kusto) and the primary change of lowering a diagnostic log’s severity, which directly reflects the change from info to debug in the code and aligns with the PR’s stated objective to reduce log noise.
✨ Finishing touches
  • 📝 Generate docstrings
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 32d9c5a and ad41122.

📒 Files selected for processing (1)
  • plugins/out_azure_kusto/azure_kusto_ingest.c (1 hunks)
🚧 Files skipped from review as they are similar to previous changes (1)
  • plugins/out_azure_kusto/azure_kusto_ingest.c

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

Signed-off-by: Nicusor Picatureanu <[email protected]>
@Nicusor97 Nicusor97 force-pushed the fix-wrong-log-level-in-azure-kusto branch from 32d9c5a to ad41122 Compare October 3, 2025 13:43
@Nicusor97
Copy link
Author

@patrick-stephens Can you please include this fix in the next version of fluent-bit ?

@patrick-stephens
Copy link
Collaborator

Was just awaiting @edsiper to confirm but it looks simple to me although I've just noticed the commit message is wrong - can you update it to match the PR title, i.e. plugin: message?
I can merge then unless I hear otherwise as it seems a trivial fix.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants