# How are you handling alert customization and noise reduction in Kubesense?

Kubesense has been great for native Kubernetes onboarding, quick setup, and a clean default dashboard that surfaces essential metrics without building everything from scratch. Having metrics, traces, infrastructure monitoring, and logs in one unified observability platform has reduced context-switching and helped lower MTTR with end-to-end visibility. The main gap for us is alerting: customization feels limited, and filtering or segregation could be more granular to manage noise, plus deeper AI-driven root-cause analysis would help during incidents. How are others configuring alerts in Kubesense today, and what would you like to see improved?

##### Post Metadata
- Posted at: 19 days ago
- Author title: Vice President – Engineering, DevOps and SRE
- Net upvotes: 1



## Related Product
[Kubesense](https://www.g2.com/products/kubesense/reviews)

## Related Category
[Observability Software](https://www.g2.com/categories/observability-software)

## Related discussions
- [How well does Trello scale into a larger team?](https://www.g2.com/discussions/1-how-well-does-trello-scale-into-a-larger-team)
  - Posted at: over 13 years ago
  - Comments: 6
- [Can we please add a new section](https://www.g2.com/discussions/2-can-we-please-add-a-new-section)
  - Posted at: over 13 years ago
  - Comments: 0
- [Quantifiable benefits from implementing your CRM](https://www.g2.com/discussions/quantifiable-benefits-from-implementing-your-crm)
  - Posted at: over 13 years ago
  - Comments: 4


