# Cisco netflow and format of flow\_start\_msec

**URL:** <https://discuss.elastic.co/t/cisco-netflow-and-format-of-flow-start-msec/122720>\
**Category:** Logstash\
**Created:** [March 6, 2018, 12:31pm UTC](https://discuss.elastic.co/t/cisco-netflow-and-format-of-flow-start-msec/122720 "2018-03-06T12:31:20Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![adankert](https://avatars.discourse-cdn.com/v4/letter/a/cc9497/32.png) [@adankert](https://discuss.elastic.co/u/adankert)\
**Post date:** [March 6, 2018, 12:31pm UTC](https://discuss.elastic.co/t/cisco-netflow-and-format-of-flow-start-msec/122720/1 "2018-03-06T12:31:21Z")

</div>

When I receive netflow data from Cisco there seems to be an issue with the type of flow\_start\_msec.  
I assume this should be treated as "date". But I get error messages like this:

`"error"=>{"type"=>"mapper_parsing_exception", "reason"=>"failed to parse [netflow.flow_start_msec]", "caused_by"=>{"type"=>"illegal_argument_exception", "reason"=>"Invalid format: \"11298594751613545221\" is malformed at \"8594751613545221\""}}}}}`

Does anybody know the details of this field from Cisco's side?

---

<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:** [April 3, 2018, 12:31pm UTC](https://discuss.elastic.co/t/cisco-netflow-and-format-of-flow-start-msec/122720/2 "2018-04-03T12:31:33Z")

</div>

Closed on April 3, 2018, 12:31pm UTC

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