# Alert Setup for DaemonSet Pod

**URL:** <https://community.dynatrace.com/t/alert-setup-for-daemonset-pod/49494>\
**Category:** Alerting\
**Tags:** problems, kubernetes\
**Created:** [December 26, 2024, 8:55am UTC](https://community.dynatrace.com/t/alert-setup-for-daemonset-pod/49494 "2024-12-26T08:55:08Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Gyanendra](https://avatars.discourse-cdn.com/v4/letter/g/7c8e57/32.png) [@Gyanendra](https://community.dynatrace.com/u/Gyanendra)\
**Post date:** [December 26, 2024, 8:55am UTC](https://community.dynatrace.com/t/alert-setup-for-daemonset-pod/49494/1 "2024-12-26T08:55:08Z")

</div>

I need to create an alert in Dynatrace for a DaemonSet to trigger a problem if any pod is not running or goes down, regardless of the node count. For example:

- Cluster 1 has 10 nodes
- Cluster 2 has 5 nodes
- Cluster 3 has 8 nodes

Each cluster has a Fluentd DaemonSet running on all nodes. The alert should dynamically monitor all clusters and generate a problem if any DaemonSet pod fails, without relying on a fixed threshold, as node counts vary across clusters.

---

<div class="post-metadata">

**Author:** ![MaciejNeumann](https://avatars.discourse-cdn.com/v4/letter/m/5e9695/32.png) [@MaciejNeumann](https://community.dynatrace.com/u/MaciejNeumann)\
**Post date:** [November 24, 2025, 1:45pm UTC](https://community.dynatrace.com/t/alert-setup-for-daemonset-pod/49494/2 "2025-11-24T13:45:14Z")

</div>

Hello&nbsp;[@Gyanendra](https://community.dynatrace.com/user/82918),

Here is a Documentation article about Node alerts:

[Alert on common Kubernetes/Openshift issues - Node alerts](https://docs.dynatrace.com/docs/shortlink/alerts-k8s#node)&nbsp;  
Available alerts are including detecting node readiness issues and detecting problematic node conditions. Would those solve your use case?

Right below the table in the article you can check Node metrics and DQL queries, that are used for creating those alerts.
