# Collectd codec and notifications

**URL:** <https://discuss.elastic.co/t/collectd-codec-and-notifications/1603>\
**Category:** Logstash\
**Created:** [May 31, 2015, 12:56pm UTC](https://discuss.elastic.co/t/collectd-codec-and-notifications/1603 "2015-05-31T12:56:59Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![gb12345](https://avatars.discourse-cdn.com/v4/letter/g/8491ac/32.png) [@gb12345](https://discuss.elastic.co/u/gb12345)\
**Post date:** [May 31, 2015, 12:56pm UTC](https://discuss.elastic.co/t/collectd-codec-and-notifications/1603/1 "2015-05-31T12:56:59Z")

</div>

I am attempting to use collectd to monitor various stats on many linux hosts. All the stats are sent to logstash via UDP and the collectd logstash codec. All worked great and I can see all my stats/hosts in kibana.

I have now configured collectd to send notifications if, for example, load is to go above a certain threshold. If I disable the collectd codec in logstash and divert to stdout I can see all these notifications (in the collectd binary format, with a clear text notification string). With the codec enabled all stats get through but the notifications appear to be dropped, with no acknowledgement of their existence.

Has anyone else had any luck with collectd notifications into logstash? Does the codec simply not support notifications? Or is this a bug?

---

<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:** [July 6, 2017, 5:38am UTC](https://discuss.elastic.co/t/collectd-codec-and-notifications/1603/2 "2017-07-06T05:38:58Z")

</div>


