Monitoring Critical Drupal Commerce Operations

What’s worse than a fire? When you don’t know there’s a fire! While there is no “one size fits all” approach to monitoring Drupal Commerce for failures and issues there is one pattern that can be applied to many sites: logging to an aggregation service.

In this session, we’ll discuss some examples of critical operations to monitor and how their failure might bypass typical website uptime monitoring. We’ll look at how to integrate with a log aggregation service, including well-used code samples. Finally, we’ll look at some considerations for setting up policy alerts in a log aggregation service.

This session is for you if you are building a Drupal Commerce website that has external system dependencies, or if you want to see this pattern to apply it elsewhere. Coming away from this session you should be able to articulate why a log aggregation service is a critical component to Drupal Commerce availability, and how to implement it.