# Printer tracking pipeline - $message\_ field names not working for set or rename

**URL:** <https://community.graylog.org/t/printer-tracking-pipeline-message-field-names-not-working-for-set-or-rename/25847>\
**Category:** Graylog Central (peer support)\
**Created:** [September 21, 2022, 6:48pm UTC](https://community.graylog.org/t/printer-tracking-pipeline-message-field-names-not-working-for-set-or-rename/25847 "2022-09-21T18:48:14Z")\
**Posts on this page:** 1\
**Showing post:** 9

<div class="post-metadata">

**Author:** ![tmacgbay](https://sea2.discourse-cdn.com/flex016/user_avatar/community.graylog.org/tmacgbay/32/3878_2.png) [@tmacgbay](https://community.graylog.org/u/tmacgbay)\
**Post date:** [September 22, 2022, 4:55pm UTC](https://community.graylog.org/t/printer-tracking-pipeline-message-field-names-not-working-for-set-or-rename/25847/9 "2022-09-22T16:55:10Z")

</div>

That all makes sense to me - one thing to help would be to look a the [Graylog Schema](https://community.graylog.org/t/graylog-information-model-schema/21540) so you can be consistent with naming conventions for field names and the like. Also, take into consideration the message you want to drop, particularly chatty ones, that you don’t want. Try to standardize dropping them or shunting them to an index that has a shorter life span. Trimming out parts of Windows messages… some have a paragraph or two of explanation that comes with each message. 🙂

---

_[View the full topic](https://community.graylog.org/t/printer-tracking-pipeline-message-field-names-not-working-for-set-or-rename/25847)._