webops dashboards

49
/ Dashboards for web operations Friday, June 17, 2011

Upload: theo-schlossnagle

Post on 15-Jan-2015

4.046 views

Category:

Technology


0 download

DESCRIPTION

What you should think about putting in webops dashboards. There's a lot of discussion that isn't annotated in the slide stack -- so you're missing a lot without audio.

TRANSCRIPT

Page 1: Webops dashboards

/

Dashboards

for web operations

Friday, June 17, 2011

Page 2: Webops dashboards

Author of “Scalable Internet Architectures”Pearson, ISBN: 067232699X

Contributor to “Web Operations”O’Reilly, ISBN: 978-1-4493-7744-1

Founder of OmniTI, Message Systems, Fontdeck, & CirconusI like to tackle problems that are “always on” and “always growing.”

I am an EngineerA practitioner of academic computing.IEEE member and Senior ACM member.On the Editorial Board of ACM’s Queue magazine.

Who is this guy?

Friday, June 17, 2011

Page 3: Webops dashboards

What’s in a dashboard

• instrumentation

• actionable information

• relevant to both your purview and your purpose

Friday, June 17, 2011

Page 4: Webops dashboards

What’s not in a dashboard

• controls

• via a dashboard you observe, not influence

• I’ll arbitrarily redefine:“dashboard” as not having controls, and“console” as having them

Friday, June 17, 2011

Page 5: Webops dashboards

Your purpose

• Your purpose is to makeyour company’s web businessoperate.

(hence: “web operations”)

Friday, June 17, 2011

Page 6: Webops dashboards

Your purpose

• Your purpose is to makeyour company’s web businessoperate.

(hence: “web operations”)

Friday, June 17, 2011

Page 7: Webops dashboards

Your purpose

• ensure business success

Friday, June 17, 2011

Page 8: Webops dashboards

Understanding your purpose

• who defines business success?

• shareholders, ultimately

• the board of directors, in their stead

• the CEO on an operational, day-to-day basis

Friday, June 17, 2011

Page 9: Webops dashboards

Understanding your purpose

• Assuming your CEO is doing a good job

• the executive team understands these metrics

• Assuming the executive team is competent

• their reports understand these metrics(at least the pertinent ones)

Friday, June 17, 2011

Page 10: Webops dashboards

Pertinent == Problematic

• You enable all aspects of the business

• All these metrics are pertinent

Friday, June 17, 2011

Page 11: Webops dashboards

But why?

• You could simply track stuff that is in your purview.

• Why not?

Friday, June 17, 2011

Page 12: Webops dashboards

Technology

• As a technology operations group,you have the technology.

We can rebuild him.We have the technology.We can make him better than he was.Better...stronger...faster.

- Oscar Goldman

Friday, June 17, 2011

Page 13: Webops dashboards

Why is our technology better?

• Simply put: MTTD

Friday, June 17, 2011

Page 14: Webops dashboards

Now, what about your purview?

• Obviously monitoring the business is useful.

• However, you cannot directly affect business.

• You indirectly affect it by operating the web portion.

Friday, June 17, 2011

Page 15: Webops dashboards

What can you change?

• You can control:

• releases,

• performance,

• stability,

• computing resources,

• networking,

• and availability.

Friday, June 17, 2011

Page 16: Webops dashboards

Visualize!

• All this information must be presented visually.

Friday, June 17, 2011

Page 17: Webops dashboards

Text.

• Text is incredibly useful.

• Consider: deployment.

Friday, June 17, 2011

Page 18: Webops dashboards

Code Deployment

r82394 (by corey) 1h 7m 9s ago previous deploy 1h 42m 18s ago

11 deploys today

Friday, June 17, 2011

Page 19: Webops dashboards

Code Deployment

r82394 15:03:14 2011/06/15 previous deploy 1h 42m 18s ago

11 deploys today

Friday, June 17, 2011

Page 20: Webops dashboards

Code Deployment

r82394 (by corey) 1h 7m 9s ago previous deploy 1h 42m 18s ago

11 deploys today

