How to monitor MongoDB

•

10 likes•41,874 views

David Mytton is a MongoDB master and the founder of Server Density. In this presentation David delves deeper into what's discussed in our how to monitor MongoDB tutorial (https://blog.serverdensity.com/monitor-mongodb/), with the aim of taking you through: Key MongoDB metrics to monitor. Non-critical MongoDB metrics to monitor. Alerts to set for MongoDB on production. Tools for monitoring MongoDB.

How to monitor:
MongoDB
David Mytton
Hangout on Air - Sept 2014
https://blog.serverdensity.com/monitor-mongodb/

Server Density Architecture
● ~100 servers - Ubuntu 12.04

Server Density Architecture
● ~100 servers - Ubuntu 12.04
● 50:50 virtual/dedicated

Server Density Architecture
● ~100 servers - Ubuntu 12.04
● 50:50 virtual/dedicated
● 200TB/m processed data

Server Density Architecture
● ~100 servers - Ubuntu 12.04
● 50:50 virtual/dedicated
● 200TB/m processed data
● Nginx, Python, MongoDB

Server Density Architecture
● ~100 servers - Ubuntu 12.04
● 50:50 virtual/dedicated
● 200TB/m processed data
● Nginx, Python, MongoDB
● Softlayer > 1TB RAM, 5TB SSDs

Key metrics
● Oplog replication lag
● Replica state
● Lock %
● Disk i/o % utilization

Oplog replication lag
● Replica sets: master/slave

Oplog replication lag
● Replica sets: master/slave
● Async i.e. eventually consistent

Oplog replication lag
● Replica sets: master/slave
● Async i.e. eventually consistent
● Write concern

Oplog replication lag
https://blog.serverdensity.com/mongodb-benchmarks/

Oplog replication lag
● Replica sets: master/slave
● Async i.e. eventually consistent
● Write concern
● Falling behind

Reasons for repl falling behind
● Network problems

Reasons for repl falling behind
● Network problems
● Hardware problems

Reasons for repl falling behind
● Network problems
● Hardware problems
● Shard chunk migrations

Reasons for repl falling behind
● Network problems
● Hardware problems
● Shard chunk migrations
● MongoDB bugs

Replica state
● Primary / secondary
● Alert on state change

Lock %
● Database locking (2.6)
● Sometimes a problem:

Lock %
● Database locking (2.6)
● Sometimes a problem:
● Nearing 100%

Lock %
● Database locking (2.6)
● Sometimes a problem:
● Nearing 100%
● Constantly high

Lock %
● Database locking (2.6)
● Sometimes a problem:
● Nearing 100%
● Constantly high
● Slows replication

Disk i/o % utilization
● Hardware limits

Disk i/o % utilization
● Hardware limits
● Nearing 100%

Disk i/o % utilization
● Hardware limits
● Nearing 100%
● Constantly high

Disk i/o % utilization
● Hardware limits
● Nearing 100%
● Constantly high
● Spinning -> SSD

Disk i/o % utilization
https://blog.serverdensity.com/mongodb-performance-ssds-vs-spindle-sas-drives/

Disk i/o % utilization
https://blog.serverdensity.com/mongodb-benchmarks/

Disk i/o % utilization
● Hardware limits
● Nearing 100%
● Constantly high
● Spinning -> SSD
● Slow queries, hangs, slow repl

Non-critical metrics to watch
● Memory usage

Non-critical metrics to watch
● Memory usage
● Page faults

Non-critical metrics to watch
● Memory usage
● Page faults
● Connections

Non-critical metrics to watch
● Memory usage
● Page faults
● Connections
● Shard chunk distribution

Monitoring tools
● mongostat
● mongotop
● rs.status()
● sh.status()

Summary
● Critical alerts on key metrics

Summary
● Critical alerts on key metrics
● Watch non-critical

Summary
● Critical alerts on key metrics
● Watch non-critical
● Manual tools for real time

Summary
● Critical alerts on key metrics
● Watch non-critical
● Manual tools for real time
● Set up a monitoring product

Useful resources
● http://docs.mongodb.org/manual/administration/monitoring/
● https://blog.serverdensity.com/monitor-mongodb
● https://blog.serverdensity.com

どもありがとうございます
＠davidmytton
david@serverdensity.com
blog.serverdensity.com

This document discusses MongoDB and server performance. It covers tools for profiling and monitoring MongoDB performance like db.currentOp() and mongostat. It discusses optimizing queries and schemas for speed. It also covers server resources like storage, network, and CPU. Specifically, it goes into details about storage types like RAM, SSD, HDD and how the page cache and memory mapped files work. It provides tips on identifying and troubleshooting disk and memory limits that could impact performance.

Automate MongoDB with MongoDB Management Service

MongoDB

MongoDB Management Service makes operations effortless, reducing complicated tasks to a single click. You can now provision machines, configure replica sets and sharded clusters, and upgrade your MongoDB deployment all through the MMS interface. We'll walk through demos of all the new MMS features, including provisioning, expanding and contracting a cluster, resizing the oplog, and managing users.

MongoDB Memory Management Demystified

MongoDB

This document discusses MongoDB's memory management system. It explains that MongoDB uses memory mapped files to store data in memory and access it very quickly. However, this means MongoDB has little control over what data stays in memory. The document provides tips on monitoring MongoDB's memory usage and page faults, identifying the working data set, and optimizing data and indexes to reduce memory usage and improve performance.

MongoDB memory management demystified

Alon Horev

Understanding how memory is managed with MongoDB is instrumental in maximizing database performance and hardware utilisation. This talk covers the workings of low level operating system components like the page cache and memory mapped files. We will examine the differences between RAM, SSD and hard disk drives to help you choose the right hardware configuration. Finally, we will learn how to monitor and analyze memory and disk usage using the MongoDB Management Service, linux administration commands and MongoDB commands.

How to Monitor MySQL

Server Density

7 Ways To Crash Postgres

PostgreSQL Experts, Inc.

7 ways to crash Postgres 1. Do not apply updates and remain on outdated versions of PostgreSQL. 2. Run out of disk space by allowing the database to grow without monitoring disk usage. This can result in errors and panics. 3. Delete important database files and directories which causes the database to fail to start. 4. Set memory settings too high and overload the system memory, triggering out of memory kills of the PostgreSQL process. 5. Use faulty hardware without monitoring for failures which can lead to corrupted blocks and index errors. 6. Allow too many open connections without connection pooling which can prevent new connections. 7. Accumulate zombie locks by not closing transactions, slowing down

