/api/tree/notmatched

When processing a TSMeta, if the tree has strictMatch enabled and the meta fails to match on a rule in any level of the set, a not matched entry will be recorded. This endpoint allows for retrieving the list of TSUIDs that failed to match a rule set. It is useful for debugging in that if you find a TSUID in this list, you can pass it through the /tree/test endpoint to get details on why the meta failed to match.

Note

Calling this endpoint without a list of one or more TSUIDs will return all non-matched TSUIDs in the tree. If you have a large number of timeseries in your system, the response can potentially be very large. Thus it is best to use this endpoint with specific TSUIDs.

Note

If storeFailures is disabled for the tree, this endpoint will not return any data. Not Matched entries will still appear in the TSD’s logs.

Verbs

• GET

Requests

The following fields are used for this endpoint

Response

A successful response will return a map of key/value pairs where the unrecorded TSUID as the key and a message about which rule failed to match as the value. The response will only return not matched entries that were found. If one or more of the TSUIDs requested did not result in a not matched entry, it will not be returned with the result. This may mean that the TSMeta has not been processed yet. Note that if no failed matches have occurred or the tree hasn’t processed any data yet, the result set will be empty. If the requested tree did not exist in the system, a 404 will be returned with an error message. If invalid data was supplied a 400 error will be returned.

Example Request

http://localhost:4242/api/tree/notmatched?treeId=1&tsuids=010101,020202

Example Response

{
    "010101": "Failed rule 0:0",
    "020202": "Failed rule 1:1"
}