Splunk Completes Acquisition of Plumbr Learn more

To blog |

Early Awareness With Plumbr Alerting

May 29, 2019 by Ivo Mägi Filed under: Blog Plumbr Product Updates

We have listened and learned from our customers about the different needs for early awareness on availability and performance issues. As a result, we are reintroducing alerts you can configure and trigger directly from within the Plumbr UI.

These alerts are designed to fit two different workflows

  • Have you adopted devops and have on-call teams responding to production incidents? Plumbr proactive alerts based on user impact can really improve the response time for the incidents. Plumbr integrates with Slack, PagerDuty and email alerting channels where you can configure alerts to be sent whenever the user experience degrades below tolerable thresholds.
  • Running traditional development teams? See how Plumbr integration with JIRA can keep help you to prioritize the potential fixes based on their impact during your sprint/iteration planning. The information exposed makes it easy to prioritize the few burning issues that need immediate attention.
On-call devops teams:

For devops teams responding to production incidents the main value in Plumbr alerting comes from the signal quality. Plumbr triggers alerts based on the impact (and not by the cause), thus making sure your on-call team will never sleep through issues impacting real users nor faces alert fatigue from never-ending false positives.

Here are some examples of alerts you can set up to trigger based on either real user experience or the API performance:

  • Send a page to PagerDuty  if nobody has used my application for more than 30 minutes.
  • Send a page to PagerDuty if more than 5% of the last 1,000 user interactions have been resulting in a failure.
  • Send a message to Slack room #devops-oncall if the 99.9 percentile of performance has exceeded 1,200ms on the API payment-gateway.

What we are extremely proud is that we can help you to avoid you going through lengthy trial-and error attempts when trying to get the thresholds right in the examples above. Our alert configuration includes possibility to play back the history, highlightin you the moments when a particular trigger was fired. This allows you to compare the outcome with your incidents from last month or two and see whether the calibration is matching your needs.

Interested in getting early access and steer the user experience we will offer around the feature? Contact our product team to get access to the alerts already in the beginning of June!

External development teams:

For set-ups where the engineering team is outsourced and is not involved to on-call processes, we can recommend a different approach. The problem we help to solve here is the prioritization exercise. Whenever you need to prioritize the scope for the new release, there is always the fine balancing between new features and bug fixes to existing ones.

With Plumbr pushing each new bug to JIRA and equipping it with the impact to real users you are no longer left to guesswork and rumors when trying to prioritize the potential fixes. After all, there is only so much resources available and you can never fix all the bugs. It boils down to making sure you fix the bugs with biggest impact first. This is now trivial, having all the new errors impacting real users automatically appearing in your JIRA backlog.

Interested in getting early access as early as the 1st of June? Let’s discuss and make sure that the final UI polishing touches take into account your requirements!