Viewing Enforcement Set Run History
  • 06 Feb 2024
  • 10 Minutes to read
  • Dark
    Light
  • PDF

Viewing Enforcement Set Run History

  • Dark
    Light
  • PDF

Article Summary

On the Run History page, you can view the results of all runs of Enforcement Sets defined in Axonius or of a single Enforcement Set.

Viewing the Run History of All Enforcement Sets

From the Enforcement Sets page, you can open the Run History page of all enforcement sets, in the same tab or in a new tab. When you open it in the same tab, you can use the Back arrow to return to the Enforcement Sets page.

To view the run history of all Enforcement Sets

RunHistoryButton

Viewing the Run History of a Simple Enforcement Set

To view the runs of a simple (one-action) Enforcement Set

  1. In the Enforcement Sets table in the Enforcement Sets page, click a one-action Enforcement Set.
  2. In the header of the Edit Enforcement Set drawer that opens, click the Run History icon. The Run History page opens, displaying the runs of the selected one-action Enforcement Set.
    EditECHeader

Viewing the Run History of a Complex Enforcement Set

To view the runs of a complex (multi-action) Enforcement Set

  1. In the Enforcement Sets table in the Enforcement Sets page, click a multi-action Enforcement Set.
  2. In The Enforcement Set's configuration summary page that opens, in the upper-right corner, click View Runs. The Run History - Enforcement Sets tab opens, displaying the runs of the selected multi-action Enforcement Set. The name of the selected Enforcement Name appears in the filter. You can select other Enforcement Sets from this dropdown to show their run history as well.

EC-ViewRuns

The Run History Page

The Run History page displays a list of runs of all Enforcement Sets or of a selected Enforcement Set and allows you to investigate the results of each run.

RunHistoryEnforcementSets

The Run History page consists of the following main elements:

  • Search/Filter bar
  • Run History table
  • Total Runs performed
  • The Actions menu

Run History Table

The Run History table displays a list of Enforcement Set runs, with one row representing each run.
You can expand a multi-action row in the Run History table to display one row per action and view information on each action.
The Run History table includes the following fields, by default, for each Enforcement Set, and where relevant, for each Enforcement Action within the Enforcement Set:

  • Actions - The icons indicate the type of actions configured in the Enforcement Set. You can click the Down arrow in front of a multi-action run to expand it to view information on each action in the run.
  • Run - The ID number of the run. For each action, shows the name of the Enforcement Action.
  • Enforcement Name – The Enforcement Set name.
  • Trigger Type - The type of trigger that caused the Enforcement Set to run:
  • Result - Shows the run results: Completed, Failed, In Progress, Partially, Pending, Delayed, or Terminated.
  • Query Name – The saved query that determines on which assets the Enforcement Set is run.
  • Start Time – The start date and time of the run.
  • End Time – The end date and time of the run.
  • Duration - The calculated total fetch duration in HH:MM:SS.ss format.
  • Affected Assets - The total number of assets that match the query.
  • Success – The number of assets on which the Enforcement Actions ran successfully.
  • Failed - The number of assets on which the Enforcement Actions did not run successfully.
  • Discovery Cycle - The identifier of the discovery cycle in which the activity occurred. This is presented as the start date and time of the discovery cycle.

Viewing Detailed Run Information and the Enforcement Set Configuration

On the Run History page, you can click any Enforcement Set run (row) to open the Run drawer with a tab for each of its Enforcement Actions. Clicking a tab shows detailed information about the Enforcement Action run, as well as its configuration.
You can click the Enforcement Center EC_Icon icon in the header of the Run drawer to open the detailed configuration of the Enforcement Set.

The following Run Drawer presents the run details and configuration of the main Enforcement Action in the Enforcement Set. You can click the other tab to present the other Enforcement Action's run details.

ECSetRunResultsDrawer-1.png

The following Run Drawer presents the run details of the single Enforcement Action in the Enforcement Set, and with an Additional count under Affected Assets.

EC_Run_AdditionalAction1

At the top of each tab, the following information is shown:

  • Started, Ended - Start and end date and time of the run.
  • Type - Whether the selected Enforcement Action is the Main action, Success action, Failure action, or Post action.
  • Result - Whether the run Completed successfully, Failed, is In Progress, Partially completed, is Pending, Delayed, or Terminated.
  • Affected Assets - The number of assets affected by the run:
    • Successful - The number of assets on which the Enforcement Set ran successfully. Click the number link to pivot to the Assets page with a list of these assets. Under the EC: Result Details column is displayed RunHistoryResultSuccess.

    • Failed - The number of assets on which the Enforcement Set run failed. Click the number link to pivot to the Assets page with a list of these assets. Under the EC: Result Details column is displayed the beginning of the error message. Hovering over the field displays the full error message. For example, RunHistoryResultFailure

Note:

