# Unable to receive events in lovebeat when sent from statsd

**URL:** <https://discuss.elastic.co/t/unable-to-receive-events-in-lovebeat-when-sent-from-statsd/186550>\
**Category:** Logstash\
**Created:** [June 19, 2019, 9:48pm UTC](https://discuss.elastic.co/t/unable-to-receive-events-in-lovebeat-when-sent-from-statsd/186550 "2019-06-19T21:48:47Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![H\_C1](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/h_c1/32/46843_2.png) [@H\_C1](https://discuss.elastic.co/u/H_C1)\
**Post date:** [June 19, 2019, 9:48pm UTC](https://discuss.elastic.co/t/unable-to-receive-events-in-lovebeat-when-sent-from-statsd/186550/1 "2019-06-19T21:48:47Z")

</div>

HI  
I'm unable to receive events in [lovebeat](https://lovebeat.readthedocs.io) when sent from statsd while I can receive them in elasticsearch.

The logstash output configuration is as follows :  
output {  
elasticsearch {  
hosts =\> ["localhost:9200"]  
index =\> "syslog-demo"  
}  
statsd {  
host =\> "127.0.0.1"  
namespace =\> "logstash"  
port =\> "8127"  
count =\> {  
"http.bytes.beat" =\> "1"  
}  
}   
stdout {  
codec =\> rubydebug  
}  
}  
I have lovebeat running at localhost and 8127 port.

2019/06/19 23:15:33 INFO Starting your browser with [http://localhost:8080](http://localhost:8080) - the Lovebeat Web UI.  
2019/06/19 23:15:33 INFO UDP listening on :8127  
2019/06/19 23:15:33 INFO TCP listening on :8127  
2019/06/19 23:15:33 INFO HTTP listening on :8080

I read [Monitor inactivity in log files](https://discuss.elastic.co/t/monitor-inactivity-in-log-files/50597/7) but it did not help.

Notice that I ran successfully the following command , which makes me think that Lovebeat is running well. The metric is well displayed in the Lovebeat Web UI.  
_echo "invoice.mailer.beat:1|c" | nc -4u -w0 localhost 8127_

I'm now stuck . Any clue ?  
Many thanks

---

<div class="post-metadata">

**Author:** ![H\_C1](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/h_c1/32/46843_2.png) [@H\_C1](https://discuss.elastic.co/u/H_C1)\
**Post date:** [June 20, 2019, 6:02am UTC](https://discuss.elastic.co/t/unable-to-receive-events-in-lovebeat-when-sent-from-statsd/186550/2 "2019-06-20T06:02:32Z")

</div>

After a lot of digging , here the result

The following works (the lovebeat server accepts the metric)  
echo "a.b.c.beat:1|c" | nc -4u -w0 localhost 8127  
The following fails (the lovebeat server refuses the metric)  
echo "a.b.C.beat:1|c" | nc -4u -w0 localhost 8127  
My understanding is that the metric name should not have uppercase characters.

As stated in the _**[statsd](https://www.elastic.co/guide/en/logstash/current/plugins-outputs-statsd.html#plugins-outputs-statsd-count)**_ documentation, The host name is the first element of the metric name, and unfortunately, my host name has uppercase characters.  
I use now the [sender](https://www.elastic.co/guide/en/logstash/current/plugins-outputs-statsd.html#plugins-outputs-statsd-sender) property to avoid this naming problem and it works.

statsd {  
host =\> "127.0.0.1"  
sender =\> "myservername"  
namespace =\> "logstash"  
port =\> "8127"  
count =\> {  
"http.bytes.beat" =\> "1"  
}  
}

Hope this helps others.

---

<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 18, 2019, 6:02am UTC](https://discuss.elastic.co/t/unable-to-receive-events-in-lovebeat-when-sent-from-statsd/186550/3 "2019-07-18T06:02:44Z")

</div>

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