Monitoring

and performance

5 Ws and 1 H
Benoit Delbosc

1
Why?
●

Solves issues

●

Understand the limits

●

Shorten the decision making cycle

2
What?
●

Few predetermined metrics

●

Collect all possible logs and metrics

➔

Focus on
➔

metrics that measure the work...
When?
●

Only when something is going wonky

●

All the time

➔

Gives you a historical context

4
Where?
●

Poll your application to get information

●

Application pushes metrics

➔

Gives you real time feedback

5
Who?
●

Sysadmin

●

Dev

●

Ops

➔

Learn to speak both languages

6
How?
●

Collect Nuxeo metrics with Coda Hale Metrics

●

Collect other metrics with Diamond

●

All metrics go to Graphite...
How? overview

8
How? Graphite dashboard

9
How? visualize with other tools

10
How? logstash dashboard

11
Conclusion
●

Monitoring is a tool
●

●

You need to learn its strengths and weaknesses

Monitoring is mandatory for a sca...
Resources
●

Monitoring (at) Nuxeo By Mathieu Guillaume

●

http://graphite.readthedocs.org/

●

http://logstash.net/

●

...
Thank you!

14
Upcoming SlideShare
Loading in...5
×

[Nuxeo World 2013] MONITORING AND PERFORMANCE - BENOIT DELBOSC

583

Published on

This talk will be delivered by the man behind Funkload, a tool used for functional and load testing of web applications. Benoit will talk about how we manage monitoring and performance for the Nuxeo Platform, and how we provide our tools & know-how in application monitoring to our customers. There are some interesting new features and improvements in this area that you need to know about.

Published in: Technology, Business
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
583
On Slideshare
0
From Embeds
0
Number of Embeds
2
Actions
Shares
0
Downloads
9
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

[Nuxeo World 2013] MONITORING AND PERFORMANCE - BENOIT DELBOSC

  1. 1. Monitoring and performance 5 Ws and 1 H Benoit Delbosc 1
  2. 2. Why? ● Solves issues ● Understand the limits ● Shorten the decision making cycle 2
  3. 3. What? ● Few predetermined metrics ● Collect all possible logs and metrics ➔ Focus on ➔ metrics that measure the work being done ➔ Usage, Saturation and Errors of resources (USE method) 3
  4. 4. When? ● Only when something is going wonky ● All the time ➔ Gives you a historical context 4
  5. 5. Where? ● Poll your application to get information ● Application pushes metrics ➔ Gives you real time feedback 5
  6. 6. Who? ● Sysadmin ● Dev ● Ops ➔ Learn to speak both languages 6
  7. 7. How? ● Collect Nuxeo metrics with Coda Hale Metrics ● Collect other metrics with Diamond ● All metrics go to Graphite ● Logs become structured logs using logstash ● Rieman takes care of alerts 7
  8. 8. How? overview 8
  9. 9. How? Graphite dashboard 9
  10. 10. How? visualize with other tools 10
  11. 11. How? logstash dashboard 11
  12. 12. Conclusion ● Monitoring is a tool ● ● You need to learn its strengths and weaknesses Monitoring is mandatory for a scalable framework and sustainable application 12
  13. 13. Resources ● Monitoring (at) Nuxeo By Mathieu Guillaume ● http://graphite.readthedocs.org/ ● http://logstash.net/ ● http://metrics.codahale.com/ ● http://github.com/BrightcoveOS/Diamond/ ● http://riemann.io/ 13
  14. 14. Thank you! 14
  1. A particular slide catching your eye?

    Clipping is a handy way to collect important slides you want to go back to later.

×