By default the Measurements API in OpenNMS operates in "strict" mode, which means that queries that contain any non-existent resources/attributes will be rejected. This API also supports a "relaxed" mode which does not enforce this constraint.
I don't recall what the caveats are, but we should (possibly optionally) allow queries to be executed which contain non-existent resources, only returning the data for those that do actually exist.
By default the Measurements API in OpenNMS operates in "strict" mode, which means that queries that contain any non-existent resources/attributes will be rejected. This API also supports a "relaxed" mode which does not enforce this constraint.
I don't recall what the caveats are, but we should (possibly optionally) allow queries to be executed which contain non-existent resources, only returning the data for those that do actually exist.