# Netflow: Unsupported field in template

**URL:** <https://discuss.elastic.co/t/netflow-unsupported-field-in-template/119772>\
**Category:** Logstash\
**Created:** [February 14, 2018, 10:46am UTC](https://discuss.elastic.co/t/netflow-unsupported-field-in-template/119772 "2018-02-14T10:46:56Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![bobspunkhouse](https://avatars.discourse-cdn.com/v4/letter/b/e36b37/32.png) [@bobspunkhouse](https://discuss.elastic.co/u/bobspunkhouse)\
**Post date:** [February 14, 2018, 11:50am UTC](https://discuss.elastic.co/t/netflow-unsupported-field-in-template/119772/2 "2018-02-14T11:50:12Z")

</div>

Working with sarlacpit on this issue, I've found the 'unsupported field in template' warning appears in log when passing the following field from a Cisco flow record to logstash:

**collect ipv4 ttl**

After removing the field from the Cisco flow record template, we've seen the error no longer appears in the logstash logs, and flows are received.

---

_[View the full topic](https://discuss.elastic.co/t/netflow-unsupported-field-in-template/119772)._