[SERVER-49944] Getting Blank Graphs For MongoDB Free Monitoring Created: 28/Jul/20  Updated: 26/Oct/20  Resolved: 26/Oct/20

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

Type: Question Priority: Minor - P4
Reporter: Pratiksha Aggarwal Assignee: Jonathan Streets (Inactive)
Resolution: Done Votes: 0
Labels: monitoring
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: PNG File image-2020-07-28-15-20-23-894.png     PNG File image-2020-07-28-15-21-20-092.png    
Participants:

 Description   

Enabled free monitoring on replica set cluster but when accessing the URL provided, getting blank graphs. All the servers in cluster are up and running in production



 Comments   
Comment by Jonathan Streets (Inactive) [ 26/Oct/20 ]

Hi pratiksha.gupta38@gmail.com ,

We haven’t heard back from you for some time, so I’m going to mark this ticket as resolved. If this is still an issue for you, please provide additional information and we will reopen the ticket.

Regards,

jon

Comment by Jonathan Streets (Inactive) [ 12/Oct/20 ]

Hi pratiksha.gupta38@gmail.com

We still need additional information to diagnose the problem. If this is still an issue for you, would you please reply to the previous comment?

Thanks,

Jon

Comment by Jonathan Streets (Inactive) [ 31/Jul/20 ]

hi pratiksha.gupta38@gmail.com,
its strange you see nothing in the mongod log,   i see lines such as 

2020-07-31T16:00:59.336-0400 I  CONTROL  [FreeMonProcessor] Free Monitoring is Enabled. Frequency: 60 seconds
2020-07-31T16:00:59.336-0400 I  COMMAND  [conn1] command admin.$cmd appName: "MongoDB Shell" command: setFreeMonitoring { setFreeMonitoring: 1.0, action: "enable", lsid: { id: UUID("08d1787e-2ce8-4f02-a44d-3dde4e777176") }, $db: "admin" } numYields:0 reslen:38 locks:{} protocol:op_msg 117ms

statistics for the last time stats were sent to the server in AWS are available in

> db.serverStatus().freeMonitoring
{
	"state" : "enabled",
	"retryIntervalSecs" : NumberLong(60),
	"lastRunTime" : "2020-07-31T16:11:22.321-0400",
	"registerErrors" : NumberLong(0),
	"metricsErrors" : NumberLong(0)
}

* Do you see the "Free Monitoring" message in the log ?

  • What is the result of db.serverStatus().freeMonitoring ?
  • Can you verify the firewall is allowing port 443 to the AWS cloud
  • Can you verify the account has the correct privileges - see here

Thanks
Jon

Comment by Pratiksha Aggarwal [ 30/Jul/20 ]

Hi Jonathan,

Please find my response below to your above questions

  1. I didn't found anything related in the log file.
  2. I am not allowed to share the host due to organizational restrictions.
  3. No, we have same configuration for staging and production. But staging one if perfectly working while prod one shows blank graphs
Comment by Jonathan Streets (Inactive) [ 29/Jul/20 ]

hi pratiksha.gupta38@gmail.com,

to help me understand about the issue, i will need more information. 

  • have you checked the mongo.log for any errors?
  • can you tell me the name of the aws host that mongod is sending the information? - i was able to find it on my system with lsof -aPi -p $(pidof mongod)
  • is this host being blocked by a firewall in your network ?

thanks,
Jon

Comment by Pratiksha Aggarwal [ 29/Jul/20 ]

Please assign the ticket to respective person. 

Comment by Tim Fogarty [ 28/Jul/20 ]

Hi pratiksha.gupta38@gmail.com, I'm sorry to hear you're having trouble with free monitoring. The TOOLS Jira project is for tracking development and bugs of the CLI tools such as mongoimport and mongorestore. We don't work on free monitoring here, so I'm going to move this ticket to the SERVER project. They might be able to help further. It might also be useful to ask in the MongoDB community forum for help with this topic: https://developer.mongodb.com/community/forums/ 

Generated at Thu Feb 08 05:21:17 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.