# Pipeline rule breaks feed

**URL:** <https://community.graylog.org/t/pipeline-rule-breaks-feed/31466>\
**Category:** Graylog Central (peer support)\
**Created:** [February 10, 2024, 5:18pm UTC](https://community.graylog.org/t/pipeline-rule-breaks-feed/31466 "2024-02-10T17:18:31Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![2045kdy](https://avatars.discourse-cdn.com/v4/letter/2/f1d935/32.png) [@2045kdy](https://community.graylog.org/u/2045kdy)\
**Post date:** [February 10, 2024, 7:33pm UTC](https://community.graylog.org/t/pipeline-rule-breaks-feed/31466/3 "2024-02-10T19:33:40Z")

</div>

found this post , [https://community.graylog.org/t/using-a-csv-lookup-table-within-a-pipeline/3707/13](https://community.graylog.org/t/using-a-csv-lookup-table-within-a-pipeline/3707/13) , unsure why this is but, remove the rule from stage, went in maintenance on index, rotated then the reapplied original rule:

> rule “iptoname”  
> when  
> has\_field(“src\_ip”)  
> then  
> let update\_source = lookup\_value(“ip\_device\_name”, to\_string($message.src\_ip));  
> set\_field(“devicename”, update\_source);  
> end  
> now its showing just the value:  
> devicename  
> homeassistant

---

_[View the full topic](https://community.graylog.org/t/pipeline-rule-breaks-feed/31466)._