# Possible bug in Kafka metadata

**URL:** <https://discuss.elastic.co/t/possible-bug-in-kafka-metadata/139059>\
**Category:** Logstash\
**Created:** [July 8, 2018, 3:28pm UTC](https://discuss.elastic.co/t/possible-bug-in-kafka-metadata/139059 "2018-07-08T15:28:53Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![crickes](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/crickes/32/18009_2.png) [@crickes](https://discuss.elastic.co/u/crickes)\
**Post date:** [July 8, 2018, 3:28pm UTC](https://discuss.elastic.co/t/possible-bug-in-kafka-metadata/139059/1 "2018-07-08T15:28:54Z")

</div>

Hi,

I' have been playing around with using the Kafka input plugin and I wanted to use some of the metadata to assist with debugging some issues. I output the metadata to stdout with the metadata option set to true, and sure enough I could see the metadata, but the values don't seem to match up with the field names.

"kafka" =\> {  
"key" =\> "1531062676",  
"partition" =\> 0,  
"timestamp" =\> -1,  
"offset" =\> 117661020,  
"topic" =\> "nx-cdrs",  
"consumer\_group" =\> "nx-cdrs-1"  
}

Looks to me as if the key and timestamp fields have been mixed up as the value in the key field is the value i was expecting to see in the timestamp field.

---

<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:** [August 5, 2018, 3:28pm UTC](https://discuss.elastic.co/t/possible-bug-in-kafka-metadata/139059/2 "2018-08-05T15:28:54Z")

</div>

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