---
title: "Sentry: broken transactions section"
url: https://michalasobczak.pl/posts/sentry-broken-transactions-section.html
author: "Michał Sobczak"
description: "Managing self-hosted Sentry is pretty straightforward. However due to high number of containers which Sentry is comprised of, there is high chance that we can encounter some kind of issues due to obvious nature of software development products which consists by definition some flaws."
published: 2025-01-23T09:50:04.000Z
updated: 2025-01-23T09:50:04.000Z
language: en
categories: ["Technology"]
tags: ["Kafka", "Sentry"]
license: CC BY-NC-ND 4.0 (https://creativecommons.org/licenses/by-nc-nd/4.0/)
---
# Sentry: broken transactions section

Managing self-hosted Sentry is pretty straightforward. However due to high number of containers which Sentry is comprised of, there is high chance that we can encounter some kind of issues due to obvious nature of software development products which consists by definition some flaws.

So this time Sentry is getting traffic from embedded agents but payload is not complete. It lacks processing of transactions. So first we need to dive into Kafka groups. With the following, we can inspect the state of topics:

```bash
docker compose run --rm kafka kafka-consumer-groups --bootstrap-server kafka:9092 --all-groups --describe
```

We can learn that something is out of date or nothing processes some topics. So using `docker compose exec kafka bash` we can start shell in kafka container and then delete failed topics:

```text
kafka-topics --bootstrap-server kafka:9092 --delete --topic ingest-transactions
kafka-topics --bootstrap-server kafka:9092 --delete --topic ingest-performance-metrics
kafka-topics --bootstrap-server kafka:9092 --delete --topic ingest-metrics
```

There might be lag, wrong offset or any other kind of issue with consumer of beforementioned topics. Sentry software will recreate those topics and your performance metric will again start to show up in Sentry UI.