Sentry on Daffa Abhipraya

PPL: Self-Hosted Error Monitoring with Custom Instrumentation

Sat, 11 Apr 2026 00:00:00 +0700

Error monitoring is one of those things that feels optional until the first production bug slips through unnoticed. A user reports “the page is broken,” you check the server, everything looks fine, and three hours later you discover a background task has been silently failing since the last deploy. This blog covers how we built monitoring that catches those failures before users do.

Note: Our project is hosted on an internal GitLab instance, so we use the term MR (Merge Request) throughout this blog. If you’re coming from GitHub, MRs are the equivalent of Pull Requests (PRs).

PPL: New Learnings Applied to SIRA [Sprint 2, Week 2]

Thu, 09 Apr 2026 00:00:00 +0700

Overview

Sprint 2 Week 2 (April 3 to 9) was dominated by a mutation testing sprint: setting up mutmut and Stryker in CI, building integration test infrastructure from scratch, and writing mutation-killing tests. The week also delivered three application features and a meta-level improvement to AI workflow. Each area required learning at least one technology or concept not covered in standard Fasilkom coursework.

1. Mutation Testing with mutmut (Python)

Mutation testing is a technique where a tool injects small faults (“mutants”) into your source code (flipping operators, changing constants, removing lines) and checks whether your test suite catches each fault. If a test fails, the mutant is “killed.” If no test fails, the mutant “survives,” meaning your tests have a blind spot.

PPL: Service Layer Instrumentation [Sprint 2, Week 1]

Mon, 23 Mar 2026 00:00:00 +0700

What I Worked On

This week I implemented custom Sentry span instrumentation across 3 key API services to track sub-operation latency in GlitchTip. The interesting part wasn’t the Sentry API itself; it was where to place the instrumentation in our layered architecture, and how the existing SOLID patterns made the change trivially simple.

Following the Architecture: Spans in Services, Not Routers

SIRA follows a strict Router → Service → DB pattern. Routers handle HTTP concerns (auth, status codes). Services hold business logic. DB queries are isolated in db/queries/.

Sentry on Daffa Abhipraya

PPL: Self-Hosted Error Monitoring with Custom Instrumentation

PPL: New Learnings Applied to SIRA [Sprint 2, Week 2]

# Overview

# 1. Mutation Testing with mutmut (Python)

PPL: Service Layer Instrumentation [Sprint 2, Week 1]

# What I Worked On

# Following the Architecture: Spans in Services, Not Routers

Overview

1. Mutation Testing with mutmut (Python)

What I Worked On

Following the Architecture: Spans in Services, Not Routers