Testing your tagger

A successful test invocation of any given tagger version is required before that version may be used by our system at ingest, or manually triggered by you as a backfill invocation.

Running a test

You may create a test invocation from either the event autotagging dashboard or from a specific tagger's details page.

1. Click "Test".
2. Select the tagger you want to test from the dropdown; the latest version is selected by default and is the one you want to use in most cases.
3. Use the provided search UI to find the robologs you want to use for the test.
4. Click "+ Add" to add a robolog to the test.
5. Click "Run test".

Your test invocation is queued and you are prompted to go to the tagger's details page. From there, you may view the status of the ongoing invocation and access the results once the invocation has completed. The total time to complete a test invocation depends on the number of robologs used in the test and the complexity of the tagger definition.

Viewing results

The details and results of a test invocation are visible from the tagger's details invocation list. Each invocation listed shows the invocation start time, as well as the invocation's status, type, and tagger version. Results may be accessed from the invocation's ( ⋮ ) context menu.

Within the invocation results modal, the status of various invocation stages are shown for each robolog included in the invocation.

Reminder: Our platform considers a test successful if the invocation did not fail at runtime, and the invocation's status will reflect that. You should verify whether or not the successful test invocation produced the metadata values you expected, taking into consideration the tagger definition and robologs used in the test invocation.

Next steps

Once you have successfully tested at least one version of your tagger, you may enable it for normfill invocations. Proceed to the next section to learn more about what it means to enable your tagger for event autotagging on ingest.