Webinar slides: Become a MongoDB DBA - What to Monitor (if you’re really a My...

Severalnines

To operate MongoDB efficiently, you need to have insight into database performance. And with that in mind, we’ll dive into monitoring in this second webinar in the ‘Become a MongoDB DBA’ series. MongoDB offers many metrics through various status overviews and commands, but which ones really matter to you? How do you trend and alert on them? What is the meaning behind the metrics? We’ll discuss the most important ones and describe them in ordinary plain MySQL DBA language. And we’ll have a look at the open source tools available for MongoDB monitoring and trending. Finally, we’ll show you how to leverage ClusterControl’s MongoDB metrics, dashboards, custom alerting and other features to track and optimize the performance of your system. AGENDA How does MongoDB monitoring compare to MySQL Key MongoDB metrics to know about Trending or alerting? Available open source MongoDB monitoring tools How to monitor MongoDB using ClusterControl Demo SPEAKER Art van Scheppingen is a Senior Support Engineer at Severalnines. He’s a pragmatic MySQL and Database expert with over 15 years experience in web development. He previously worked at Spil Games as Head of Database Engineering, where he kept a broad vision upon the whole database environment: from MySQL to Couchbase, Vertica to Hadoop and from Sphinx Search to SOLR. He regularly presents his work and projects at various conferences (Percona Live, FOSDEM) and related meetups.

Shootout at the AWS Corral

PostgreSQL Experts, Inc.

The document summarizes the results of benchmarking and comparing the performance of PostgreSQL databases hosted on Amazon EC2, RDS, and Heroku. It finds that EC2 provides the most configuration options but requires more management, RDS offers simplified deployment but less configuration options, and Heroku requires no management but has limited configuration and higher costs. Benchmark results show EC2 performing best for raw performance while RDS and Heroku trade off some performance for manageability. Heroku was the most expensive option.

This document summarizes the results of benchmarking PostgreSQL database performance on several cloud platforms, including AWS EC2, RDS, Google Compute Engine, DigitalOcean, Rackspace, and Heroku. The benchmarks tested small and large instance sizes across the clouds on different workload types, including in-memory and disk-based transactions and queries. Key metrics measured were transactions per second (TPS), load time to set up the database, and cost per TPS and load bandwidth. The results show large performance and cost variations between clouds and instance types. In general, dedicated instances like EC2 outperformed shared instances, and DBaaS options like RDS were more expensive but offered higher availability. The document discusses challenges

Introducing MongoDB in a multi-site HA environment

Sebastian Geib

Advanced Administration, Monitoring and Backup

MongoDB

Sailthru has been using MongoDB for 4 years, pushing the system to scale. Maintaining a high degree of client-side customizability while growing aggressively has posed unique challenges to our infrastructure. We have maintained high uptime and performance by using monitoring that covers expected use patterns as well as monitoring that catches edge cases for new and unexpected access to the database. In this session, we will talk about Sailthru's use of MongoDB Management Service (MMS), as well as areas in which we have implemented custom monitoring and alerting tools. I will also discuss our transition from a hybrid backup solution using on-premise hardware and AWS snapshots, to using backups with MMS, and how this has benefited Sailthru.

High Availabiltity & Replica Sets with mongoDB

Gareth Davies

Optimizing MongoDB: Lessons Learned at Localytics

andrew311

Как Web-акселератор акселерирует ваш сайт / Александр Крижановский (Tempesta ...

Ontico

В докладе я расскажу, что такое Web-акселератор, он же reverse proxy и он же - фронтенд. Как следует из названия, он ускоряет сайт. Но за счет чего он это делает? Какие они, вообще, бывают? Что они умеют, а что нет? В чем особенности каждого из решений? И, вообще, постараюсь рассказать о них вглубь и вширь. Еще я расскажу про еще один Open Source Web-акселератор - Tempesta FW. Уникальность проекта в том, что это гибрид Web-акселератора и файервола, разрабатываемый специально для обработки и фильтрации больших объемов HTTP трафика. Основные сценарии использования системы — это защита от DDoS прикладного уровня и просто доставка больших объемов HTTP трафика малыми затратами на оборудование. - Что такое Web-акселератор, зачем он был придуман и как понять когда он нужен; - Типичный функционал reverse proxy, его отличия от Web-сервера; - Упомянем про SSL акселераторы; - Заглянем вглубь HTTP, и как он управляет кэшированием и проксированием, что может быть закэшированно, а что - нет; - Мы сравним наиболее популярные акселераторы (Nginx, Varnish, Apache Traffic Server, Apache HTTPD, Squid) по фичам и внутренностям; - Зачем нужен еще один Web-акселератор Tempesta FW, и в чем его отличие от других акселераторов.

Tuning Linux for MongoDB

Tim Vaillancourt

This document discusses how to tune Linux for optimal MongoDB performance. Key points include setting ulimits to allow for many processes and open files, disabling transparent huge pages, using the deadline IO scheduler, setting the dirty ratio and swappiness low, and ensuring consistent clocks with NTP. Monitoring tools like Percona PMM or Prometheus with Grafana dashboards can help analyze MongoDB and system metrics.

92 grand prix_2013

PostgreSQL Experts, Inc.

This document summarizes Josh Berkus's presentation on new features in PostgreSQL versions 9.1, 9.2, and the upcoming 9.3. Some key highlights include improvements to read and write performance, the addition of JSON data type and PL/v8 and PL/Coffee procedural languages, index-only scans, cascading replication, SP-GiST indexing, and many new monitoring and administration features. Josh Berkus is available for questions at josh@pgexperts.com and encourages attendees to upcoming PostgreSQL conferences.

Redis ndc2013

DaeMyung Kang

Redis Tips discusses various tips for using Redis including dangerous commands to avoid such as KEYS and FLUSHALL. It describes how FLUSHALL works differently in Redis compared to Memcache and can be slow. It also covers Redis memory policies, replication, RDB snapshots, and approaches to sharding or clustering Redis including using a client library or server proxy. Sentinel is introduced as a failover solution for Redis masters and slaves.

Clug 2012 March web server optimisation

grooverdan

GUC Tutorial Package (9.0)

PostgreSQL Experts, Inc.

Fail over fail_back

PostgreSQL Experts, Inc.

1) Automated failover involves detecting failure of the primary database, promoting a replica to be the new primary, and failing over applications to connect to the new primary. 2) Detecting failure involves multiple checks like connecting to the primary, checking processes, and using pg_isready. Promoting a replica requires choosing the most up-to-date one and running pg_ctl promote. 3) Failing over applications can be done by updating a configuration system and restarting apps, using a tool like Zookeeper, or by failing over a virtual IP with Pacemaker. Proxies can also be used to fail over connections.

Elephant Roads: a tour of Postgres forks

Command Prompt., Inc

Josh Berkus Most users know that PostgreSQL has a 23-year development history. But did you know that Postgres code is used for over a dozen other database systems? Thanks to our liberal licensing, many companies and open source projects over the years have taken the Postgres or PostgreSQL code, changed it, added things to it, and/or merged it into something else. Illustra, Truviso, Aster, Greenplum, and others have seen the value of Postgres not just as a database but as some darned good code they could use. We'll explore the lineage of these forks, and go into the details of some of the more interesting ones.

Как PostgreSQL работает с диском

PostgreSQL-Consulting

Troubleshooting redis

DaeMyung Kang

This document discusses troubleshooting Redis. Some key points: - Redis is single-threaded, so commands like KEYS, FlushAll, and deleting large collections can be slow. It's better to use SCAN instead of KEYS. - Creating Redis database snapshots (RDB files) and rewriting the append-only file (AOF) can cause high disk I/O and CPU usage. It's best to disable automatic rewrites. - Monitoring memory usage and fragmentation is important to avoid performance issues. The maxmemory setting also needs monitoring to prevent out-of-memory errors. - Network and replication failures need solutions like DNS failover or using Zookeeper for coordination to maintain high availability of Redis

HighLoad Solutions On MySQL / Xiaobin Lin (Alibaba)

Ontico

The document summarizes several issues encountered with high load on Alibaba MySQL databases and solutions implemented: 1) Hotspot updating of a single row caused deadlocks; implementing queueing on the primary key resolved this. 2) Unexpected long transactions under high load led to clients waiting long periods; committing transactions early where possible addressed this. 3) More than 50,000 active threads overwhelmed MySQL's capabilities; implementing actions based on low and high thread thresholds helped.

초보자를 위한 분산 캐시 이야기

OnGameServer

