9
“DevOps, How Do You Debug?” Results From Logentries Poll Conducted In November 2014

“DevOps, How Do You Debug?” Results From Logentries Poll

Embed Size (px)

Citation preview

“DevOps, How Do You Debug?” Results From Logentries Poll

Conducted In November 2014

Time Spent Debugging Weekly

13%

61%

17% 9%

Less than one hour

Between 1 and 5 hours

Between 5 and 10 hours

More than 10 hours

0% 10% 20% 30% 40% 50% 60% 70%

87% of DevOps professionals spend more than 1 hour a week debugging their apps.

Logs and Debugging

Yay for logs! Most (83%) DevOps professionals use logs for debugging. Do you?

System anomaly tracking across your environments

0%

5%

10%

15%

20%

25%

30%

35%

Word of mouth – Ops team, other team members

APM monitoring tool (i.e. NewRelic)

Log management tool (i.e.

Logentries)

We do not actively track anomalies

Other Option Native platform alerting feature

Yup, DevOps professionals still rely on tips from humans, then come alerts from APM and log management tools. To more intelligent anomaly tracking in 2015!

Ways DevOps professionals get notified if problem with code / application

21%

Word of mouth – Ops team, other team members, users

Word of mouth is the #1 way teams are alerted of problems

Did you know?: With real-time log management tools like Logentries, you and your team can get alerted of events, system anomalies or exceptions, right as they happen.

There’s a bug.

Top DevOps challenges with debugging systems/applications

#1 DevOps Debugging Challenge:

Here’s what DevOps professionals shared:

•  “Collating, parsing and searching logs”

•  “Errors usually come in batches of 100s or 1,000s. Hitting rate limits mean we may miss legitimate errors.”

•  “Noisy alerting: have to figure out whether this is a real problem or not”

•  “Service Oriented Architecture can be misleading with error messages. The application may throw an exception that is caused by something downstream”

•  “Missing insights into the app internals”

Too Much Noise, Very Little Signal!

Top DevOps challenges with debugging systems/applications (cont.)

#2 DevOps Debugging Challenge:

Here’s what DevOps professionals shared:

•  “Complex architectures have complex problems and interactions making it difficult to follow a transaction across the system”

•  “Debugging complex ajax requests”

•  “Pinpointing the issue”

•  “Reproducing the problems from end users”

Complexity

Top DevOps challenges with debugging systems/applications (cont.)

#3 DevOps Debugging Challenge:

Here’s what DevOps professionals shared:

•  “Development that actually fix bugs instead of adding features”

•  “Getting developers to write good log statements” •  “People not using SVN, developing on production systems, lack of communication”

•  “In a world now driven by instances that can be quickly rebuilt, how do you tell the difference between two given instances? It takes too long to figure out so we often just destroy and rebuild”

Good code done right

To Bug-free 2015!