The search page for events is not working as expected

Description

If you go to "Status -> Events" and then click on "Advanced Search", you'll see a big form to build a custom filter, and apply it to the events page.

I tried adding partial content on the node label, and click search, but the output is not filtered.

I tried adding partial content on the IP address, and click search, but the output is not filtered.

I tried selecting a service, and click search, but the output is not filtered.

If I apply several filter rules, I can see all of them on the URLs, but the output is not filtered.

It seems like the format for the filters is invalid.

Acceptance / Success Criteria

None

Lucidchart Diagrams

Activity

Show:

Alejandro Galue January 3, 2017 at 11:30 AM

The solution created for `foundation-2016` on `1bde36deb022ec342e326e57a0de39c8216263d1` has been cherry-picked on `foundation`.

Alejandro Galue December 14, 2016 at 11:08 AM

A customer reported the problem on Meridian 2015. The solution should be ported from foundation-2016 into foundation.

Alejandro Galue October 6, 2016 at 2:04 PM
Edited

Alejandro Galue October 6, 2016 at 2:02 PM

I was able to verify that if I remove WebSecurityUtils when setting the queryString variable, the filters work as expected.

Alejandro Galue October 6, 2016 at 12:30 PM
Edited

I found some key differences between AlarmQueryServlet.java and EventQueryServlet.java, specially when I saw that the query parameters returned by the Events Advanced Search are using the URL encoded version of "&", instead of a plain "&" for the separator. In fact, if I fix the separator on a returned URL from the advanced query, I can see the filtered output.

Here are the differences on the controllers:

Alarms

Events

So, WebSecurityUtils seems to be the problem for some reason, because the search on alarms is working as expected.

Fixed

Details

Assignee

Reporter

Labels

Components

Affects versions

Priority

PagerDuty

Created October 6, 2016 at 11:35 AM
Updated January 3, 2017 at 4:29 PM
Resolved January 3, 2017 at 11:30 AM