This document discusses using caching to improve performance for web applications. It provides three key points: 1. Cache stores data to serve future requests faster by avoiding accessing the database. It is commonly used for things like login information, page content, and API responses. 2. There are different cache architectures like memcached and Redis that support storing data in-memory for fast retrieval. Factors like data size, update frequency, and consistency requirements determine the appropriate caching strategy. 3. Real-world examples show how companies like Facebook, Twitter, and Wonga use caching extensively to handle high volumes of traffic and database requests. Caching is critical to scaling applications in a cost-effective way.

Как понять, что происходит на сервере? / Александр Крижановский (NatSys Lab.,...

Ontico

Запускаем сервер (БД, Web-сервер или что-то свое собственное) и не получаем желаемый RPS. Запускаем top и видим, что 100% выедается CPU. Что дальше, на что расходуется процессорное время? Можно ли подкрутить какие-то ручки, чтобы улучшить производительность? А если параметр CPU не высокий, то куда смотреть дальше? Мы рассмотрим несколько сценариев проблем производительности, рассмотрим доступные инструменты анализа производительности и разберемся в методологии оптимизации производительности Linux, ответим на вопрос за какие ручки и как крутить.

Using ZFS file system with MySQL

Mydbops

PostgreSQL Replication in 10 Minutes - SCALE

PostgreSQL Experts, Inc.

This document summarizes a presentation about PostgreSQL replication. It discusses different replication terms like master/slave and primary/secondary. It also covers replication mechanisms like statement-based and binary replication. The document outlines how to configure and administer replication through files like postgresql.conf and recovery.conf. It discusses managing replication including failover, failback, remastering and replication lag. It also covers synchronous replication and cascading replication setups.

MongoDB Performance Tuning and Monitoring

MongoDB

The document discusses MongoDB's free cloud monitoring service MMS and how it can be used to monitor and tune MongoDB performance. It provides examples of using MMS metrics and logs to diagnose two cases of performance issues - high replication lag due to insufficient bandwidth and slow queries causing high disk latency. The presentation recommends setting up MMS to collect metrics and receive alerts, and explores some key metrics and tools for log analysis to help identify and address bottlenecks.

Mongo db monitoring 어떤 것이 좋을까(mongodb korea, 김인범)

InBum Kim

What's hot

Shootout at the PAAS Corral

PostgreSQL Experts, Inc.

Introducing MongoDB in a multi-site HA environment

Sebastian Geib

Advanced Administration, Monitoring and Backup

MongoDB

High Availabiltity & Replica Sets with mongoDB

Gareth Davies

Optimizing MongoDB: Lessons Learned at Localytics

andrew311

Как Web-акселератор акселерирует ваш сайт / Александр Крижановский (Tempesta ...

Ontico

Tuning Linux for MongoDB

Tim Vaillancourt

92 grand prix_2013

PostgreSQL Experts, Inc.

Redis ndc2013

DaeMyung Kang

Clug 2012 March web server optimisation

grooverdan

GUC Tutorial Package (9.0)

PostgreSQL Experts, Inc.

Fail over fail_back

PostgreSQL Experts, Inc.

Elephant Roads: a tour of Postgres forks

Command Prompt., Inc

Как PostgreSQL работает с диском

PostgreSQL-Consulting

Troubleshooting redis

DaeMyung Kang

HighLoad Solutions On MySQL / Xiaobin Lin (Alibaba)

Ontico

초보자를 위한 분산 캐시 이야기

OnGameServer

Как понять, что происходит на сервере? / Александр Крижановский (NatSys Lab.,...

Ontico

Using ZFS file system with MySQL

Mydbops

PostgreSQL Replication in 10 Minutes - SCALE

PostgreSQL Experts, Inc.

What's hot (20)

Shootout at the PAAS Corral

Introducing MongoDB in a multi-site HA environment

Advanced Administration, Monitoring and Backup

High Availabiltity & Replica Sets with mongoDB

Optimizing MongoDB: Lessons Learned at Localytics

Как Web-акселератор акселерирует ваш сайт / Александр Крижановский (Tempesta ...

Tuning Linux for MongoDB

92 grand prix_2013

Redis ndc2013

Clug 2012 March web server optimisation

GUC Tutorial Package (9.0)

Fail over fail_back

Elephant Roads: a tour of Postgres forks

Как PostgreSQL работает с диском

Troubleshooting redis

HighLoad Solutions On MySQL / Xiaobin Lin (Alibaba)

초보자를 위한 분산 캐시 이야기

Как понять, что происходит на сервере? / Александр Крижановский (NatSys Lab.,...

Using ZFS file system with MySQL

PostgreSQL Replication in 10 Minutes - SCALE

Viewers also liked

MongoDB Performance Tuning and Monitoring

MongoDB

Mongo db monitoring 어떤 것이 좋을까(mongodb korea, 김인범)

InBum Kim

An Introduction to MongoDB Ops Manager

MongoDB

MongoDB Ops Manager is the easiest way to manage/monitor/operationalize your MongoDB footprint across your enterprise. Ops Manager automates key operations such as deployments, scaling, upgrades, and backups, all with the click of a button and integration with your favorite tools. It also provide the ability to monitor and alert on dozens of platform specific metrics. In this webinar, we'll cover the components of Ops Manager, as well as how it integrates and accelerates your use of MongoDB.

MongoDB Performance Tuning

MongoDB

This document discusses MongoDB performance tuning. It emphasizes that performance tuning is an obsession that requires planning schema design, statement tuning, and instance tuning in that order. It provides examples of using the MongoDB profiler and explain functions to analyze statements and identify tuning opportunities like non-covered indexes, unnecessary document scans, and low data locality. Instance tuning focuses on optimizing writes through fast update operations and secondary index usage, and optimizing reads by ensuring statements are tuned and data is sharded appropriately. Overall performance depends on properly tuning both reads and writes.

How to monitor NGINX

Server Density

10 Key MongoDB Performance Indicators

iammutex

The document discusses 10 key performance indicators for MongoDB: 1) Slow operations using the profiler 2) Replication lag by checking oplog timestamps 3) High resident memory usage indicating paging is occurring 4) High page faults 5) High write lock percentage indicating concurrency issues 6) Large reader/writer queues indicating lock contention 7) Frequent background flushing indicating I/O issues 8) Too many connections 9) High network traffic 10) Collection fragmentation leading to increased storage size It provides examples of how to check for each indicator using the db.serverStatus() command.

MongoDBが遅いときの切り分け方法

Tetsutaro Watanabe

MongoDB Ops Manager

Norberto Leite

Ops Manager is MongoDB management solution to administer, deploy and backup your MongoDB Cluster. It's complete solution that offers a Automation mechanism, auto and point-in-time backup mechanism along side with a practical Monitoring interface. Along side, and feature better integration with existing deployment and monitoring tools, Ops Manager exposes a REST API to make sure that you can use the offered functionality from your existing infrastructure and existing tools like Docker, Nagios, HP Openview. The main purpose is to allow a comprehensive experience of your environment from pleasant web GUI interface.

MongoDB Administration ~ Kevin Hanson

hungarianhc

The document provides an overview of MongoDB administration topics including: - Supported platforms for MongoDB - Common MongoDB administration tools like mongod, mongo, and mongodump - How to set up replication with replica sets for high availability and data redundancy - Popular tools for MongoDB monitoring like munin, ganglia, nagios, and cacti - How to take backups with mongodump or filesystem snapshots - The importance of indexing queries for performance and avoiding table scans

Mongo db sharding guide

Deysi Gmarra

