---
title: "Sentry | Skills We Assign For | Azendo"
description: "Sentry for error tracking — grouping, release tracking, noise, plus the Azendo roles assigned for it."
url: "https://azendo.co/skills/sentry/"
---

[Skills](https://azendo.co/skills/) Observability 

# Sentry.

Sentry is an error tracking platform capturing exceptions with stack traces, request context and user information, grouping similar errors and tracking whether each is new, regressed or resolved.

## Where Sentry fits on a long engagement.

Grouping is what makes error tracking usable. Thousands of occurrences of the same exception collapse into one issue with a count, which turns an unreadable log stream into a prioritised list of distinct problems.

Release tracking closes the loop that matters most. Knowing that an error first appeared in a specific deployment identifies the cause immediately, and regression detection — an error marked resolved reappearing — catches the fix that did not hold.

## What an assigned team does with Sentry.

Unmanaged Sentry becomes noise. Errors nobody triages accumulate, known issues are not muted, and the tool becomes a dashboard people stopped opening — at which point a real new error is invisible among the accumulated ones.

Triage as a routine rather than an occasional clean-up is what keeps it useful, and it is part of the standards held under [devops managed services](https://azendo.co/services/cloud-and-devops/).

## What we use Sentry for.

* Distinct problems rather than log volume Grouping that turns thousands of lines into a prioritised list.
* Errors attributed to a release First occurrence tied to a deployment, which identifies the cause immediately.
* Triage as routine Issues resolved or muted, so a new error is visible rather than buried.

## How Sentry capacity is assigned.

Error tracking is assigned alongside the application capacity it observes, with triage treated as routine work rather than periodic clean-up.

## Service lines it sits in

* [AI automation engineering](https://azendo.co/services/ai-automation-engineering/)

Capacity is agreed as a committed monthly capacity across a discipline, not per skill.

## Related in observability

* [SLO and error budget design — skill we assign for](https://azendo.co/skills/slo-and-error-budget-design/)
* [Prometheus — skill we assign for](https://azendo.co/skills/prometheus/)
* [OpenTelemetry — skill we assign for](https://azendo.co/skills/opentelemetry/)
* [CloudWatch — skill we assign for](https://azendo.co/skills/cloudwatch/)
* [PagerDuty — skill we assign for](https://azendo.co/skills/pagerduty/)
* [Observability — skill we assign for](https://azendo.co/skills/observability/)
* [Logging — skill we assign for](https://azendo.co/skills/logging/)
* [audit logging — skill we assign for](https://azendo.co/skills/audit-logging/)

## Tell us what your roadmap needs Sentry for.

A service delivery manager replies with the disciplines we would assign, the monthly capacity and what the first month looks like.

[All skills we assign for](https://azendo.co/skills/)