The number of Affected Assets (Succesful and Failed) is calculated at the end of a run. When some time after the run, you pivot from the Successful number link in the Run drawer to the Assets page, it could be that the number of reported Successful assets will be lower or higher than the actual number of assets on the Assets page. Similarly for Failed assets. This difference is due to assets constantly being correlated and deleted in the system over time. If you want to display on the Assets page all Successful or Failed assets that existed at the time of the run, you can change Display by Date on the Assets page to the date of the run.

Note:
  • When using Custom Enrichment - Enrich assets with CSV file enforcement action to Add custom enrichment to assets, those assets which are returned by the query but do not match the Custom Enrichment statement, are not enriched, and are therefore included in the Failed assets count.

  • When using Custom Enrichment - Enrich assets with CSV file enforcement action to Remove custom enrichment from assets:

    • Those assets which are returned by the query and do not have custom enrichment even before running the action, are included in the Successful assets count.
    • Those assets which are returned by the query and have custom enrichment, but match the Custom Enrichment statement and therefore their custom enrichment is removed, are included in the Successful assets count.
    • Those assets which are returned by the query and have custom enrichment, but do not match the Custom Enrichment statement and therefore remain with their custom enrichment (not removed), are included in the Failed assets count.

* Additional - The number of assets on which other actions were performed, when Remove this tag from entities not found in the saved query results is selected on either Axonius - Add Custom Data to Assets or Axonius - Add and Remove Tag. Click the number to see a list of these assets.

When an Enforcement Action runs one time on an entire pool (e.g., send a single email or create a single ticket for all assets returned from a query), if the action results in an error, the Run Error is displayed in the drawer.
RunErrorinDrawer

When an Enforcement Action runs asset-by-asset (e.g., tag, custom data, ticket per asset), the error never appears in the drawer as it is per asset (some may succeed while others fail). It is accessible by clicking the Failed assets link in the drawer to open the Assets page with the assets that failed in the run (see EC Result Details in the first screen below), and then clicking an individual failed asset from that page and opening its Enforcement Runs tab to view the detailed error in the Additional Info column (second screen below).
RunErrorAssetsPage

RunErrorIndividual

Note:

You can also view detailed information about each Enforcement Action run (but not its Additional affected assets, and without the configuration summary) directly from the Run History table by expanding the Enforcement Set Run row (click the Down arrow to the left of the Actions column) to show its Enforcement Actions.

Viewing Run History of an Asset

In the Run Drawer, you can click the number of Success, Failed, or Additional assets to open the list of relevant assets. (You can also click the number of Success or Failed (but not Additional) assets in the Enforcement Action row on the Run History page to open the list of assets). You can then click any asset record, and in the page that opens, click the Enforcement Runs tab to see the history of all enforcement runs on this asset. To learn more, see Asset Profile Page.

Filtering the Run History Table

You can filter the Run History table by selecting from the following lists:

  • Search runs - Free-text search on all text fields.
  • Enforcement Name - Filters the list by Enforcement Set name.
  • Action Name - Filters the list by the Enforcement Action and lists all Enforcement Sets that include that Enforcement Action.
  • Result - Filters by the result of the Enforcement Action run:
    • Completed - Shows all Enforcement Set runs that have finished.
    • Failed - Shows all Enforcement Sets where all Actions failed.
    • In Progress - Shows all Enforcement Sets that are still running.
    • Delayed - Shows all Enforcement Sets where an action (post, success, or failure) is configured to run at a later time.
    • Partially - Shows all Enforcement Sets where at least one action (but not all) failed.
    • Pending - Shows all Enforcement Sets that are queued to run.
    • Terminated - Shows a list of all Enforcement Sets whose run was terminated.
  • Start time, End time - Filters by the date that the Enforcement Action was run.
  • Duration - From the dropdown, select an operator (Equal to, Greater than, or Less than) and enter the time duration (in HH:MM:SS.ss) format) that you want to filter.
    • To set fractional seconds, highlight ss and enter a number up to 99.
    • To set seconds, highlight SS and enter a number up to 59.
    • To set minutes, highlight MM and enter a number up to 59.
    • To set hours, highlight HH and enter a number up to 99.

SelectOperator

Note:

It can be very useful to filter the Run History table by Duration to view all the runs that were lengthier than expected. These "bad" runs can then be examined to check out if there is a problem, and if yes, attempt to resolve it.

  • Discovery Cycle - Display only Enforcement Set runs from a specific Discovery Cycle, or Cycles.

The total number of Enforcement Set runs that match the search criteria is displayed on the top left side of the Run History table just under the Filter bar. When no search criteria is selected, the total results represent the total number of runs.

ECRunHistory-TotalRuns.png

Filtering by Enforcement Set Name

In the Enforcement Name search box, type all or part of the Enforcement Set name, and then from the resulting list of Enforcement Sets containing the searched string, select the relevant Enforcement Set name.

EC_Enforcement_Name_Dropdown



Was this article helpful?

Changing your password will log you out immediately. Use the new password to log back in.
First name must have atleast 2 characters. Numbers and special characters are not allowed.
Last name must have atleast 1 characters. Numbers and special characters are not allowed.
Enter a valid email
Enter a valid password
Your profile has been successfully updated.