This document provides an overview of sharding in MongoDB. It introduces sharding as a method for horizontally scaling databases across multiple machines to support large datasets and high throughput. The key components of a sharded MongoDB cluster are shards, which store data, and config servers, which maintain cluster metadata. The document discusses various sharding techniques for partitioning data and how the cluster maintains a balanced distribution through operations like splitting and balancing. It also outlines common cluster architectures and behaviors related to query routing, availability and more. Finally, it lists tutorials for deploying, managing and troubleshooting sharded clusters.

MongoDBの監視

Tetsutaro Watanabe

Best Practices for Running MongoDB on AWS - AWS May 2016 Webinar Series

Amazon Web Services

This document provides an introduction and best practices for deploying MongoDB on AWS. It describes MongoDB's document model and features like rich queries, geospatial search, and aggregation. New features in MongoDB 3.2 include in-memory storage, encrypted storage, document validation, and dynamic lookups. The document discusses MongoDB high availability using replica sets, elastic scalability through automatic sharding, and query routing. It offers guidance on AWS instance types, EBS volumes, and global deployment architectures. Lastly, it covers management and monitoring tools like Ops Manager, backup strategies, and visual profiling.

カジュアルにMongo dbのbackup機能説明

Masakazu Matsushita

Mongo performance tuning: tips and tricks

Vladimir Malyk

This document discusses various aspects of MongoDB performance. It covers monitoring MongoDB performance through the HTTP console, SSH console, and custom monitoring. It also discusses tuning MongoDB performance through optimizing indexes, avoiding growing documents, preallocating documents, and using explain queries. The conclusion provides some tips on dealing with disk fragmentation, concurrency, and why it's good to upgrade MongoDB versions.

Understanding and tuning WiredTiger, the new high performance database engine...

Ontico

MongoDB 3.0 introduced the concept of different storage engine. The new engine known as WiredTiger introduces document level MVCC locking, compression and a choice between Btree or LSM indexes. In this talk you will learn about the storage engine architecture and specifically WiredTiger, and how to tune and monitor it for best performance. MongoDB 3.0 представил новый концепт движков хранения. Новый движок известен как WiredTiger и предоставляет новый уровень документов MVCC фикс, компрессию и выбор между Btree или индексами LSM. В этом докладе вы поймете, как тюнить и мониторить архитектуры движка базы данных, а точнее WiredTiger для получения максимальной производительности.

Performance Tuning and Optimization

MongoDB

This document provides an overview of performance tuning and optimization in MongoDB. It defines performance tuning as modifying a system to handle increased load, while optimization is modifying a system to work more efficiently or use fewer resources. Measurement tools discussed include log files, the profiler, query optimizer, and explain plans. Effecting change involves measuring current performance, identifying bottlenecks, removing bottlenecks, remeasuring, and repeating. Possible areas for improvement discussed are schema design, access patterns, indexing, hardware configuration, and instance configuration. The document provides examples and best practices around indexing, access patterns, and hardware tuning.

Monitoring_with_Prometheus_Grafana_Tutorial

Tim Vaillancourt

This document provides an overview of setting up monitoring for MySQL and MongoDB servers using Prometheus and Grafana. It discusses installing and configuring Prometheus, Grafana, exporters for collecting metrics from MySQL, MongoDB and systems, and dashboards for visualizing the metrics in Grafana. The tutorial hands-on sets up Prometheus and Grafana in two virtual machines to monitor a MySQL master-slave replication setup and MongoDB cluster.

Mongodb - Scaling write performance

Daum DNA

- MongoDB allows for automatic sharding of data across multiple servers to improve write performance. However, scaling write performance is challenging due to the way B-tree indexes handle random inserts. - To improve write performance, one can partition data by time or use a hash shard key. However, these have limitations as the data grows large. The best approach is to use a low-cardinality hash prefix combined with a sequential part for the shard key. - Proper choice of shard key is crucial for scaling MongoDB's write performance as data size increases. Linear scalability is difficult to achieve and alternative databases may be better if extremely high write throughput is required.

MongoDB World 2016: Smart Strategies for Resilient Applications

MongoDB

This document discusses strategies for building resilient MongoDB applications that can handle network errors and failures. It recommends: 1. Making all database operations idempotent so they can be retried safely if an error occurs. This involves things like adding unique tokens to update operations. 2. Using driver-level monitoring of the MongoDB deployment to detect issues like primary failures and retry operations when connectivity is restored. 3. Retrying failed operations once, except for command errors, to avoid overcounting while still handling transient issues.

Monitoring MongoDB (MongoSV)

Boxed Ice

Viewers also liked (20)

MongoDB Performance Tuning and Monitoring

Mongo db monitoring 어떤 것이 좋을까(mongodb korea, 김인범)

An Introduction to MongoDB Ops Manager

MongoDB Performance Tuning

How to monitor NGINX

10 Key MongoDB Performance Indicators

MongoDBが遅いときの切り分け方法

MongoDB Ops Manager

MongoDB Administration ~ Kevin Hanson

Mongo db sharding guide

MongoDBの監視

Best Practices for Running MongoDB on AWS - AWS May 2016 Webinar Series

カジュアルにMongo dbのbackup機能説明

Mongo performance tuning: tips and tricks

Understanding and tuning WiredTiger, the new high performance database engine...

Performance Tuning and Optimization

Monitoring_with_Prometheus_Grafana_Tutorial

Mongodb - Scaling write performance

MongoDB World 2016: Smart Strategies for Resilient Applications

Monitoring MongoDB (MongoSV)

Similar to How to monitor MongoDB

Experiences from DevOps production: Deployment, performance, failure.

Server Density

Linux Memory Basics for SysAdmins - ChinaNetCloud Training

ChinaNetCloud

MariaDB Server Performance Tuning & Optimization

MariaDB plc

This document discusses various techniques for optimizing MariaDB server performance, including: - Tuning configuration settings like the buffer pool size, query cache size, and thread pool settings. - Monitoring server metrics like CPU usage, memory usage, disk I/O, and MariaDB-specific metrics. - Analyzing slow queries with the slow query log and EXPLAIN statements to identify optimization opportunities like adding indexes.

Screaming Fast Wpmu

djcp

This document discusses optimizing a WordPress installation for performance. It recommends using Nginx as a reverse proxy cache in front of Apache and PHP to cache both logged-in and logged-out content. It achieved near elimination of problems, doubled network throughput, halved memory usage, and allowed disabling of plugins by caching everything. Results included atom feeds increasing in speed from 6 requests/second to over 7000 requests/second.

Performance Whack-a-Mole Tutorial (pgCon 2009)

PostgreSQL Experts, Inc.

The document discusses tools for troubleshooting database performance issues. It describes operating system tools like ps, vmstat, iostat that can help identify hardware and resource bottlenecks. It also covers PostgreSQL-specific tools like the pg_stat views and logs that provide insight into query performance and activity. Benchmarks like pgbench, bonnie++, and the more complex DBT2 are presented as options for reproducing and analyzing problems in a controlled way. The overall approach presented is to start with less invasive tools and progress to more targeted benchmarks if needed to pinpoint severe issues.

Performance Whackamole (short version)

PostgreSQL Experts, Inc.

The document discusses performance troubleshooting for databases. It provides an overview of common issues ("moles") that can impact database performance and tools/techniques for identifying and resolving them. Some key points: - Most database performance issues are not actually problems with the database itself but other areas like hardware, OS, middleware, or application code. - A small number (less than 10%) of issues usually account for the vast majority (90%) of performance degradation. - The first steps in troubleshooting are establishing a baseline configuration and gathering performance metrics from across the full software stack using tools like OS monitoring utilities, database admin views, and benchmarks. - Common types of performance issues ("moles") include

