addressalign-toparrow-leftarrow-rightbackbellblockcalendarcameraccwcheckchevron-downchevron-leftchevron-rightchevron-small-downchevron-small-leftchevron-small-rightchevron-small-upchevron-upcircle-with-checkcircle-with-crosscircle-with-pluscontroller-playcrossdots-three-verticaleditemptyheartexporteye-with-lineeyefacebookfolderfullheartglobegmailgooglegroupshelp-with-circleimageimagesinstagramFill 1light-bulblinklocation-pinm-swarmSearchmailmessagesminusmoremuplabelShape 3 + Rectangle 1ShapeoutlookpersonJoin Group on CardStartprice-ribbonprintShapeShapeShapeShapeImported LayersImported LayersImported Layersshieldstartickettrashtriangle-downtriangle-uptwitteruserwarningyahoo

Re: [TriangleDevOps] What is DevOps?

From: Michael H.
Sent on: Wednesday, August 15, 2012 9:43 AM
Where I work (heroku.com) we use a bit of a home grown approach to metrics/monitoring/visibility using tools like graphite and some that we have open-sourced: http://vimeo.com/43699577. One of the things I think is really cool is how we are able to alert on data that we trend to graphite. For example if service A has more than 100 connections over say 5 minutes we could trigger a nagios alert.

On Mon, Aug 13, 2012 at 8:20 PM, Neal Anders <[address removed]> wrote:
All of the success stories I have heard around monitoring / performance usually revolve around something home-grown - usually wrapping existing tools out there...  New Relic comes to mind, as does StatsD and Graphite..  anyone else have others? - Neal


From: Magnus <[address removed]>
To: [address removed]
Sent: Monday, August 13,[masked]:51 PM

Subject: Re: [TriangleDevOps] What is DevOps?

On Mon, 13 Aug[masked]:41:27 -0400, Neal Anders <[address removed]>
wrote:
> The larger
> challenge in that case is convincing folks that such things provide value
> to your customers, even if they don't use it directly as part of the
> service you provide.

In an agile environment, anyway, this challenge is easier to overcome than
one might think because the product owners are directly connected to the
scrum teams, and also (in theory) getting a feedback loop from the
customer. The monitoring stories almost write themselves. But yes, there
can be some challenge in illustrating the importance & priority of a
monitoring/metrics story over a feature story.

On that subject, monitoring sucks. Too many of us drag Nagios across the
years like the ghost of Jacob Marley dragged his chains across the
afterlife. There are better tools out there, I hear. Zenoss was supposedly
one of them, but it seems only an incremental improvement over Nagios. Is
there anything in this new world order, where cloud-based autoscaling
infrastructure is the norm, that makes sense of monitoring?



--
Please Note: If you hit "REPLY", your message will be sent to everyone on this mailing list ([address removed])
http://www.meetup.com/Triangle-DevOps/
This message was sent by Magnus ([address removed]) from Triangle DevOps.
To learn more about Magnus, visit his/her member profile: http://www.meetup.com/Triangle-DevOps/members/9841577/
Set my mailing list to email me

As they are sent
http://www.meetup.com/Triangle-DevOps/list_prefs/?pref=1

In one daily email
http://www.meetup.com/Triangle-DevOps/list_prefs/?pref=2

Don't send me mailing list messages
http://www.meetup.com/Triangle-DevOps/list_prefs/?pref=0
Meetup, PO Box 4668 #37895 New York, New York[masked] | [address removed]







--
Please Note: If you hit "REPLY", your message will be sent to everyone on this mailing list ([address removed])
This message was sent by Neal Anders ([address removed]) from Triangle DevOps.
To learn more about Neal Anders, visit his/her member profile
Set my mailing list to email me As they are sent | In one daily email | Don't send me mailing list messages

Meetup, PO Box 4668 #37895 New York, New York[masked] | [address removed]

Our Sponsors

Sign up

Meetup members, Log in

By clicking "Sign up" or "Sign up using Facebook", you confirm that you accept our Terms of Service & Privacy Policy