Monitoring for MongoDb | MongoDb Performance and Health Check
Ғылым және технология
Hello and Namaste everyone,
I will today talk about that how we can monitor our MongoDB servers. It will help you to understand and tune the performance of our MongoDB queries and servers. We Will also check the health status of MongoDB and if it is low we will see the methods or ways available for identifying the exact issue.
We will be checking the mongo DB logs as well to identify the slow queries.
As you develop and operate applications with MongoDB, you may need to analyze the performance of the application and its database. When you encounter degraded performance, it is often a function of database access strategies, hardware availability, and the number of open database connections.
Performance issues may indicate that the database is operating at capacity and that it is time to add additional capacity to the database. In particular, the application’s working set should fit in the available physical memory.
how to check MongoDB performance | how to check MongoDB health | how to check MongoDB logs | how to identify slow queries in MongoDB
#mongodbPerformance #mongodbMonitoring #mongodbHealth #mongodb #beSmartBeTechie #smartyTechFizz
Пікірлер: 17
Nice video 😊 well explained. Good topic as well.
Hi, i have a question regarding mongo. I have a collection of 5.5M records. I have a index, on a single field 'description'. 2M of those records have description value as 'First Lot' and rest 2M have them as 'Second Lot'. After doing explain ExecutionStats, for queries on COUNT for ({"description" : "First Lot"}) and ({"description" : "Second Lot"}) the "executionTimeMillis" is 500-600 range for both but when I do COUNT for ({"description" : { $in : ["First Lot", "Second Lot"]}}) the "executionTimeMillis" is minimum in the range of 2000. why is that? it should be in the range of 1100-1200 but its not. Will be a great help if I can reduce the time 🙏
Hello Mam, Could you please let me know the entire process for do the mongodb database point in time restore using the mongodb opps manager console?
mongostat command is not running in my mongodb server 5.0
how to connect mongodb by tcp://ip:port ?
Hi Anjali, Can we monitor the mongodb health using pm2?
@SmartyTechFizz
2 жыл бұрын
Hi Abhi, I am not much aware of pm2 but yes there are monitoring tools available but I don't think they will tell you what actually causing the issue.
@abhisycvirat
2 жыл бұрын
@@SmartyTechFizzHi Anjali, actually I want to check slow running queries in production. Let me know if you are aware of any resources to monitor execution times of queries in production. I checked the mongod log, but I wondered if there is a better solution instead of checking the logs. And thanks for connecting on LinkedIn.
@SmartyTechFizz
2 жыл бұрын
@@abhisycvirat I'll check it out, if I can find any tools for it. Also, you can check by using db.currentOps() if any slow query still running in the background.
@abhisycvirat
2 жыл бұрын
@@SmartyTechFizz Thank you Anjali. I appreciate your help.
@sandeepaara5522
2 жыл бұрын
@@abhisycvirat Hi Bro,can i know to find slow queries in production,have you find any tool or can you tell me it will be helpfull.
my replication robo3t connect is very slow......how to fix it.....plz plz help me🙏 we will pay you....for fix this issue
@SmartyTechFizz
2 жыл бұрын
Hi Vivek, Please mail me at smartytechfizz@gmail.com about the issue you are facing the I'll check it out.
how can view logs in robo3t
@SmartyTechFizz
3 жыл бұрын
Hi, Logs are present only on the server. You can see in the conf of MongoDB i.e mongod.conf log file path is also present there.
mongodb created index itself when you did _id='hgf' (IDHACK) why didn't mongodb created index when you did item='hgf' please tell me.
@SmartyTechFizz
3 жыл бұрын
Hi Atul, Mongodb used to create index on _id itself whenever we insert any document. So, when will query the document using _id then ut is going to use _id index which we called as IDHACK in explain (). Now, when we the colomn or key item : hgf, we don't have created any index on the this field nor mongodb built it automatically that is why it is not going to use any index and not showing in explain().