# Overriding log event status

**URL:** <https://community.dynatrace.com/t/overriding-log-event-status/37070>\
**Category:** Logs\
**Tags:** log-processing, log-monitoring-class\
**Created:** [October 28, 2022, 3:32pm UTC](https://community.dynatrace.com/t/overriding-log-event-status/37070 "2022-10-28T15:32:30Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![MartyM](https://avatars.discourse-cdn.com/v4/letter/m/5f8ce5/32.png) [@MartyM](https://community.dynatrace.com/u/MartyM)\
**Post date:** [October 28, 2022, 3:32pm UTC](https://community.dynatrace.com/t/overriding-log-event-status/37070/1 "2022-10-28T15:32:30Z")

</div>

I have written a log processing rule to parse a log file.&nbsp; Some log events have a secondary event log level that can be different from primary log level.&nbsp; I want to set both the event’s loglevel and status to the secondary log level.&nbsp; When I test the rule it works perfectly, setting both the loglevel and status to “WARNING” using a FIELD\_ADD.&nbsp; However, when that rule is used to ingest the log data both fields are set to “NONE”.&nbsp; Is there something more I need to do?

---

<div class="post-metadata">

**Author:** ![ChadTurner](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/chadturner/32/161_2.png) [@ChadTurner](https://community.dynatrace.com/u/ChadTurner)\
**Post date:** [January 20, 2023, 3:09pm UTC](https://community.dynatrace.com/t/overriding-log-event-status/37070/2 "2023-01-20T15:09:04Z")

</div>

[@MartyM](https://community.dynatrace.com/user/56053)&nbsp;were you able to get this issue resolved?

---

<div class="post-metadata">

**Author:** ![MartyM](https://avatars.discourse-cdn.com/v4/letter/m/5f8ce5/32.png) [@MartyM](https://community.dynatrace.com/u/MartyM)\
**Post date:** [January 23, 2023, 2:49pm UTC](https://community.dynatrace.com/t/overriding-log-event-status/37070/3 "2023-01-23T14:49:14Z")

</div>

[@ChadTurner](https://community.dynatrace.com/user/14877)&nbsp;Yes, I just needed to another command to update the status field.

// Make sure the loglevel matches the event status| FIELDS\_ADD(status:UPPER(loglevel))