UKOUG 2011: Practical MySQL Tuning

FromDual GmbH

This document provides a summary of a presentation on practical MySQL tuning. It discusses measuring critical system resources like CPU, memory, I/O and network usage to identify bottlenecks. It also covers rough tuning of MySQL parameters like the InnoDB buffer pool size, log file size and key buffer size. Further tuning includes application optimizations like query tuning with EXPLAIN, index tuning, and schema design. The presentation also discusses scaling MySQL through approaches like caching, sharding, replication and optimizing architecture and data distribution. Regular performance monitoring is emphasized to simulate increased load and aid capacity planning.

Virtualizing MongoDB: Cloud, EC2, OpenStack, VMs...or Dedicated?

MongoDB

The document discusses virtualizing MongoDB and deploying it on cloud platforms like AWS EC2, Google Cloud, or dedicated servers. It outlines advantages and disadvantages of virtualization versus bare metal servers. While virtualization provides flexibility, dedicated servers offer better performance and control. The document provides tips for optimizing MongoDB performance on different cloud platforms like using high-memory instances, properly sizing disks, and separating data for optimal I/O. Overall virtual machines offer flexibility but require tweaks for best performance, while bare metal/colocation is best for price and performance but has higher operations overhead.

Proper Care and Feeding of a MySQL Database for Busy Linux Administrators

Dave Stokes

Buytaert kris my_sql-pacemaker

kuchinskaya

This document discusses using Pacemaker with MySQL for high availability (HA). It covers key concepts in HA including eliminating single points of failure. It then discusses various MySQL HA solutions like replication, DRBD, MySQL Cluster, and using Linux HA tools like Pacemaker. Pacemaker manages resources across nodes to ensure services are always running, and can monitor and migrate MySQL and other services in an HA cluster. The document provides configuration examples and best practices for setting up MySQL HA with Pacemaker.

Open Source Data Deduplication

RedWireServices

Data deduplication is a hot topic in storage and saves significant disk space for many environments, with some trade offs. We’ll discuss what deduplication is and where the Open Source solutions are versus commercial offerings. Presentation will lean towards the practical – where attendees can use it in their real world projects (what works, what doesn’t, should you use in production, etcetera).

The Proper Care and Feeding of a MySQL Database for Busy Linux Admins -- SCaL...

Dave Stokes

OSMC 2019 | How to improve database Observability by Charles Judith

NETWAYS

Delivering a database service is not a simple job but to ensure that everything is working correctly your platform needs to be observable. In this talk, I’ll talk about how we make the MySQL/MariaDB databases observable. We’ll talk about the RED, USE methods, and the golden signals. You’ll discover how we dealt with the following questions “We think the database is slow”. This talk will allow you to make your databases discoverable with open source solutions.

EVCache: Lowering Costs for a Low Latency Cache with RocksDB

Scott Mansfield

EVCache is a distributed, sharded, replicated key-value store optimized for Netflix's use cases on AWS. It is based on Memcached but uses RocksDB for persistent storage, lowering costs compared to storing all data in memory. Moneta is the next generation EVCache server, using Rend and Mnemonic libraries to intelligently manage data placement in RAM and SSD. This provides high performance for both volatile and batch workloads while reducing costs by 70% compared to the original Memcached-based design.

Linuxfest Northwest Proper Care and Feeding Of a MySQL for Busy Linux Admins

Dave Stokes

This document provides tips and best practices for properly configuring and maintaining a MySQL server for busy Linux administrators. It recommends focusing on hardware resources like memory, storage, and networking. It also emphasizes the importance of backups, replication, monitoring tools, and security configurations. Proper configuration of these areas can help keep MySQL databases running smoothly and prevent issues that waste administrators' time.

Nagios Conference 2014 - Andy Brist - Nagios XI Failover and HA Solutions

Nagios

MariaDB / MySQL tripping hazard and how to get out again?

FromDual GmbH

High performance json- postgre sql vs. mongodb

Wei Shan Ang

PostgreSQL and MongoDB were benchmarked for performance on common operations like inserts, updates, and selects using a JSON document format. The key findings were: 1) PostgreSQL generally had lower latency but required extensive tuning to achieve high performance, while MongoDB delivered reasonable performance out of the box. 2) MongoDB showed unstable throughput and latency over time due to a cache eviction bug. 3) PostgreSQL did not scale well to large connection loads without connection pooling, while MongoDB scaled horizontally more easily. 4) Both databases had pros and cons for their data models, query capabilities, and upgrade processes. The optimal choice depends on an application's specific requirements.

Perfmon And Profiler 101

Quest Software

This document discusses using Perfmon and Profiler tools in SQL Server to capture metrics and traces in order to diagnose and resolve performance issues. It provides examples of using these tools to identify issues such as high disk queue lengths caused by table scans without indexes, low memory availability causing page file usage, long transaction log backups impacting drives, and inefficient cursor usage. The document emphasizes establishing a cause-and-effect relationship between metrics and traces to define effective mitigation strategies like adding indexes, memory, or changing queries.

Optimizing Your Frontend Performance

Thomas Weinert

This document discusses various techniques for optimizing frontend performance, including: 1. Using hardware, backend, and frontend optimizations like combined and minified files, CSS sprites, browser caching headers, and content delivery networks. 2. Analyzing performance with tools like Firebug, YSlow, and Google Page Speed to identify opportunities. 3. Specific techniques like gzipping, avoiding redirects, placing scripts at the bottom, and making Ajax cacheable can improve performance.

Similar to How to monitor MongoDB (20)

Experiences from DevOps production: Deployment, performance, failure.

Linux Memory Basics for SysAdmins - ChinaNetCloud Training

MariaDB Server Performance Tuning & Optimization

Screaming Fast Wpmu

Performance Whack-a-Mole Tutorial (pgCon 2009)

Performance Whackamole (short version)

UKOUG 2011: Practical MySQL Tuning

Virtualizing MongoDB: Cloud, EC2, OpenStack, VMs...or Dedicated?

Proper Care and Feeding of a MySQL Database for Busy Linux Administrators

Buytaert kris my_sql-pacemaker

Open Source Data Deduplication

The Proper Care and Feeding of a MySQL Database for Busy Linux Admins -- SCaL...

OSMC 2019 | How to improve database Observability by Charles Judith

EVCache: Lowering Costs for a Low Latency Cache with RocksDB

Linuxfest Northwest Proper Care and Feeding Of a MySQL for Busy Linux Admins

Nagios Conference 2014 - Andy Brist - Nagios XI Failover and HA Solutions

MariaDB / MySQL tripping hazard and how to get out again?

High performance json- postgre sql vs. mongodb

Perfmon And Profiler 101

Optimizing Your Frontend Performance

More from Server Density

Content marketing @ Server Density

Server Density

Flight training for DevOps & HumanOps - IncontroDevOps 2016

Server Density

Flight training for DevOps

Server Density

This document discusses improving incident response procedures through practices such as checklists, documented procedures, realistic incident simulations and postmortems. It recommends extended use of checklists to guide responses while still allowing for experience and independent thought. Regular incident response simulations that test both general processes and specific failures can help refine procedures and build confidence. Postmortems should objectively review incidents, suggest improvements and run through scenarios again over time to prevent complacency.

Handling incidents

Server Density

The document discusses how to handle incidents, downtime, and outages. It notes that the cost of downtime for companies in Q1 2015 was $2.9 billion, $870 million, and $4.1 billion. It recommends preparing for incidents by having on-call staff and documentation, responding quickly by following an incident response checklist and notifying stakeholders, and performing a postmortem within days to analyze what failed and how to prevent future issues.

