Reduce logging from mongodb exporter when unauthorized
General
Escalation
General
Escalation
Description
How to test
None
How to document
None
AFFECTED CS IDs
CS0044415
Activity
Show:
Aaditya Dubey June 3, 2024 at 1:58 PM
Hi @Michael Okoko
Thank you for the report and feedback.
Nurlan Moldomurov May 30, 2024 at 10:27 AM
I suggest to not run diagnostic data on non authed arbiter instance.
Details
Details
Assignee
Michael Okoko
Michael OkokoReporter
Michael Okoko
Michael OkokoPriority
Components
Needs QA
Yes
Needs Doc
Yes
Smart Checklist
Open Smart Checklist
Smart Checklist

Open Smart Checklist
Created May 30, 2024 at 9:00 AM
Updated November 13, 2024 at 9:44 AM
As a follow up on https://perconadev.atlassian.net/browse/PMM-12989 , When mongodb commands (such as
getDiagnosticData
) fail on MongoDB exporter, we log the error and the corresponding reasons.Since these commands are run on every scrape, they can be spammy and grow really large (default scrape is 5s).
Proposed Solution
Check if we can execute MongoDB commands on startup and log authorization errors on startup. That way, we can ignore such errors subsequently.