Destination Page

The destination connector page has information about the destination connector’s schema, configuration, and actions for editing the connector

Navigating to the destination page

Click on 1. the destination connector listed in the destination section in order to see the source details.

👍

Recall that you can egress individual anomalies from datapoint pipelines

Destination overview

The destination page lists all of the 1. features (schema) for egressed data points. The 2. right side panel shows the configuration for the connectors and includes an actions menu indicated by the three vertical dots in the upper right-hand corner including update option to update parameters.

Schema overview

All egress tables from Validio follows the same Schema regardless of which source the data is validated where from.

FeatureDescription
uuidAuto generated unique identifier of the anomaly.
timeTimestamp of when the anomaly was caught.
is_anomalyWill be true for all egressed points.
applied_filterWhich filter (s) that was applied and whether the filter labeled the datapoint an anomaly(see details below)
datapointThe specific datapoint in questions containing all the feature values.

'applied_filter' details

One datapoint can be evaluated by multiple filters, e.g. on different features of the data. As long as one of the Filters labels the datapoint an anomaly, the point will be egressed. The JSON egressed in the applied_filter feature will list all applied filters along with boolean value corresponding to whether the filter evaluate the datapoint as an anomaly or not. The filter_id can be found in the URL when navigating the particular filter in the platform.

Example:

[
  {
    "filter_id": "FTRF_ksleKxovmSG4peLApoQK51w",
    "is_anomaly": true
  },
  {
    "filter_id": "FTRF_BLCpoSNzGHemp5T32089KhX",
    "is_anomaly": false
  }
]