Haproxy strconv.ParseFloat: parsing "": invalid syntax

Elastic Stack Beats
1

Dear Elastic Team,

I've configured the haproxy but still receiving the following error message:
"strconv.ParseFloat: parsing "": invalid syntax" as shown below. I'm wondering what i'm doing wrong. i also do not get the stats it's empty

   |@timestamp|       |May 16th 2019, 15:07:35.873|
    |---|---|---|
    |t  _id|      |c67BwGoBW9uGghWyUqyR|
    |t  _index|      |metricbeat-6.7.1-2019.05.16|
    |#  _score|    | - |
    |t  _type|      |doc|
    |t  beat.hostname|       |monitoring-metricbeat-1|
    |t  beat.name|       |OPSFINAL|
    |t  beat.version|       |6.7.1|
    |t  error.message|       |strconv.ParseFloat: parsing "": invalid syntax|
    |t  event.dataset|       |haproxy.info|
    |#  event.duration|       |3,208,008|
    |?  fields.env|     |  TESTENV|
    |t  host.name|       |FINAL|
    |t  metricset.host|       |lb-base:14567|
    |t  metricset.module|       |haproxy|
    |t  metricset.name|       |info|
    |#  metricset.rtt|       |3,20|
2

Not sure what we're looking at (?) Is this a Kibana question, because that error-message rather seems Beats related?

3

Dear Thomas,

I'm terrible sorry, it's a metricbeat problem and not a kibana.
Changed into beats-metricbeats.

4

yasin,

I'm not quite sure what I'm looking it. This appears to be ES event output of some kind? Can you enable debug logging and supply us with some logs? Also, what version of haproxy are you using?

5

Dear Alex,

As you also can see in the logs i don't have any stats information, i'm wondering what is causing the isue.

Log1:

2019-05-22T07:35:35.910Z	DEBUG	[publish]	pipeline/processor.go:309	Publish event: {
22/05/2019 09:35:35  "@timestamp": "2019-05-22T07:35:35.906Z",
22/05/2019 09:35:35  "@metadata": {
22/05/2019 09:35:35    "beat": "metricbeat",
22/05/2019 09:35:35    "type": "doc",
22/05/2019 09:35:35    "version": "6.7.1"
22/05/2019 09:35:35  },
22/05/2019 09:35:35  "event": {
22/05/2019 09:35:35    "dataset": "haproxy.stat",
22/05/2019 09:35:35    "duration": 3731983
22/05/2019 09:35:35  },
22/05/2019 09:35:35  "haproxy": {
22/05/2019 09:35:35    "stat": {
22/05/2019 09:35:35      "queue": {},
22/05/2019 09:35:35      "service_name": "",
22/05/2019 09:35:35      "server": {},
22/05/2019 09:35:35      "request": {
22/05/2019 09:35:35        "rate": {}
22/05/2019 09:35:35      },
22/05/2019 09:35:35      "session": {
22/05/2019 09:35:35        "rate": {}
22/05/2019 09:35:35      },
22/05/2019 09:35:35      "compressor": {},
22/05/2019 09:35:35      "status": "",
22/05/2019 09:35:35      "response": {
22/05/2019 09:35:35        "http": {}
22/05/2019 09:35:35      },
22/05/2019 09:35:35      "proxy": {
22/05/2019 09:35:35        "name": ""
22/05/2019 09:35:35      },
22/05/2019 09:35:35      "check": {
22/05/2019 09:35:35        "status": "",
22/05/2019 09:35:35        "health.last": "",
22/05/2019 09:35:35        "agent.last": ""
22/05/2019 09:35:35      },
22/05/2019 09:35:35      "connection": {}
22/05/2019 09:35:35    }
22/05/2019 09:35:35  },
22/05/2019 09:35:35  "fields": {
22/05/2019 09:35:35    "env": "TESTENV"
22/05/2019 09:35:35  },
22/05/2019 09:35:35  "beat": {
22/05/2019 09:35:35    "hostname": "monitoring-metricbeat-2",
22/05/2019 09:35:35    "version": "6.7.1",
22/05/2019 09:35:35    "name": "OPSFINAL_NODE1"
22/05/2019 09:35:35  },
22/05/2019 09:35:35  "host": {
22/05/2019 09:35:35    "name": "OPSFINAL_NODE1"
22/05/2019 09:35:35  },
22/05/2019 09:35:35  "metricset": {
22/05/2019 09:35:35    "module": "haproxy",
22/05/2019 09:35:35    "host": "avio-lb-base:14567",
22/05/2019 09:35:35    "rtt": 3731,
22/05/2019 09:35:35    "name": "stat"
22/05/2019 09:35:35  }
22/05/2019 09:35:35}

