# Kubernetes App - Feedback / Excluding Kubernetes events

**URL:** <https://community.dynatrace.com/t/kubernetes-app-feedback-excluding-kubernetes-events/46435>\
**Category:** Container platforms\
**Tags:** feedback, kubernetes\
**Created:** [July 3, 2024, 1:58am UTC](https://community.dynatrace.com/t/kubernetes-app-feedback-excluding-kubernetes-events/46435 "2024-07-03T01:58:16Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![sivart\_89](https://avatars.discourse-cdn.com/v4/letter/s/848f3c/32.png) [@sivart\_89](https://community.dynatrace.com/u/sivart_89)\
**Post date:** [July 3, 2024, 1:58am UTC](https://community.dynatrace.com/t/kubernetes-app-feedback-excluding-kubernetes-events/46435/1 "2024-07-03T01:58:16Z")

</div>

I tried to post this in the feedback channel that is linked in the Kubernetes app, link below but I get an **'You do not have sufficient privileges for this resource or its parent to perform this action.** ’ error, not sure if that is expected.

[https://community.dynatrace.com/t5/forums/filteredbylabelpage/board-id/Feedback\_channel/label-name/kubernetes](https://community.dynatrace.com/tag/kubernetes)

We are trying out the Kubernetes app some and have added 2 clusters. We are using kyverno running in a audit mode so there are a lot of **PolicyViolation** events, at least until we get them cleaned up. I had excluded these events from being pulled in for the clusters when they were setup the traditional way (before adding them to the Kubernetes app). The events did get excluded then but now they are back for the clusters that have been added to the Kubernetes app.

I see the below within the cluster settings in the old interface. Does this mean we are forced to always pull in ALL k8 events? Can we no longer exclude the unimportant ones? Am I missing something with the new app?

Monitoring settings are handled differently since the new Kubernetes experience was activated. The Kubernetes app requires that the following monitoring settings are always enabled:

- Monitor Kubernetes namespaces, services, workloads, and pods
- Monitor workload and node resource metrics
- Monitor important events

To maintain consistency between classic and new Kubernetes experience, these settings can’t be changed any longer on this page or&nbsp;[via API](https://docs.dynatrace.com/docs/dynatrace-api/environment-api/settings). They are&nbsp; **automatically overruled** &nbsp;and always&nbsp; **treated as enabled**.

_Note: The values of the settings are preserved. This is why they may still be displayed as disabled._

---

<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:** [July 31, 2024, 10:53am UTC](https://community.dynatrace.com/t/kubernetes-app-feedback-excluding-kubernetes-events/46435/2 "2024-07-31T10:53:23Z")

</div>

Hello&nbsp;[@sivart\_89](https://community.dynatrace.com/user/17361),

I’ve crosslinked your comment to the thread about the newest Kubernetes app here:  
[Getting started with the new Kubernetes experience](https://community.dynatrace.com/post/252073)

---

<div class="post-metadata">

**Author:** ![sivart\_89](https://avatars.discourse-cdn.com/v4/letter/s/848f3c/32.png) [@sivart\_89](https://community.dynatrace.com/u/sivart_89)\
**Post date:** [July 31, 2024, 11:07am UTC](https://community.dynatrace.com/t/kubernetes-app-feedback-excluding-kubernetes-events/46435/3 "2024-07-31T11:07:27Z")

</div>

Thank you&nbsp;[@MaciejNeumann](https://community.dynatrace.com/user/6). We’re hoping to understand that piece a bit more before we get more serious about onboarding other k8 clusters.