Documentation for Axxon Next 4.3.5. Documentation for other versions of Axxon Next is available too.

Previous page The System Log  Event search procedure Next page

Skip to end of metadata
Go to start of metadata

To view and/or export system log events, first you need to perform a search for them.

To search for system log events, you need to set one or more filters:

  1. Time period during which the events were recorded.
  2. Event type:
    1. Information;
    2. Alarm;
    3. Error;
    4. Debug;
    5. Audit - user actions log.

  3. A key phrase contained in the system event descriptions.


The time period is a mandatory filter, while the event type and key phrase are optional.

Search filters can be set as follows:

  1. In the To and From fields (1) you can enter the date and time of the beginning and end of the period during which the events you are searching for were recorded.


    The date format is DD-MM-YYYY and the time format is HH:MM:SS.XXX.


    By default, the event search period is defined as the past 24 hours.
  2. Selecting event types for search (2). 

  3. Select the Axxon domain where you need to search for events (3).

  4. If user actions search was selected (the Audit type), choose a particular system user (4). If no user is selected, the search function will return actions of all system users.

  5. Enter the text that matches the events you want to find in the Search Text field (5). To find license plate numbers, enter the full or partial number.  Use ? (any one character) and *  (any number of any characters). For example, a search query ?20* shows all vehicles with a license plate containing 2 and 0 in the second and third position respectively. The total number of characters in number plates can be arbitrary.


You can use OR and AND logical operators when searching data in the system log.

- to search with the OR logical operator, separate the words with the symbol "|";

- to search with the AND logical operator, use a space.

The event search filters have been set.

Next you must start the event search (see the section titled Event search procedure).