A final PR has been created to implement a limit parameter on the property value endpoint.

https://github.com/OpenNMS/opennms/pull/1650

The changes for this feature have been backported to foundation-2017. Another PR for this has been merged that implements the /alarms/properties/{propertyId} endpoint to implement autocomplete for the property values.

https://github.com/OpenNMS/opennms/pull/1638

The last remaining thing to do here is implement a limit query property for the autocomplete to provide a limit to the results that are returned.

https://github.com/OpenNMS/opennms/pull/1616 was merged to develop.

Property enumeration is currently working, auto-complete and looking up specific properties in pending.

Note that CXF can export Swagger by scanning annotations but I don't see an appropriate Swagger annotation for this sort of thing, ie. search terms in a string query value.

http://cxf.apache.org/docs/swagger2feature.html

One thing that would be nice here is to also provide autocomplete support for each search/orderBy term. I'm thinking something like:

/alarms/properties: Returns a list of all search/orderBy property objects for the alarms endpoint. The objects would include name, type (String, Long, Timestamp), and human-readable name.
/alarms/properties?q=node: Returns a list of all search/orderBy property names that match the q expression to use for autocomplete.
/alarms/properties/node.label: Returns a list of all node labels.
/alarms/properties/node.label?q=www.mycompan: Returns node labels matching the q expression to use for autocomplete.

We could reuse the node.label, etc. resources on all endpoints that support the same parameters.