Issues
- Searching for alarms in the v2 API with a reductionKey that includes a comma or semicolon results in a 500 errorNMS-12777Resolved issue: NMS-12777David Schlenk
- inadequate performance of alarms endpoint of v1 REST APINMS-12764
- Netflow ingress performance regressionNMS-12724Resolved issue: NMS-12724Jesse White
- bin/opennms returns 0 when stopped instead of 3NMS-12672
- Online documentation links in snapshot builds are invalidNMS-12567Resolved issue: NMS-12567
- "No future found for message" warnings in telemetryd logNMS-12565Resolved issue: NMS-12565Matthew Brooks
- The OpenNMS web UI has encountered an error that it does not know how to handle.NMS-12539Resolved issue: NMS-12539
- Selecting an Icon on Topology Map breaks the mapNMS-12532Resolved issue: NMS-12532Benjamin Reed
- Minion ignores credentials in environment variablesNMS-12530
- Splitting Docker documentation in Horizon, Minion and SentinelNMS-12529Resolved issue: NMS-12529Ronny Trommer
- Migrate config-tester wiki to the docsNMS-12527Resolved issue: NMS-12527Marcel Fuhrmann
- Add support for SCL PostgreSQL for our opennms meta packageNMS-12523
- Downtime model change was not updated in the docsNMS-12520Resolved issue: NMS-12520Ronny Trommer
- Custom Resource Performance Reports with error Missing ResourceIdNMS-12516
14 of 14
Searching for alarms in the v2 API with a reductionKey that includes a comma or semicolon results in a 500 error
Fixed
Description
Acceptance / Success Criteria
None
Attachments
1
Lucidchart Diagrams
Details
Assignee
David SchlenkDavid SchlenkReporter
David SchlenkDavid SchlenkLabels
HB Grooming Date
Jul 07, 2020HB Backlog Status
SprintComponents
Sprint
NoneFix versions
Priority
Minor
Details
Details
Assignee
David Schlenk
David Schlenk
Reporter
David Schlenk
David SchlenkLabels
HB Grooming Date
Jul 07, 2020
HB Backlog Status
Sprint
Components
Sprint
None
Fix versions
Priority
MinorPagerDuty
PagerDuty
PagerDuty
Created June 25, 2020 at 9:08 PM
Updated July 22, 2020 at 7:52 PM
Resolved July 22, 2020 at 7:52 PM
Activity
Show:
Benjamin ReedJuly 22, 2020 at 7:52 PM
Merged to foundation-2019
David SchlenkJuly 13, 2020 at 9:28 PM
@Sandy Skipper I tried that, but the same query does not work on that branch. It might have something to do with wildcards. I talked wtih Ben and Jesse in chat and they said foundation-2019 is enough as it's just doc and test.
Sandy SkipperJuly 7, 2020 at 3:28 PM
please retarget your PR to foundation-2017.
David SchlenkJune 26, 2020 at 1:06 AM
Okayyyy well I was writing the test and noticed that in another one there's mention of double escaping and then I tried using %252C instead of %2C and wouldn't you know it, it works! Anyway I wrote tests for it and then I added some very minimal documentation for the v2 API including a note about this in PR 3050.
David SchlenkJune 25, 2020 at 9:10 PM
I'm working on writing a (failing) test to illustrate the problem and will update this with a link to the branch when ready.
While attempting to move an integration that uses the v1 alarms REST API to v2 due to poor performance in v1 (), we found that attempting to filtering on reductionKey fails if the query includes a percent-encoded comma or semicolon, despite the fact that
search.decode.valuesis set totruein the CXF-RS config.]Stack trace attached.