classification of events not being limited by date

[pmos69]

I'll post some images to better demonstrate the issue.

Here's a selection of SNMP events between 2 nodes from sunday:
(608 events)

Here's a selection of SNMP events between the same nodes on monday:
(1524 events)

now, having sunday as the selected date/timeframe, select all the events (608):

and press F8 to dismiss them:

all 608 sunday events were classified.

But what happened to the same type events on monday between the same nodes?
Let's check:

...they were all classified as well, even though they were not included in the classification selection.

[int13h]

Can you reliably reproduce this? It seems a little odd because the event
id's are generated with each view. I don't really understand how events
that weren't part of the current view were included when the class action
fired.

On Mon, Sep 9, 2013 at 11:08 AM, Pedro Simoes notifications@github.comwrote:

I'll post some images to better demonstrate the issue.

Here's a selection of SNMP events between 2 nodes from sunday:
(608 events)

[image: image]https://f.cloud.github.com/assets/123733/1107188/e34715f6-1957-11e3-9d87-b0c8a55857fa.png

Here's a selection of SNMP events between the same nodes on monday:
(1524 events)

[image: image]https://f.cloud.github.com/assets/123733/1107206/3afa9c50-1958-11e3-92b0-a13f4f43c293.png

now, having sunday as the selected date/timeframe, select all the events
(608):

[image: image]https://f.cloud.github.com/assets/123733/1107220/ba2ec9d8-1958-11e3-9577-32aa22426fde.png

and press F8 to dismiss them:

[image: image]https://f.cloud.github.com/assets/123733/1107228/d62e3d26-1958-11e3-9edf-bc226587ee76.png

all 608 sunday events were classified.

But what happened to the same type events on monday between the same nodes?
Let's check:

[image: image]https://f.cloud.github.com/assets/123733/1107244/2b27ebce-1959-11e3-9390-8a5402b3a707.png

...they were all classified as well, even though they were not included in
the classification selection.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/32
.

Paul Halliday
http://www.pintumbler.org/

[int13h]

There has been a patch for sguild that may address this issue. Can you please replace you current SguildEvent.tcl with this one https://github.com/bammv/sguil/blob/master/server/lib/SguildEvent.tcl and see if the problem still exists?

[pmos69]

Sorry for the delay.
After a few reboots (for other reasons) I can't reproduce the issue, even though I haven't updated the sguil script.
So I guess this had other reasons for happening...
I'll close the issue.