Provide an ability to disable query examples for mongoDB monitoring

Description

User story:
As a user, I need to disable query examples and I am unable to do so for MongoDB, so they appear in QAN

UI/UX:
pmm-admin add mongodb ... --disable-queryexamples ...

Acceptance criteria

  • user is able to specify flag so the Query examples are not collected on PMM server side

  • Documentation

    • Release notes

    • Reference manual updates

Suggested implementation

  • API

  • CLI add --disable-queryexamples

 

Out of Scope

  • UI Add option to disable query examples when adding MongoDB service and PG service (new ticket to be created)

 

How to test:
- Manual + add QAA

Details:
TBD 

 

Impact on the user:

Unable to disable query examples for MongoDB

Steps to reproduce:

Actual result:

Expected Result:

Workaround:

None
 
Additional information:
I am presuming that there is no similar information collected for ProxySQL and HAProxy, but if there were to be then that should also be possible to disable.

How to test

None

How to document

None

Activity

Show:

Ben Mildren 
July 15, 2024 at 8:07 AM

Ah awesome ok, thank you!

Roma Novikov 
July 15, 2024 at 8:04 AM

Hi, ! Thanks for the ping, as I haven’t seen the previous comment.
There is no technical complexity here, only resources/time to implement.
Let me check this and see if this is something we can fit into the current scope of the MongoDB improvements bundle we are working on.

Ben Mildren 
July 15, 2024 at 7:55 AM

Hi , apologies for the direct ping, just wanted to confirm this isn’t lost in the backlog.

Out of interest, what are the technical blockers on this one at this point?

Thanks!
Ben

Ben Mildren 
June 29, 2024 at 11:04 AM

Hi folks, this is still a thing, just to manage expectations, is this planned to be addressed at some point?

Jira Bot 
April 16, 2021 at 11:55 AM

To:
CC:

Hi, I'm jira-bot, Percona's Jira automation tool. I've detected that someone from
Percona has made an edit to the Summary field of an issue that you reported.

I'm not sentient (yet) so I'm not sure whether the person fixed a typo, changed
a few words, or completely rewrote the text. In any case, it is Percona Engineering's
intention to make the Summary and Description of an issue as accurate as possible
so that we're fixing the actual problem you're encountering, and to avoid
misunderstandings about symptoms and causes.

If the current Summary does not accurately reflect the problem you are reporting,
or if you feel the change was otherwise inappropriate in some way, please add a
new comment explaining things and we'll address it as soon as we can.

This message will be added only once per issue, regardless of how many times
the Summary is edited.

message-code:summary-edited

Details

Assignee

Reporter

Priority

Components

Needs QA

Needs Doc

Planned Version/s

Fix versions

Story Points

Affects versions

Due date

Created April 7, 2021 at 8:43 AM
Updated 4 days ago