# Packetbeat memory and cpu consumption when monitoring cassandra ... continuation

**URL:** <https://discuss.elastic.co/t/packetbeat-memory-and-cpu-consumption-when-monitoring-cassandra-continuation/109750>\
**Category:** Beats\
**Tags:** packetbeat\
**Created:** [November 30, 2017, 1:07pm UTC](https://discuss.elastic.co/t/packetbeat-memory-and-cpu-consumption-when-monitoring-cassandra-continuation/109750 "2017-11-30T13:07:26Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![chemt79](https://avatars.discourse-cdn.com/v4/letter/c/57b2e6/32.png) [@chemt79](https://discuss.elastic.co/u/chemt79)\
**Post date:** [November 30, 2017, 1:07pm UTC](https://discuss.elastic.co/t/packetbeat-memory-and-cpu-consumption-when-monitoring-cassandra-continuation/109750/1 "2017-11-30T13:07:26Z")

</div>

This is a continuation of topic  
[Packetbeat memory and cpu consumption when monitoring cassandra](https://discuss.elastic.co/t/packetbeat-memory-and-cpu-consumption-when-monitoring-cassandra/105210)

I had the same problem. **Packetbeat** consumed a lot of memory. The problem was resolved by excluding AUTH\_SUCCESS packets.

```
packetbeat.protocols.cassandra:
  #Cassandra port for traffic monitoring.
  ports: [9042]
  ignored_ops: ["AUTH_SUCCESS"]

```

As I understood the **packetbeat** had been receiving too many of packets of this kind.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [December 28, 2017, 1:08pm UTC](https://discuss.elastic.co/t/packetbeat-memory-and-cpu-consumption-when-monitoring-cassandra-continuation/109750/2 "2017-12-28T13:08:00Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.