Skip to content
This repository has been archived by the owner on Feb 11, 2020. It is now read-only.

_timestamp field in mqtt message causes logstash ingestion failure #16

Open
tedder opened this issue Sep 27, 2018 · 0 comments
Open

_timestamp field in mqtt message causes logstash ingestion failure #16

tedder opened this issue Sep 27, 2018 · 0 comments

Comments

@tedder
Copy link

tedder commented Sep 27, 2018

I have some mqtt messages coming in that already have a _timestamp field, and logstash complains about these.

2018/09/27 17:38:42.251161 mqttbeat.go:87: DBG MQTT MESSAGE RECEIVED {"_timestamp": 1538069922, "actual": 21.6, "target": 0.0}
2018/09/27 17:38:42.251298 mqttbeat.go:147: DBG Payload decoded - json
2018/09/27 17:38:42.251421 client.go:203: DBG Publish: {
  "@timestamp": "2018-09-27T17:38:42.251Z",
  "_timestamp": 1538069922,
  "actual": 21.6,
  "beat": {
    "index": "mqttbeat",
    "type": "message"

I don't know what the answer is since I can't change my incoming messages, but I at least wanted to log it.

@tedder tedder changed the title _timestamp field in mqtt message causes WARN in logstash _timestamp field in mqtt message causes logstash ingestion failure Sep 27, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant