![117/15/15
|
Simple Setup for Agent and MongoDB Monitoring
sudo curl -o /etc/apt/sources.list.d/stackdriver.list http://repo.stackdriver.com/trusty.list
curl --silent https://app.stackdriver.com/RPM-GPG-KEY-stackdriver | sudo apt-key add -
sudo apt-get update
sudo apt-get install stackdriver-agent
python-netifaces python-psutil stackdriver-extractor
[ Enter your API Key here ]
# sudo /opt/stackdriver/stack-config --api-key <API-Key>
sudo vi /opt/stackdriver/collectd/etc/collectd.d/mongodb.conf
LoadPlugin mongodb
<Plugin "mongodb">
Host "localhost”
Port "27017”
# If you restricted access to the database, you can
# set the username and password here
# User "user_name”
# Password "user_password"
# For performance/eventually consistent trade-offs you may add this line
# PreferSecondaryQuery true
</Plugin>
sudo service stackdriver-agent restart](https://image.slidesharecdn.com/mongodbusersgroup20150714v1-150717173013-lva1-app6891/85/Using-Stackdriver-with-MongoDB-11-320.jpg)
Using Stackdriver with MongoDB
- 1. 7/15/15 Using Stackdriver with MongoDB Cloud Monitoring Made Easy Bryan Ignatow, Director of Network Engineering
- 2. 27/15/15 | Who is OléMedia? • OléMedia brings next generation television to foreign markets through the use of innovative OTT solutions, including: – Traditional TV content delivery – A customizable experience – Targeted advertising delivery – And advanced search capabilities • Any Device, Anytime • Currently broadcasting in the Philippines and Mexico
- 3. 37/15/15 | OléMedia Operations • Bryan Ignatow, Director of Network Engineering – Leads the technical operations group – Technical Operations is responsible for the care and feeding of: • Networks: Firewalls, Switches, Access Points, and other appliances • Network Services: DNS, Corporate and Customer Email • Servers: Local and Cloud-Based infrastructure • Cloud Services: Amazon AWS and EC2 services • Service Monitoring: Infrastructure, Services, Databases, and Video – Over 30 years of industry experience in operations – Over 15 years experience in high-end, mission critical monitoring for the service provider industry
- 4. 47/15/15 | Why Stackdriver?
- 5. 57/15/15 | Why Stackdriver? • We chose Stackdriver since we had a large Amazon AWS presence: – Amazon CloudWatch Metrics are good but we needed more – Amazon’s monitoring interface is very basic – We were wanting a single pane of glass approach • Stackdriver brings us this single pane of glass – Easy to setup – Starts right out of the box without agents installed – Consolidated information, including AWS status and costs – Once you install agents, the monitoring gains further depth and detail
- 6. 67/15/15 | Stackdriver Lets explore a bit, shall we?
- 7. 77/15/15 | Stackdriver Custom Metrics • Since Stackdriver provides the capability to inject custom metrics, which can then leverage all the graphic and reporting capabilities of their portal, we chose to develop a script around MongoDB profiling: – Enabling profiling per database with db.setProfilingLevel(1,100) – Collecting profiled transactions with db.system.profile.find() – Organizing the profiled transactions into aggregate metrics like longtrans_<op>_<ns> – Preserving these aggregate metrics across monitoring/collection invocations, so we can maintain zero-value lines and graphic continuity in the reporting interface – Metrics injected into Stackdriver are organized by AWS Instance ID
- 8. 87/15/15 | Stackdriver Custom Metrics (con’t) • Challenges so far in the development process: – Profiling has been found to “turn itself off” on occasion and we are researching why – We’ve optimized our queries with application server caching, which gives us limited data to experiment with – The monitoring/collecting script has (as usual) become complex, in order to provide maximum flexibility in collecting and organizing metrics, as we didn’t know precisely what we wanted to collect and how we wanted to organize it – Stackdriver only allows metrics within the last two hours to be injected (limits testing in our development environment which is not as busy as production)
- 9. 97/15/15 | Conclusion • Stackdriver includes a 14 day free trial and is very easy to get started with • Its easy to install and configure the agent and add monitoring for MongoDB, Apache, nginx, and Tomcat • The documentation is good • And the product looks better than most monitoring products out there The jury is still out as to the usefulness of custom metrics derived from MongoDB profiling
- 10. 107/15/15 | Questions?
- 11. 117/15/15 | Simple Setup for Agent and MongoDB Monitoring sudo curl -o /etc/apt/sources.list.d/stackdriver.list http://repo.stackdriver.com/trusty.list curl --silent https://app.stackdriver.com/RPM-GPG-KEY-stackdriver | sudo apt-key add - sudo apt-get update sudo apt-get install stackdriver-agent python-netifaces python-psutil stackdriver-extractor [ Enter your API Key here ] # sudo /opt/stackdriver/stack-config --api-key <API-Key> sudo vi /opt/stackdriver/collectd/etc/collectd.d/mongodb.conf LoadPlugin mongodb <Plugin "mongodb"> Host "localhost” Port "27017” # If you restricted access to the database, you can # set the username and password here # User "user_name” # Password "user_password" # For performance/eventually consistent trade-offs you may add this line # PreferSecondaryQuery true </Plugin> sudo service stackdriver-agent restart