Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Alarmd Drools context logs constantly in DEBUG mode

Description

The following 4 lines can be found in alarmd.log every millisecond filling up alarmd.log quite quickly and making it very difficult to read:

2018-12-11 09:22:25,300 DEBUG [Timer-1] o.o.n.a.d.DroolsAlarmContext: Firing rules.
2018-12-11 09:22:25,300 DEBUG [Timer-1] o.d.c.c.DefaultAgenda: State was INACTIVE is now FIRING_ALL_RULES
2018-12-11 09:22:25,301 DEBUG [Timer-1] o.d.c.c.DefaultAgenda: State was FIRING_ALL_RULES is now HALTING
2018-12-11 09:22:25,301 DEBUG [Timer-1] o.d.c.c.DefaultAgenda: State was HALTING is now INACTIVE

 

 

Acceptance / Success Criteria

None

Lucidchart Diagrams

Activity

Show:

Jesse White January 30, 2019 at 7:44 PM

Can you share an example that demonstrates this? From what I have observed, these 4 lines should be printed roughly every second.

David Hustace January 30, 2019 at 4:22 PM

It's actually sending multiple log statements every millisecond.

Jesse White December 18, 2018 at 5:44 PM

These get logged every second when the engine ticks and are very useful for DEBUGging problems with alarmd now that we use Drools.

Won't Fix

Details

Assignee

Reporter

Components

Affects versions

Priority

PagerDuty

Created December 11, 2018 at 2:27 PM
Updated January 30, 2019 at 7:44 PM
Resolved January 30, 2019 at 2:13 PM

Flag notifications