---
title: "Ashitha Ravindran (@ashitharavindran) | Hashnode"
description: "Ashitha Ravindran (@ashitharavindran) writes on Hashnode. Read their latest articles and follow their work."
url: "https://hashnode.com/@ashitharavindran"
---

@ashitharavindran

# Ashitha Ravindran

@ashitharavindran · bangalore · Joined June 2026

### [20 Kubernetes Failures You Should Be Alerting On](https://epok.hashnode.dev/20-kubernetes-failures-you-should-be-alerting-on?utm_source=hashnode&utm_medium=feed)

CrashLoopBackOff is the one everyone watches. Here are 20 Kubernetes failures — in logs and events — that actually deserve an alert. It's 3am and the dashboard is green. Checkout is timing out anyway,

10 min read · [epok.hashnode.dev](https://epok.hashnode.dev/20-kubernetes-failures-you-should-be-alerting-on?utm_source=hashnode&utm_medium=feed)

[Jul 7](https://hashnode.com/posts/20-kubernetes-failures-you-should-be-alerting-on/6a4d1c65ffac0be90922840d)

### [Silent Failures: The Bug That Won't Page You](https://epok.hashnode.dev/silent-failures-the-bug-that-won-t-page-you?utm_source=hashnode&utm_medium=feed)

A silent failure is when a service stops logging and no alert fires. Here's how absence detection catches the bug that never throws an error. The webhook consumer died at 2:41am. OOM kill — the kernel

8 min read · [epok.hashnode.dev](https://epok.hashnode.dev/silent-failures-the-bug-that-won-t-page-you?utm_source=hashnode&utm_medium=feed)

[Jul 7](https://hashnode.com/posts/silent-failures-the-bug-that-won-t-page-you/6a4d16bfda4640d29ba4e122)

### [Catch New Errors in Production Before Your Users Do](https://epok.hashnode.dev/catch-new-errors-in-production-before-your-users-do?utm_source=hashnode&utm_medium=feed)

Catch New Errors in Production Before Your Users DoThe errors that take you down are the ones you've never seen before. Here's how automatic fingerprinting catches new errors in production on the firs

8 min read · [epok.hashnode.dev](https://epok.hashnode.dev/catch-new-errors-in-production-before-your-users-do?utm_source=hashnode&utm_medium=feed)

[Jul 7](https://hashnode.com/posts/catch-new-errors-in-production-before-your-users-do/6a4d12591dfc7374ab7147fb)

### [Datadog Alternatives for Small Teams (2026)](https://epok.hashnode.dev/datadog-alternatives-for-small-teams-2026?utm_source=hashnode&utm_medium=feed)

Datadog Alternatives for Small Teams (2026) Datadog alternatives for small teams in 2026: an honest look at Grafana, Axiom, Better Stack, and Epok — by billing model, not just per-GB rate. DATADOG COM

8 min read · [epok.hashnode.dev](https://epok.hashnode.dev/datadog-alternatives-for-small-teams-2026?utm_source=hashnode&utm_medium=feed)

[Jul 7](https://hashnode.com/posts/datadog-alternatives-for-small-teams-2026/6a4cd89cbca5156a822b5184)

### [Root Cause Analysis in Distributed Systems: Why Looking at One Signal Isn't Enough](https://epok.hashnode.dev/root-cause-analysis-in-distributed-systems-why-looking-at-one-signal-isn-t-enough?utm_source=hashnode&utm_medium=feed)

How combining logs, metrics, and traces helps identify production issues faster.

4 min read · [epok.hashnode.dev](https://epok.hashnode.dev/root-cause-analysis-in-distributed-systems-why-looking-at-one-signal-isn-t-enough?utm_source=hashnode&utm_medium=feed)

[Jun 29](https://hashnode.com/posts/root-cause-analysis-in-distributed-systems-why-looking-at-one-signal-isn-t-enough/6a4218799004a524371125bf)