Friday, June 17, 2011

Page 21: Webops dashboards

Code Deployment

r82394 (by corey) 1h 7m 9s ago previous deploy 1h 42m 18s ago

11 deploys today

Friday, June 17, 2011

Page 22: Webops dashboards

Code Deployment

r82394 (by corey) 1h 7m 9s ago previous deploy 1h 42m 18s ago

11 deploys today

Friday, June 17, 2011

Page 23: Webops dashboards

Code Deployment

r82394 (by corey) 1h 7m 9s ago previous deploy 1h 42m 18s ago

11 deploys today

Friday, June 17, 2011

Page 24: Webops dashboards

Text.

• Numbers are trickier.

• So many representations from which to choose.

Friday, June 17, 2011

Page 25: Webops dashboards

Beware

Friday, June 17, 2011

Page 26: Webops dashboards

Beware

Friday, June 17, 2011

Page 27: Webops dashboards

Beware

Friday, June 17, 2011

Page 28: Webops dashboards

Beware

Friday, June 17, 2011

Page 29: Webops dashboards

Gauges require understanding

• Gauges imply a deep understanding of

• bounds, and

• tolerances

Friday, June 17, 2011

Page 30: Webops dashboards

Gauges require understanding

• General advice

• If the range will ever change, don’t use gauges

Friday, June 17, 2011

Page 31: Webops dashboards

Gauges require understanding

• Great for:

• percentages,

• temperature,

• power per rack,

• bandwidth per uplink

Friday, June 17, 2011

Page 32: Webops dashboards

Gauges require understanding

• Bad for:

• IOPS,

• current visitor counts,

• requests per second,

• bandwidth overall

Friday, June 17, 2011

Page 33: Webops dashboards

Graphs are often better

Friday, June 17, 2011

Page 34: Webops dashboards

Even little ones

Friday, June 17, 2011

Page 35: Webops dashboards

Think relatively

Friday, June 17, 2011

Page 36: Webops dashboards

Think relatively

xxxxxxxxxxxxxxx

xxxxxxxxxxxxxxx

Friday, June 17, 2011

Page 37: Webops dashboards

Users live all around the world

• Users live just about everywhere

• “Where?” is a useful question

Friday, June 17, 2011

Page 38: Webops dashboards

Geolocation

Friday, June 17, 2011

Page 39: Webops dashboards

Geolocation is interesting

• to marketing

• to legal

• (okay to everyone)

• but, not so useful to operations

Friday, June 17, 2011

Page 40: Webops dashboards

Geolocation is interesting

• perhaps more interesting

Friday, June 17, 2011

Page 41: Webops dashboards

Geolocation is interesting

Friday, June 17, 2011

Page 42: Webops dashboards

Geolocation

• Internet location != geo-political location

Friday, June 17, 2011

Page 43: Webops dashboards

ASN location

• The closest thing to geo-political boundaries is peering

-bash-4.0$ /usr/sbin/bgpctl show rib 66.78.236.243flags: * = Valid, > = Selected, I = via IBGP, A = Announcedorigin: i = IGP, e = EGP, ? = Incomplete

flags destination gateway lpref med aspath origin 66.78.236.0/22 64.202.119.7 100 0 23352 4436 2914 3356 32778 i

### ASN 327778 is “Smart City Networks, L.P.”

Friday, June 17, 2011

Page 44: Webops dashboards

ASN location

Friday, June 17, 2011

Page 45: Webops dashboards

What about the business?

Friday, June 17, 2011

Page 46: Webops dashboards

What about the business?

Authorizations : Hard Failed : Soft Failed : Releases

Friday, June 17, 2011

Page 47: Webops dashboards

Is that all?

• Hells no.

Friday, June 17, 2011

Page 48: Webops dashboards

It’s all about real-time

• Everything so far is old hat (maybe)

• Every business unit has visualizations like this

• You need to combine the data

• You need to make it real-time

Friday, June 17, 2011

Page 49: Webops dashboards

Thanks

• web demo ensues....

Friday, June 17, 2011