15
Monitoring that does suck DevOpsDays Rome 2012 not

Monitoring that does not suck

Embed Size (px)

DESCRIPTION

A good open-source monitoring architecture should have the following qualities: composable, self-service, resilient, automated, correlative and show craftsmanship. These are essential for any open-source monitoring to have. First, no assembly required. It works out of the box. Second, it’s self-service. There’s no permission to ask to use it. Everyone can use it. Third, it’s resilient. It works all the time, especially when you’re in the middle of a crisis. Fourth, it’s automated, completely API-driven, deployment is automated. Fifth, it’s correlative, it lets you graph and correlate any metric from anywhere. Sixth it shows good craftsmanship, it’s a pleasure to use. We’ve built such a system. Learn more at https://www.datadoghq.com/

Citation preview

Page 1: Monitoring that does not suck

Monitoring that does suck

DevOpsDays Rome 2012

not

Page 2: Monitoring that does not suck

@alq

Hi, my name is Alexis. @alq on twitter.I’d like to take just a few minutes to talk about monitoring.

Page 3: Monitoring that does not suck

Jason Dixon

The Good, The Bad, The

Fucking Terrible and a

Glimpse Into Our Future

The State

of Open Source

Monitoring:

Friday, October 5, 12

John Willis says he’s never seen the asshole element at DevOpsDays. Coincidentally, this is my first visit to DevOpsDays.

Who here thinks monitoring sucks? Ok, this talk is not for you. I want to talk to people who love monitoring and want to make it better. After the end of this talk today I hope that we’ve started a new discussion around monitoring and the guys who come after me need to update their slides.

http://dtdg.co/obfuscurity-in-rome

If you attended yesterday morning’s presentations, you saw Jason’s talk. He gave us a great overview of the state of open-source monitoring. If you have not seen it, here’s the link.

Page 4: Monitoring that does not suck

composableself-service

resilientautomatedcorrelative

craftsmanship

(bad-ass robot)

Friday, October 5, 12

Last but not least, it's beautiful. It's a pleasure to use. It removes impedance from the user experience and rewards us simply by using it.

What do we end up with?He suggested that a good open-source monitoring architecture should have the following qualities:composable, self-service, resilient, automated, correlative and show craftsmanship.

I wholeheartedly agree with him. These are essential for an open-source monitoring to have.

Page 5: Monitoring that does not suck

CriticallyImportant

And monitoring is critically important to your job.

Page 6: Monitoring that does not suck

Now if you have the expertise, the time and the will to put a great open-source monitoring solution together, you should. There’s a lot to learn and contribute in the process.

But I recognize that not everyone has the bandwidth to do that. You may already be applying your time and effort toward some other equally critical project.

In other words you need your monitoring to work and you need it to work right now and forever after.

Page 7: Monitoring that does not suck

Monitoring that does suck not

Of course you want monitoring that does not suck. So if you’re open to not putting it together yourself I submit to you the qualities that such a monitoring service should have.

Page 8: Monitoring that does not suck

no assembly req’d

First, no assembly required. It works out of the box.Second, it’s self-service. There’s no permission to ask to use it. Everyone can use it.Third, it’s resilient. It works all the time, especially when you’re in the middle of a crisis.Fourth, it’s automated, completely API-driven, deployment is automated.Fifth, it’s correlative, it lets you graph and correlate any metric from anywhere.Sixth it shows good craftsmanship, it’s a pleasure to use.

We’ve built such a system.

Page 9: Monitoring that does not suck

no assembly req’d

self-service

First, no assembly required. It works out of the box.Second, it’s self-service. There’s no permission to ask to use it. Everyone can use it.Third, it’s resilient. It works all the time, especially when you’re in the middle of a crisis.Fourth, it’s automated, completely API-driven, deployment is automated.Fifth, it’s correlative, it lets you graph and correlate any metric from anywhere.Sixth it shows good craftsmanship, it’s a pleasure to use.

We’ve built such a system.

Page 10: Monitoring that does not suck

no assembly req’d

self-service

resilient

First, no assembly required. It works out of the box.Second, it’s self-service. There’s no permission to ask to use it. Everyone can use it.Third, it’s resilient. It works all the time, especially when you’re in the middle of a crisis.Fourth, it’s automated, completely API-driven, deployment is automated.Fifth, it’s correlative, it lets you graph and correlate any metric from anywhere.Sixth it shows good craftsmanship, it’s a pleasure to use.

We’ve built such a system.

Page 11: Monitoring that does not suck

no assembly req’d

self-service

resilient

automated

First, no assembly required. It works out of the box.Second, it’s self-service. There’s no permission to ask to use it. Everyone can use it.Third, it’s resilient. It works all the time, especially when you’re in the middle of a crisis.Fourth, it’s automated, completely API-driven, deployment is automated.Fifth, it’s correlative, it lets you graph and correlate any metric from anywhere.Sixth it shows good craftsmanship, it’s a pleasure to use.

We’ve built such a system.

Page 12: Monitoring that does not suck

no assembly req’d

self-service

resilient

automated

correlative

First, no assembly required. It works out of the box.Second, it’s self-service. There’s no permission to ask to use it. Everyone can use it.Third, it’s resilient. It works all the time, especially when you’re in the middle of a crisis.Fourth, it’s automated, completely API-driven, deployment is automated.Fifth, it’s correlative, it lets you graph and correlate any metric from anywhere.Sixth it shows good craftsmanship, it’s a pleasure to use.

We’ve built such a system.

Page 13: Monitoring that does not suck

no assembly req’d

self-service

resilient

automated

correlativecraftsmanship

First, no assembly required. It works out of the box.Second, it’s self-service. There’s no permission to ask to use it. Everyone can use it.Third, it’s resilient. It works all the time, especially when you’re in the middle of a crisis.Fourth, it’s automated, completely API-driven, deployment is automated.Fifth, it’s correlative, it lets you graph and correlate any metric from anywhere.Sixth it shows good craftsmanship, it’s a pleasure to use.

We’ve built such a system.

Page 14: Monitoring that does not suck

no assembly req’d

self-service

resilient

automated

correlativecraftsmanship

First, no assembly required. It works out of the box.Second, it’s self-service. There’s no permission to ask to use it. Everyone can use it.Third, it’s resilient. It works all the time, especially when you’re in the middle of a crisis.Fourth, it’s automated, completely API-driven, deployment is automated.Fifth, it’s correlative, it lets you graph and correlate any metric from anywhere.Sixth it shows good craftsmanship, it’s a pleasure to use.

We’ve built such a system.

Page 15: Monitoring that does not suck

http://dtdg.co/rome-2012

It’s called Datadog.

If you want to know more, come and chat with us at the break.Or visit us on the web.

Thank you.