Log2:

22/05/2019 09:45:202019-05-22T07:45:20.654Z	DEBUG	[publish]	pipeline/processor.go:309	Publish event: {
22/05/2019 09:45:20  "@timestamp": "2019-05-22T07:45:20.651Z",
22/05/2019 09:45:20  "@metadata": {
22/05/2019 09:45:20    "beat": "metricbeat",
22/05/2019 09:45:20    "type": "doc",
22/05/2019 09:45:20    "version": "6.7.1"
22/05/2019 09:45:20  },
22/05/2019 09:45:20  "beat": {
22/05/2019 09:45:20    "name": "OPSFINAL_NODE1",
22/05/2019 09:45:20    "hostname": "monitoring-metricbeat-2",
22/05/2019 09:45:20    "version": "6.7.1"
22/05/2019 09:45:20  },
22/05/2019 09:45:20  "host": {
22/05/2019 09:45:20    "name": "OPSFINAL_NODE1"
22/05/2019 09:45:20  },
22/05/2019 09:45:20  "event": {
22/05/2019 09:45:20    "dataset": "haproxy.info",
22/05/2019 09:45:20    "duration": 2304259
22/05/2019 09:45:20  },
22/05/2019 09:45:20  "error": {
22/05/2019 09:45:20    "message": "strconv.ParseFloat: parsing \"\": invalid syntax"
22/05/2019 09:45:20  },
22/05/2019 09:45:20  "metricset": {
22/05/2019 09:45:20    "name": "info",
22/05/2019 09:45:20    "module": "haproxy",
22/05/2019 09:45:20    "host": "avio-lb-base:14567",
22/05/2019 09:45:20    "rtt": 2304
22/05/2019 09:45:20  },
22/05/2019 09:45:20  "fields": {
22/05/2019 09:45:20    "env": "TESTENV"
22/05/2019 09:45:20  }
22/05/2019 09:45:20}
22/05/2019 09:45:212019-05-22T07:45:21.686Z	DEBUG	[elasticsearch]	elasticsearch/client.go:337	PublishEvents: 1 events have been published to elasticsearch in 31.93157ms.
22/05/2019 09:45:212019-05-22T07:45:21.686Z	DEBUG	[publisher]	memqueue/ackloop.go:160	ackloop: receive ack [178: 0, 1]
22/05/2019 09:45:212019-05-22T07:45:21.686Z	DEBUG	[publisher]	memqueue/eventloop.go:535	broker ACK events: count=1, start-seq=624, end-seq=624
22/05/2019 09:45:21
6

Dear Alex,

And now i'm receiving the following error message:

failed fetching haproxy stat: error parsing CSV: empty csv file given

7

yasin,

Is that error message from the metricbeats logs? The CSV line appears to indicate that it received an empty response from the haproxy socket. Can you post any surrounding log lines as well?

Also, I would still like to know what version of haproxy you're using. Also, I assume these errors are constant, and you haven't been able to get any data out at all?

8

Dear Alex,

Yes, the logs from the metricbeats.
docker:rancher/lb-service-haproxy:v0.9.6
I will get the "surrounding log lines " as requested

9

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