# Infoblox module parsing

**URL:** https://discuss.elastic.co/t/infoblox-module-parsing/296336
**Category:** Beats
**Tags:** filebeat
**Created:** [February 4, 2022, 6:42pm UTC](https://discuss.elastic.co/t/infoblox-module-parsing/296336 "2022-02-04T18:42:28Z")
**Posts on this page:** 2
**Page:** 1

<div class="post-metadata">

### Author: ![willemdh](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/willemdh/32/16922_2.png) [@willemdh](https://discuss.elastic.co/u/willemdh)
#### Post date: [February 4, 2022, 6:42pm UTC](https://discuss.elastic.co/t/infoblox-module-parsing/296336/1 "2022-02-04T18:42:28Z")

</div>

Hello,

The Infoblox rsa module has 'a lot of room for improvement'.. Multiple fields are very badly parsed. For example a small extract of the network.interface.name field :

 ![image](https://us1.discourse-cdn.com/elastic/original/3X/9/c/9c0f0eb0e861b19c9f6483e75da469e235d1c0ee.png)

As you can see there are multiple issues here.. And that is just the tip of the iceberg. Is this a module developed by Elastic? Can I make a GitHub issue to ask for some improvements please? As in it's current state, I prefer to keep using my own Logstash pipeline. (which is not ecs compliant)

Willem

---

<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: [March 4, 2022, 8:43pm UTC](https://discuss.elastic.co/t/infoblox-module-parsing/296336/2 "2022-03-04T20:43:23Z")

</div>

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