Scaling humans - Ops teams and incident management

Server Density

The document discusses the costs of downtime for companies and best practices for incident management teams to prepare for, respond to, and review incidents to minimize downtime costs. It notes that downtime costs companies billions per quarter and recommends teams prepare documentation and contact information, have on-call rotation schedules, log all responses to incidents, provide frequent status updates, gather teams to escalate incidents as needed, and conduct post-mortem reviews within days of an incident.

Briefing: Containers

Server Density

Containers seem to have suddenly become the hot new thing everyone is talking about, but what are they? Why are they important? How should you use them and what does it mean for cloud infrastructure? This talk will examine the history, technical details and strategy around containerisation from the perspective of developers and operations, consider internal container OSs like Rocket and Ubuntu Core as well as management layers like Docker and Apache Mesos and take a look at why cloud providers are launching their own services around them. Presented by David Mytton at Datacloud Monaco 2015-06-04

Why puppet? Why now?

Server Density

Why Puppet? Why now? Can you get by without using any config management? You probably think don't have time, or that your project is too small. What can using Puppet really add? How can you justify investing time up front? Maybe you can just do it later? Getting started with config management can often seem like a big project, especially if you only manage a few systems or have a small team. This talk will examine why you should use Puppet from the beginning. It will examine what you can do with Puppet that couldn't do otherwise, how much time it will save and why it's especially important if you think your project has even the smallest chance of scaling in the future. Presented by David Mytton at Puppet Camp London 2015-04-13

Infrastructure choices - cloud vs colo vs bare metal

Server Density

This document discusses the differences between cloud, colocation, and bare metal infrastructure options. It covers key considerations for performance including CPU, memory, disk, and network latency and bandwidth. Colocation provides hardware at a specific location while maintaining internal skills, but has costs for total spend, hardware specifications, and power usage. Cloud infrastructure offers elastic workloads and support for demand spikes and unknown requirements, but bare metal is preferable for managed hardware replacement and networking needs. Overall, the best option depends on an organization's specific workload characteristics and skills.

Navigating the customer lifecycle

Server Density

DevOps Incident Handling - Making friends not enemies.

Server Density

High performance Infrastructure Oct 2013

Server Density

The document discusses high performance infrastructure for Server Density which includes 150 servers that have been running since June 2009 and migrated from MySQL to MongoDB. It stores 25TB of data per month. Key aspects of performance discussed are using fast networks like 10 Gigabit Ethernet on AWS, ensuring high memory, using SSDs over spinning disks for performance, and factors like replication lag based on location. The document also compares options like using cloud, dedicated servers, or colocation and discusses monitoring, backups, dealing with outages, and other operational aspects.

Puppet at the centre of everything

Server Density

The document discusses Server Density's architecture which includes 100 Ubuntu servers with 50% being virtual, using Nginx, Python, and MongoDB. It handles 25TB of data per month. Puppet is used for configuration, failover, code deploys, and system updates. The document also considers colocating servers versus using a dedicated provider and factors like hardware specs, costs, skills required, and fun.

NoSQL Infrastructure - Late 2013

Server Density

NoSQL databases are often touted for their performance and whilst it's true that they usually offer great performance out of the box, it still really depends on how you deploy your infrastructure. Dedicated vs cloud? In memory vs on disk? Spindal vs SSD? Replication lag. Multi data centre deployment. This talk considers all the infrastructure requirements of a successful high performance infrastructure with hints and tips that can be applied to any NoSQL technology. It includes things like OS tweaks, disk benchmarks, replication, monitoring and backups.

Remote startup - building a company from everywhere in the world

Server Density

This document discusses how Server Density grew from 2 employees in 2009 to 12 employees in 2013 while being fully remote. It outlines the company's timeline and some advantages of being fully remote such as access to worldwide talent, lower costs, and no distractions of an office. However, it also notes disadvantages like collaboration being more difficult without in-person interactions. While the company added an office in 2012, the document emphasizes that working remotely is a mindset that is difficult to adopt after initially co-locating. Effective communication and availability are important for fully distributed teams.

NoSQL Infrastructure

Server Density

This document discusses MongoDB infrastructure at Server Density. It notes that Server Density uses 27 MongoDB nodes to store 20TB of data per month from their MySQL database. Some key reasons for choosing MongoDB include replication, official drivers, easy deployment, and fast performance out of the box. The document then discusses various MongoDB performance and infrastructure considerations like network throughput, replication lag, failover processes, disk types, backups, and monitoring.

StartOps: Growing an ops team from 1 founder

Server Density

Bootstrapped startups don't have the luxury of a full team of ops engineers available to respond to issues 24/7, so how can you survive on your own? This talk will tell the story of how to run your infrastructure as a single founder through to growing that into a team of on call engineers. It will include some interesting war stories as well as tips and suggestions for how to run ops at a startup. Presented at DevOpsDays London 2013 by David Mytton.

MongoDB: Optimising for Performance, Scale & Analytics

Server Density

MongoDB is easy to download and run locally but requires some thought and further understanding when deploying to production. At scale, schema design, indexes and query patterns really matter. So does data structure on disk, sharding, replication and data centre awareness. This talk will examine these factors in the context of analytics, and more generally, to help you optimise MongoDB for any scale. Presented at MongoDB Days London 2013 by David Mytton.

Puppet Camp Ghent 2013

Server Density

This document discusses adding Forge modules to Puppet Enterprise. It describes moving the HTTP load balancer from Pound to nginx, keeping existing manifests pulled from GitHub, and using the Puppet Forge to install the puppetlabs/nginx module or integrating it via Git submodules. It also covers parameterizing classes on the Puppet Enterprise console and merging site.pp files, as well as updating nginx configurations on the fly and considering alternative nginx modules on the Forge.

Puppet Camp 2012

Server Density

Going from zero to Puppet by Pedro Pessoa, Operations Engineer at Server Density. Abstract: Using out-of-the-box Puppet for non-sysadmin work - steps from going from no config management to managing 100 nodes and allowing non-sysadmin tasks to be performed. Speaker Bio: Linux admin for 10+ years. Java/Python/C developer 12+ years. Ops engineer at http://www.serverdensity.com - a hosted server and website monitoring service. Currently processing 12TB+ per month into MongoDB running on dedicated and virtual instances. www.serverdensity.com/puppetcamp/

More from Server Density (19)

Content marketing @ Server Density

Flight training for DevOps & HumanOps - IncontroDevOps 2016

Flight training for DevOps

Handling incidents

Scaling humans - Ops teams and incident management

Briefing: Containers

Why puppet? Why now?

Infrastructure choices - cloud vs colo vs bare metal

Navigating the customer lifecycle

DevOps Incident Handling - Making friends not enemies.

High performance Infrastructure Oct 2013

Puppet at the centre of everything

NoSQL Infrastructure - Late 2013

Remote startup - building a company from everywhere in the world

NoSQL Infrastructure

StartOps: Growing an ops team from 1 founder

MongoDB: Optimising for Performance, Scale & Analytics

Puppet Camp Ghent 2013

Puppet Camp 2012

Recently uploaded

PCI PIN Basics Webinar from the Controlcase Team

ControlCase

Large Language Model (LLM) and it’s Geospatial Applications

Rohit Gautam

20240609 QFM020 Irresponsible AI Reading List May 2024

Matthew Sinclair

Why You Should Replace Windows 11 with Nitrux Linux 3.5.0 for enhanced perfor...

