Skip to main content
A.I. Commerce Studio

Workshop

Observability and SRE Workshop

A workshop with your team on what you observe, how you learn about a problem and how you respond: signals, SLOs, alerts, incidents.

WorkshopScoped individually

Price, length and scope are agreed in writing. We do not guarantee specific outcomes: the findings depend on the information available and on your team's participation.

Send an enquiry

Who it is for

  • Operations and development teams of business-critical systems.
  • Companies that hear about problems from their customers.
  • Teams introducing AI systems that must be observed.

Problems it addresses

  • Many alerts, but few of them lead to action.
  • No shared definition of what "the system works" means.
  • Logs, metrics and traces are scattered.
  • Incidents get fixed, but the lessons are not recorded.

What is needed beforehand

  • A list of the main systems and the monitoring tools used.
  • An example of a recent incident and how it was found and resolved.
  • Recommended: completed free observability or AI operations assessments.

Format

Participants
Operations, development and the owner of at least one key service.
Delivery
Remote or on site; the materials and notes stay with you.
Length
Indicatively half a day to two days with your team. The exact length is agreed in writing when the scope is set.

Agenda

  1. 01 · Critical journeys

    Which user journeys and services matter most, and why.

  2. 02 · Signals and SLOs

    Indicators and service-level objectives for those journeys.

  3. 03 · Alerts and response

    When whom is alerted and what they do; incident roles.

  4. 04 · Roll-out plan

    Steps towards OpenTelemetry, dashboards and post-incident reviews.

What you receive

  • A written summary of the decisions made.
  • Draft SLIs and SLOs for the selected services.
  • Alerting rules and a post-incident review template.
  • A step-by-step plan for introducing observability.

What is not included

  • It includes no tool set-up or telemetry collection.
  • It implies no round-the-clock support; that is agreed separately.
  • The SLO targets are a draft to be confirmed with real data.

Would this format suit your team?

Send an enquiry. We will clarify the goal, the participants and the material needed, and propose a written scope.