# Events fields & notifications

**URL:** <https://community.graylog.org/t/events-fields-notifications/13814>\
**Category:** Graylog Central (peer support)\
**Created:** [February 5, 2020, 8:44pm UTC](https://community.graylog.org/t/events-fields-notifications/13814 "2020-02-05T20:44:11Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![shoothub](https://sea2.discourse-cdn.com/flex016/user_avatar/community.graylog.org/shoothub/32/6412_2.png) [@shoothub](https://community.graylog.org/u/shoothub)\
**Post date:** [February 6, 2020, 7:20am UTC](https://community.graylog.org/t/events-fields-notifications/13814/2 "2020-02-06T07:20:05Z")

</div>

Check my previous post about this topis:

> [@Extractors value in body of notifications](https://community.graylog.org/t/extractors-value-in-body-of-notifications/13484/2):
>
> Hello, syntax is the same also in latest version 3.1 Check if you setup correctly Message Backlog parameter in Alerts - Event Definitions - Edit - tab Notification, check field Message Backlog and set to 1. It’s a number of messages to be included in Notification, if 0 no field will be extracted in message. I use for example this snippet after user connect to switch: ${if backlog} ${foreach backlog message} User ${message.fields.username} connected to switch ${message.source} from IP ${me…

---

_[View the full topic](https://community.graylog.org/t/events-fields-notifications/13814)._