SOFTTECHHUB

The choice of an operating system plays a pivotal role in shaping our computing experience. For decades, Microsoft's Windows has dominated the market, offering a familiar and widely adopted platform for personal and professional use. However, as technological advancements continue to push the boundaries of innovation, alternative operating systems have emerged, challenging the status quo and offering users a fresh perspective on computing. One such alternative that has garnered significant attention and acclaim is Nitrux Linux 3.5.0, a sleek, powerful, and user-friendly Linux distribution that promises to redefine the way we interact with our devices. With its focus on performance, security, and customization, Nitrux Linux presents a compelling case for those seeking to break free from the constraints of proprietary software and embrace the freedom and flexibility of open-source computing.

Removing Uninteresting Bytes in Software Fuzzing

Aftab Hussain

Imagine a world where software fuzzing, the process of mutating bytes in test seeds to uncover hidden and erroneous program behaviors, becomes faster and more effective. A lot depends on the initial seeds, which can significantly dictate the trajectory of a fuzzing campaign, particularly in terms of how long it takes to uncover interesting behaviour in your code. We introduce DIAR, a technique designed to speedup fuzzing campaigns by pinpointing and eliminating those uninteresting bytes in the seeds. Picture this: instead of wasting valuable resources on meaningless mutations in large, bloated seeds, DIAR removes the unnecessary bytes, streamlining the entire process. In this work, we equipped AFL, a popular fuzzer, with DIAR and examined two critical Linux libraries -- Libxml's xmllint, a tool for parsing xml documents, and Binutil's readelf, an essential debugging and security analysis command-line tool used to display detailed information about ELF (Executable and Linkable Format). Our preliminary results show that AFL+DIAR does not only discover new paths more quickly but also achieves higher coverage overall. This work thus showcases how starting with lean and optimized seeds can lead to faster, more comprehensive fuzzing campaigns -- and DIAR helps you find such seeds. - These are slides of the talk given at IEEE International Conference on Software Testing Verification and Validation Workshop, ICSTW 2022.

Essentials of Automations: The Art of Triggers and Actions in FME

Safe Software

In this second installment of our Essentials of Automations webinar series, we’ll explore the landscape of triggers and actions, guiding you through the nuances of authoring and adapting workspaces for seamless automations. Gain an understanding of the full spectrum of triggers and actions available in FME, empowering you to enhance your workspaces for efficient automation. We’ll kick things off by showcasing the most commonly used event-based triggers, introducing you to various automation workflows like manual triggers, schedules, directory watchers, and more. Plus, see how these elements play out in real scenarios. Whether you’re tweaking your current setup or building from the ground up, this session will arm you with the tools and insights needed to transform your FME usage into a powerhouse of productivity. Join us to discover effective strategies that simplify complex processes, enhancing your productivity and transforming your data management practices with FME. Let’s turn complexity into clarity and make your workspaces work wonders!

Artificial Intelligence for XMLDevelopment

Octavian Nadolu

In the rapidly evolving landscape of technologies, XML continues to play a vital role in structuring, storing, and transporting data across diverse systems. The recent advancements in artificial intelligence (AI) present new methodologies for enhancing XML development workflows, introducing efficiency, automation, and intelligent capabilities. This presentation will outline the scope and perspective of utilizing AI in XML development. The potential benefits and the possible pitfalls will be highlighted, providing a balanced view of the subject. We will explore the capabilities of AI in understanding XML markup languages and autonomously creating structured XML content. Additionally, we will examine the capacity of AI to enrich plain text with appropriate XML markup. Practical examples and methodological guidelines will be provided to elucidate how AI can be effectively prompted to interpret and generate accurate XML markup. Further emphasis will be placed on the role of AI in developing XSLT, or schemas such as XSD and Schematron. We will address the techniques and strategies adopted to create prompts for generating code, explaining code, or refactoring the code, and the results achieved. The discussion will extend to how AI can be used to transform XML content. In particular, the focus will be on the use of AI XPath extension functions in XSLT, Schematron, Schematron Quick Fixes, or for XML content refactoring. The presentation aims to deliver a comprehensive overview of AI usage in XML development, providing attendees with the necessary knowledge to make informed decisions. Whether you’re at the early stages of adopting AI or considering integrating it in advanced XML development, this presentation will cover all levels of expertise. By highlighting the potential advantages and challenges of integrating AI with XML development tools and languages, the presentation seeks to inspire thoughtful conversation around the future of XML development. We’ll not only delve into the technical aspects of AI-powered XML development but also discuss practical implications and possible future directions.

20240605 QFM017 Machine Intelligence Reading List May 2024

Matthew Sinclair

GraphSummit Singapore | Graphing Success: Revolutionising Organisational Stru...

Neo4j

Sudheer Mechineni, Head of Application Frameworks, Standard Chartered Bank Discover how Standard Chartered Bank harnessed the power of Neo4j to transform complex data access challenges into a dynamic, scalable graph database solution. This keynote will cover their journey from initial adoption to deploying a fully automated, enterprise-grade causal cluster, highlighting key strategies for modelling organisational changes and ensuring robust disaster recovery. Learn how these innovations have not only enhanced Standard Chartered Bank’s data infrastructure but also positioned them as pioneers in the banking sector’s adoption of graph technology.

GraphSummit Singapore | Enhancing Changi Airport Group's Passenger Experience...

Neo4j

Dr. Sean Tan, Head of Data Science, Changi Airport Group Discover how Changi Airport Group (CAG) leverages graph technologies and generative AI to revolutionize their search capabilities. This session delves into the unique search needs of CAG’s diverse passengers and customers, showcasing how graph data structures enhance the accuracy and relevance of AI-generated search results, mitigating the risk of “hallucinations” and improving the overall customer journey.

UiPath Test Automation using UiPath Test Suite series, part 6

DianaGray10

Welcome to UiPath Test Automation using UiPath Test Suite series part 6. In this session, we will cover Test Automation with generative AI and Open AI. UiPath Test Automation with generative AI and Open AI webinar offers an in-depth exploration of leveraging cutting-edge technologies for test automation within the UiPath platform. Attendees will delve into the integration of generative AI, a test automation solution, with Open AI advanced natural language processing capabilities. Throughout the session, participants will discover how this synergy empowers testers to automate repetitive tasks, enhance testing accuracy, and expedite the software testing life cycle. Topics covered include the seamless integration process, practical use cases, and the benefits of harnessing AI-driven automation for UiPath testing initiatives. By attending this webinar, testers, and automation professionals can gain valuable insights into harnessing the power of AI to optimize their test automation workflows within the UiPath ecosystem, ultimately driving efficiency and quality in software development processes. What will you get from this session? 1. Insights into integrating generative AI. 2. Understanding how this integration enhances test automation within the UiPath platform 3. Practical demonstrations 4. Exploration of real-world use cases illustrating the benefits of AI-driven test automation for UiPath Topics covered: What is generative AI Test Automation with generative AI and Open AI. UiPath integration with generative AI Speaker: Deepak Rai, Automation Practice Lead, Boundaryless Group and UiPath MVP

20240607 QFM018 Elixir Reading List May 2024

Matthew Sinclair

Introduction to CHERI technology - Cybersecurity

mikeeftimakis1

“I’m still / I’m still / Chaining from the Block”

Claudio Di Ciccio

GraphSummit Singapore | Neo4j Product Vision & Roadmap - Q2 2024

Neo4j

UiPath Test Automation using UiPath Test Suite series, part 5

DianaGray10

Mind map of terminologies used in context of Generative AI

Kumud Singh

