[SERVER-39617] Free Monitoring does not reflect current situation Created: 09/Feb/19  Updated: 11/Mar/19  Resolved: 11/Mar/19

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: 4.0.4
Fix Version/s: None

Type: Bug Priority: Minor - P4
Reporter: Semyon Vyskubov Assignee: Kelsey Schubert
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: PNG File image-2019-02-10-00-08-05-462.png    
Issue Links:
Related
Participants:

 Description   

I have 2 servers running in a replica set. Recently I had some issues with the primary one, and whole replica has been reconfigured, but the primary one stayed on its original place.

After I've added one server to the set, Free Monitoring started to show "blank graphs" like these:

Disabling and enabling monitoring does not help much.

I've noticed also that on restarting the primary, there were some data in a new graph related to a secondary server. However once primary back online graph related to secondary disappeared, and the blank one, without data, back again.

Is there anything I could try to safely remove Free Monitoring related data to try to set it up from scratch?

 



 Comments   
Comment by Kelsey Schubert [ 11/Mar/19 ]

I'm resolving this since a workaround has provided and there are no changes required to the MongoDB server codebase. We're tracking the issue internally, thanks again for the bug report.

Comment by Mark Benvenuto [ 13/Feb/19 ]

If you need to clear all local free monitoring state, you need to run MongoDB without auth and {{--
enableFreeMonitoring=off}}, and then delete one record in admin.system.version.
In the shell, run:

db.getSiblingDB("admin").system.version.remove({_id: "free_monitoring"}); 

 
Be very careful as deleting records in system.version is dangerous and unsupported. After you delete this record, restart mongod without --enableFreeMonitoring=off.

Comment by Semyon Vyskubov [ 12/Feb/19 ]

No problem!

I have tried to turn monitoring off, then on again, and got same url with same problem.

Is there any.. some sort of cache folder folder I could safely wipe out and try enabling monitoring afterwards?

Comment by Kelsey Schubert [ 11/Feb/19 ]

Thanks for the email!

Comment by Kelsey Schubert [ 11/Feb/19 ]

uoziod, would you please provide the url that you're using to access free monitoring for this cluster?

Thanks,
Kelsey

Comment by Kelsey Schubert [ 11/Feb/19 ]

Hi uoziod,

Thanks for the report, we're looking into what we can do our side to resolve the issue and will update you when we know more.

Kind regards,
Kelsey

Generated at Thu Feb 08 04:52:35 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.