---
title: "Discussion on \"Struggles of Monitoring with Ingress on AKs\" | Hashnode"
description: "Discussion on \"Struggles of Monitoring with Ingress on AKs\". When I started working on the monitoring setup for my project, CodeForge — a coding platform — I thought it would be a fairly straightforward task. I decided to use the Prometheus-Grafana stack for mo"
url: "https://hashnode.com/posts/struggles-of-monitoring-with-ingress-on-aks/6a08741610b27f042502d87e"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [Struggles of Monitoring with Ingress on AKs](https://devops-track.hashnode.dev/struggles-of-monitoring-with-ingress-on-aks?utm_source=hashnode&utm_medium=feed)

When I started working on the monitoring setup for my project, CodeForge — a coding platform — I thought it would be a fairly straightforward task. I decided to use the Prometheus-Grafana stack for mo

May 16 · 4 min read · devops-track.hashnode.dev  
Read the article

-   [#devops](https://hashnode.com/tag/devops)
-   [#devsecops](https://hashnode.com/tag/devsecops)
-   [#debugging](https://hashnode.com/tag/debugging)
-   [#cloud-computing](https://hashnode.com/tag/cloud-computing)
-   [#observability](https://hashnode.com/tag/observability)
-   [#azure](https://hashnode.com/tag/azure)
-   [#ingress](https://hashnode.com/tag/ingress)

## Written by

[Subrat Yadav](https://hashnode.com/@Subrat-Devops)

@Subrat-Devops

  
[View profile](https://hashnode.com/@Subrat-Devops)

## Responses

Markdown supported · ⌘↵ to post

No responses yet.
