Skip to content

in_prometheus: do not disclosure error details for client - #259

Open
kenhys wants to merge 2 commits into
fluent:masterfrom
kenhys:suppress-exception
Open

in_prometheus: do not disclosure error details for client#259
kenhys wants to merge 2 commits into
fluent:masterfrom
kenhys:suppress-exception

Conversation

@kenhys

@kenhys kenhys commented Jul 31, 2026

Copy link
Copy Markdown
Contributor

It is reasonable to logging error, but no need to disclose detail for client.

@kenhys kenhys changed the title jin_prometheus: do not disclosure error details for client in_prometheus: do not disclosure error details for client Jul 31, 2026
Comment thread lib/fluent/plugin/in_prometheus.rb Outdated
@kenhys
kenhys force-pushed the suppress-exception branch from d52876d to 9bb53f1 Compare August 3, 2026 03:37
kenhys added 2 commits August 3, 2026 12:38
It is reasonable to logging error, but no need to disclose detail
for client.

Signed-off-by: Kentaro Hayashi <hayashi@clear-code.com>
/metrics and /all_metrics are assumed that these API will be called
periodically. If internal server error occurs continuously, it means
that same error log will be recorded. That is incompatible behavior
before.

To record detailed logs as often as necessary, introduced
`ignore_error_log_interval`.

Fluentd itself have ignore_repeated_log_interval and
ignore_same_log_interval, but it must be system wide configuration.
The scope of error handling should be limited to this plugin, so
do not escalate system wide configuration.

Signed-off-by: Kentaro Hayashi <hayashi@clear-code.com>
@kenhys
kenhys force-pushed the suppress-exception branch from 9bb53f1 to dfc7049 Compare August 3, 2026 03:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants