devicehistory search by date ignores date

Bug #1242606 reported by John-Magne Bredal
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Network Administration Visualized
Confirmed
Medium
Unassigned

Bug Description

Gro-Anita H Vindheim reported that device history seemingly ignores date when filtering by date.

The two attachments display search input and result that indicates either some sort of expectancy related problem or a bug.

Revision history for this message
John-Magne Bredal (john-m-bredal) wrote :
Revision history for this message
John-Magne Bredal (john-m-bredal) wrote :
description: updated
Revision history for this message
Gro-Anita Vindheim (gro-anita-vindheim) wrote :

Did some research.

Seems like the filtering by date works for
Type = All snmpState

Does NOT work for
Type = "All", "boxState"

Haven't tried other types of events/alerts.

One more thing:
When the date filtereing works, it seems a bit unlogical.
Ex:
To show results for 18/10, "To" must be set to 19/10.

I suspect time is set to 00:00 or something?

Changed in nav:
status: New → Confirmed
importance: Undecided → Medium
Revision history for this message
Morten Brekkevold (mbrekkevold) wrote :

Actually, the search does not ignore dates at all, but it filters stateless alerts wrong somehow.

A stateless alert will have a start time, but no end time, as it represents a point in time, and not an interval of time. It appears that stateless alerts are filtered according to the criteria "start_time >= search_from_date" but is missing "start_time <= search_to_date".

In effect, whatever start date you enter in the form, _all_ stateless alerts that match the other criteria and occurred after or on the starting date will be displayed.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.