Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Disable some default collectors doesn't work

Description

https://jira.percona.com/browse/PMM-9312 

 

I tried to disable `replicasetstatus` when adding MongoDB, assuming I would not find any metrics related to rs, but I can still see `mongodb_rs_*` 

 

The exporter is started with the right flags, but it seems it is an exporter bug or I am looking at the wrong metrics. 

 

User Impact: Exporter doesn't respect user passed flag to disable default collector

This might not be directly related to the new implementation, but now it is more obvious for users to be able to disable a collector with the new flag, hence this could be used. 

 

How to test

None

How to document

None

Smart Checklist

Activity

Show:

Carlos Salguero January 4, 2022 at 7:56 AM

In my checks it works as expected.
That metric comes from getDiagnosticData.
Te list of metrics coming from replicasetStatus are:

Roma Novikov January 3, 2022 at 9:47 AM

Hm, I can't see this collector at all on  https://confluence.percona.com/display/PMM/Implement+Three+Scraping+Intervals+for+all+Exporters  is this replicasetstatus collector problem or implementation in general? 

, can you test the same use case on "diagnosticdata" collector to be disabled?

Details

Assignee

Reporter

Priority

Components

Labels

Needs QA

Needs Doc

Story Points

Regression Issue

Yes

Affects versions

Smart Checklist

Created January 3, 2022 at 6:56 AM
Updated March 6, 2024 at 1:42 AM