National Security Agency - NSA mobile device best practices

Quotidiano Piemontese

Securing your Kubernetes cluster_ a step-by-step guide to success !

KatiaHIMEUR1

Today, after several years of existence, an extremely active community and an ultra-dynamic ecosystem, Kubernetes has established itself as the de facto standard in container orchestration. Thanks to a wide range of managed services, it has never been so easy to set up a ready-to-use Kubernetes cluster. However, this ease of use means that the subject of security in Kubernetes is often left for later, or even neglected. This exposes companies to significant risks. In this talk, I'll show you step-by-step how to secure your Kubernetes cluster for greater peace of mind and reliability.

Unlock the Future of Search with MongoDB Atlas_ Vector Search Unleashed.pdf

Malak Abu Hammad

Discover how MongoDB Atlas and vector search technology can revolutionize your application's search capabilities. This comprehensive presentation covers: * What is Vector Search? * Importance and benefits of vector search * Practical use cases across various industries * Step-by-step implementation guide * Live demos with code snippets * Enhancing LLM capabilities with vector search * Best practices and optimization strategies Perfect for developers, AI enthusiasts, and tech leaders. Learn how to leverage MongoDB Atlas to deliver highly relevant, context-aware search results, transforming your data retrieval process. Stay ahead in tech innovation and maximize the potential of your applications. #MongoDB #VectorSearch #AI #SemanticSearch #TechInnovation #DataScience #LLM #MachineLearning #SearchTechnology

Recently uploaded (20)

PCI PIN Basics Webinar from the Controlcase Team

Large Language Model (LLM) and it’s Geospatial Applications

20240609 QFM020 Irresponsible AI Reading List May 2024

Why You Should Replace Windows 11 with Nitrux Linux 3.5.0 for enhanced perfor...

Removing Uninteresting Bytes in Software Fuzzing

Essentials of Automations: The Art of Triggers and Actions in FME

Artificial Intelligence for XMLDevelopment

20240605 QFM017 Machine Intelligence Reading List May 2024

GraphSummit Singapore | Graphing Success: Revolutionising Organisational Stru...

GraphSummit Singapore | Enhancing Changi Airport Group's Passenger Experience...

UiPath Test Automation using UiPath Test Suite series, part 6

20240607 QFM018 Elixir Reading List May 2024

Introduction to CHERI technology - Cybersecurity

“I’m still / I’m still / Chaining from the Block”

GraphSummit Singapore | Neo4j Product Vision & Roadmap - Q2 2024

UiPath Test Automation using UiPath Test Suite series, part 5

Mind map of terminologies used in context of Generative AI

National Security Agency - NSA mobile device best practices

Securing your Kubernetes cluster_ a step-by-step guide to success !

Unlock the Future of Search with MongoDB Atlas_ Vector Search Unleashed.pdf

How to monitor MongoDB

1. How to monitor: MongoDB David Mytton Hangout on Air - Sept 2014 https://blog.serverdensity.com/monitor-mongodb/

2. David Mytton

4. Server Density Architecture

5. Server Density Architecture ● ~100 servers - Ubuntu 12.04

6. Server Density Architecture ● ~100 servers - Ubuntu 12.04 ● 50:50 virtual/dedicated

7. Server Density Architecture ● ~100 servers - Ubuntu 12.04 ● 50:50 virtual/dedicated ● 200TB/m processed data

8. Server Density Architecture ● ~100 servers - Ubuntu 12.04 ● 50:50 virtual/dedicated ● 200TB/m processed data ● Nginx, Python, MongoDB

9. Server Density Architecture ● ~100 servers - Ubuntu 12.04 ● 50:50 virtual/dedicated ● 200TB/m processed data ● Nginx, Python, MongoDB ● Softlayer > 1TB RAM, 5TB SSDs

10. Key metrics ● Oplog replication lag ● Replica state ● Lock % ● Disk i/o % utilization

11. Oplog replication lag ● Replica sets: master/slave

12. Oplog replication lag ● Replica sets: master/slave ● Async i.e. eventually consistent

13. Oplog replication lag ● Replica sets: master/slave ● Async i.e. eventually consistent ● Write concern

14. Oplog replication lag

15. Oplog replication lag https://blog.serverdensity.com/mongodb-benchmarks/

16. Oplog replication lag ● Replica sets: master/slave ● Async i.e. eventually consistent ● Write concern ● Falling behind

17. Reasons for repl falling behind ● Network problems

18. Reasons for repl falling behind ● Network problems ● Hardware problems

19. Reasons for repl falling behind ● Network problems ● Hardware problems ● Shard chunk migrations

20. Reasons for repl falling behind ● Network problems ● Hardware problems ● Shard chunk migrations ● MongoDB bugs

21. Replica state ● Primary / secondary

22. Replica state ● Primary / secondary ● Alert on state change

23. Lock % ● Database locking (2.6)

24. Lock % ● Database locking (2.6) ● Sometimes a problem:

25. Lock % ● Database locking (2.6) ● Sometimes a problem: ● Nearing 100%

26. Lock % ● Database locking (2.6) ● Sometimes a problem: ● Nearing 100% ● Constantly high

27. Lock % ● Database locking (2.6) ● Sometimes a problem: ● Nearing 100% ● Constantly high ● Slows replication

28. Disk i/o % utilization ● Hardware limits

29. Disk i/o % utilization ● Hardware limits ● Nearing 100%

30. Disk i/o % utilization ● Hardware limits ● Nearing 100% ● Constantly high

31. Disk i/o % utilization ● Hardware limits ● Nearing 100% ● Constantly high ● Spinning -> SSD

32. Disk i/o % utilization https://blog.serverdensity.com/mongodb-performance-ssds-vs-spindle-sas-drives/

33. Disk i/o % utilization https://blog.serverdensity.com/mongodb-benchmarks/

34. Disk i/o % utilization ● Hardware limits ● Nearing 100% ● Constantly high ● Spinning -> SSD ● Slow queries, hangs, slow repl

35. Non-critical metrics to watch ● Memory usage

36. Non-critical metrics to watch ● Memory usage ● Page faults

37. Non-critical metrics to watch ● Memory usage ● Page faults ● Connections

38. Non-critical metrics to watch ● Memory usage ● Page faults ● Connections ● Shard chunk distribution

39. Non-critical metrics to watch

40. Monitoring tools ● mongostat ● mongotop ● rs.status() ● sh.status()

41. rs.status()

42. sh.status()

43. Server Density

44. MMS

45. Summary ● Critical alerts on key metrics

46. Key metrics ● Oplog replication lag ● Replica state ● Lock % ● Disk i/o % utilization

47. Summary ● Critical alerts on key metrics

48. Summary ● Critical alerts on key metrics ● Watch non-critical

49. Summary ● Critical alerts on key metrics ● Watch non-critical ● Manual tools for real time

50. Summary ● Critical alerts on key metrics ● Watch non-critical ● Manual tools for real time ● Set up a monitoring product

51. Useful resources ● http://docs.mongodb.org/manual/administration/monitoring/ ● https://blog.serverdensity.com/monitor-mongodb ● https://blog.serverdensity.com

52. どもありがとうございます＠davidmytton david@serverdensity.com blog.serverdensity.com

How to monitor MongoDB

Recommended

Recommended

More Related Content

What's hot

What's hot (20)

Viewers also liked

Viewers also liked (20)

Similar to How to monitor MongoDB

Similar to How to monitor MongoDB (20)

More from Server Density

More from Server Density (19)

Recently uploaded

Recently uploaded (20)

How to monitor MongoDB