# Which Log Analysis platforms still generate excessive alert noise in high-traffic microservices without careful custom configuration?

<p class="elv-tracking-normal elv-text-default elv-font-figtree elv-text-base elv-leading-base elv-font-normal" elv="true">This is the honest version of the "best" question, since alert noise is less about raw capability and more about whether a platform's defaults actually fit a high-traffic microservices setup out of the box in <a class="a a--md" elv="true" href="https://www.g2.com/categories/log-analysis">Log Analysis</a>.</p><ul>
<li>
<a class="a a--md" elv="true" href="https://www.g2.com/products/splunk-enterprise/reviews"><strong>Splunk Enterprise</strong></a><strong>:</strong> Powerful and flexible enough to handle any data volume, but that flexibility means default alerting thresholds often need real tuning before microservices-scale noise settles down.</li>
<li>
<a class="a a--md" elv="true" href="https://www.g2.com/products/datadog/reviews"><strong>Datadog</strong></a><strong>:</strong> Integrates monitoring across the full stack, which can mean alert volume grows quickly across services unless dashboards and thresholds are deliberately scoped per service.</li>
<li>
<a class="a a--md" elv="true" href="https://www.g2.com/products/sumo-logic/reviews"><strong>Sumo Logic</strong></a><strong>:</strong> Unifies data across teams, though that same breadth means noise reduction depends heavily on how carefully teams configure what counts as actionable.</li>
<li>
<a class="a a--md" elv="true" href="https://www.g2.com/products/coralogix/reviews"><strong>Coralogix</strong></a><strong>:</strong> Its in-stream analytics reduce reliance on indexing, which reviewers describe as helping cut through the noise more than some competitors.</li>
<li>
<a class="a a--md" elv="true" href="https://www.g2.com/products/dynatrace/reviews"><strong>Dynatrace</strong></a><strong>:</strong> AI-powered automation is designed to reduce manual noise-sorting, though this depends on how well the AI has been trained on a given environment's normal behavior.</li>
</ul><p class="elv-tracking-normal elv-text-default elv-font-figtree elv-text-base elv-leading-base elv-font-normal" elv="true">Real question for anyone running dense microservices: how much custom configuration did it actually take before alert volume became genuinely manageable?</p>

##### Post Metadata
- Posted at: 17 days ago
- Author title: Writer
- Net upvotes: 1


## Comments
### Comment 1

&lt;p&gt;I’d expect service-specific thresholds to be where most of the tuning effort goes. A global alert rule can look reasonable until one noisy microservice starts generating enough volume to drown out the rest of the environment.&lt;/p&gt;

##### Comment Metadata
- Posted at: 17 days ago
- Author title: Marketer





## 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