Logs
On this page
Alloy Navigator keeps a log for each of its background tools and for several kinds of events. A tool log holds one row per run of a tool, such as one Mail Connector session or one scheduled-report run. The other logs are written by the product itself: the System Log, the workflow log, the user session log, the deleted objects log, and the SSP search log. Each log keeps its records for a number of days, and the Automation Server removes older records once a day.
You read logs in the Settings App and in the Admin Center. The System Log and its alerts have their own page: System Log and Alerts.
Log types
| Log | One row records | Read in | Kept by default |
|---|---|---|---|
| Incoming Mail | A Mail Connector session: records created and updated, messages received, messages in the inbox, errors | Settings App, Admin Center | 30 days |
| Outgoing Notifications | A pass over the notification queue: total, succeeded, errors, e-mail or push | Settings App, Admin Center | 30 days |
| AD Synchronization | An Active Directory import session: total, created, updated, errors | Settings App, Admin Center | 30 days |
| Discovery Synchronization | An Alloy Discovery synchronization: computers created, conflicts, errors | Settings App, Admin Center | 30 days |
| AlloyScan | An AlloyScan synchronization session | Settings App, Admin Center | 30 days |
| Archiving | An archiving run: archive database, objects, errors | Settings App, Admin Center | 30 days |
| Reporting | A scheduled-report run: report name, output file, errors | Settings App, Admin Center | 30 days |
| Scheduled Tasks | A run of the Scheduled Task Agent | Settings App, Admin Center | 30 days |
| On Condition Triggers | A condition-checking session | Settings App, Admin Center | 30 days |
| Recurrent Tickets | A recurring-ticket session | Settings App, Admin Center | 30 days |
| SSP AI Assistant | A conversation with the AI assistant of the Self Service Portal, with the knowledge base searches the assistant ran during it | Admin Center only | 7 days |
| System Log (All Errors) | An error event from any component; a repeated event is counted in its existing row | Settings App, Admin Center | 30 days |
| Workflow | One execution of a workflow item, with its operations and e-mails | Settings App, Admin Center | 7 days |
| User Sessions | A finished session: login, IP address, module, times, concurrent and named counts | Settings App, Admin Center | 30 days |
| Deleted Objects | A deleted object: class, ID, name, date, who deleted it, Alloy login and SQL login | Settings App, Admin Center | 999 days |
| SSP Search | A portal search: date, person or Anonymous User, scope, search text, number of results |
Settings App, Admin Center | 30 days |
What a tool log holds
The logs from Incoming Mail to Recurrent Tickets are tool logs. Besides its counters, each row carries the text the tool wrote during the run. The text starts with the tool's command line, with every argument that carries a password or a key removed, followed by the tool's version and build; the Outgoing Notifications log has no such header. A run that produced nothing is not kept, and neither is a connection-test run that succeeded.
Tools write their logs through the Alloy Logging Engine, which is installed
separately into Common Files\Alloy Shared\LoggingEngine\. When a tool cannot
find it, the tool counts the engine as not installed; the archiving tool, for
one, then stops with exit code 6 and "Alloy Logging Engine is not installed or
its installation is corrupted."
Job history
A job's history, shown in the history dialog of the job, is not one of these logs. No retention setting applies to it and the daily purge does not trim it; Clear All in the history dialog empties it, and deleting the job removes it too. The dialog lists only runs that succeeded or failed.
Runs do not add records to a job's history, so the dialog shows only records left by earlier versions, if any. To see a job's runs, use the Sessions tab of the job and the job's log under Logs.
What you can see and change
In the Settings App, two administrative rights control the Logs branch. In the role editor, both are under Administrative Access > Log Management:
| Right | What it allows |
|---|---|
| Browse | See the log nodes under Logs. |
| Manage | See Alerts under All Errors, change a log's retention, and delete or clear records in the tool logs and the SSP Search log. |
Either right opens the Logs branch. Without Manage, the tool logs and the SSP Search log open read-only: Delete, Clear All, and Settings... are not offered. For the Error Log, see System Log and Alerts. Where Settings... is offered to an account without Manage, it answers "You do not have enough permissions to use this function." For the rights themselves, see Permissions Reference.
The Logs node of a service branch takes the right of that branch instead, so an administrator who may configure a service reaches its log without a Log Management right.
In the Admin Center, the Logs section needs the Log Management permission or one of its two sub-permissions, Browse and Manage; a menu entry is also subject to the menu's other checks. On a log's page, Clear All, Delete, and Settings... appear only when your account holds Log Management or Manage, and only on the log pages that provide these commands; Browse alone does not show them. An account with Administrative Access passes all of these permission checks.
Logs in the Settings App
Find a log
The Logs branch has a node for each log, in this order: AD Synchronization, Archiving, Deleted Objects, Discovery Synchronization, AlloyScan, Incoming Mail, On Condition Triggers, Outgoing Notifications, Recurrent Tickets, Reporting, Scheduled Tasks, User Sessions, SSP Search, and Workflow. Then comes All Errors, with Error Log (the System Log) and Alerts under it.
Workflow opens the workflow manager. All Errors itself is a grouping node. Every other node opens the Log Manager, where the ten tool logs share one Logs page.
Eight service branches also have a Logs node that opens the same log as its twin under Logs:
- Notifications > Logs (the Outgoing Notifications log)
- E-mail Processing > Logs
- Under Services: Active Directory Integration, Alloy Discovery Integration, AlloyScan, Archiving, Scheduled Reports, and Scheduled Tasks, each with its own Logs node
In Alloy Navigator Cloud and on Azure SQL, the Archiving branch, with its Logs node, is not shown; see Administering Alloy Navigator Cloud.
The window of a job also has a Sessions tab that lists the log rows of that job; Settings... is not offered there. A Trigger on Condition has sessions only while its condition is checked on a schedule, with Every n minute(s) or Use advanced schedule; for After the object has been saved, the trigger window hides its Sessions tab. In the On Condition Triggers log, the trigger name reads the workflow object's name, the word Trigger, and then the item number and the trigger's name in parentheses. Logs without a job window of their own, such as Outgoing Notifications, are read from their nodes in the tree only.
Work with a log
A log shows its newest records, at most 1,000, and says "Last <n> records are loaded". While its page is on screen, it checks for new records every 10 seconds by default.
- Open a record. Enter or a double-click opens the selected row, as does
the log's open command: View Log in a tool log and in the SSP Search log,
and View Details in the Deleted Objects, User Sessions, Error Log, and
workflow logs. For a tool log, the run's text is saved
as a
.logfile in the product's temporary folder and opened in the program Windows uses for.logfiles; opening the same run again reopens that file. When the record no longer exists, the tool log reports "The log file is currently unavailable." When the record exists but holds no text, it reports "The '<key>.log' file can't be accessed from this computer.", where <key> is the key of the log record. The Deleted Objects, Workflow, SSP Search, and Error Log logs open a details window instead (see Details windows). - Delete. Removes the selected records after confirmation. If a record cannot be deleted and others remain, the log shows the error and asks whether to continue with the remaining records.
- Clear All. Removes every entry in the log after confirmation, independently of the daily purge.
- Settings... changes the log's retention; see Set how long a log keeps records.
- Refresh, or F5, reloads the log at once.
When a log is too large to load in time, it shows its number of records instead, and Clear All stays available, even when the log is read-only for you.
To export records, right-click a row and use View > Export Rows > Export All or Export Selected, in MS Excel Format, HTML Web Page, XML Format, or ASCII Text File Format; Analyze with MS Excel is next to them. The Log Manager's Export Log... exports the System Log's alert definitions, not log records.
Details windows
- Deleted Objects opens the Deleted Object window. Its Object group shows Class:, ID:, and Name:, and its Deleted group Date:, Technician:, Alloy Login:, and SQL Login:. Nothing in it can be edited. < and > move to the previous and next row, each available only while there is such a row, and Close closes it.
- Workflow opens a window captioned with the item's name and number
followed by " - Log Entry Details". It shows Run Date:, Item Name:,
Object ID:, Event:, Triggered by Action:, Initiator Name:,
Initiator Type:, Host:, and Status:, which reads Succeed or
Failed, or shows the result code as a number for any other result.
Item Name: shows the item's name and number, followed by ", Generic
item" when the item belongs to a general, class-independent workflow object.
Object ID: shows the object's ID and class,
<deleted>in place of an ID the record no longer carries, and no ID for PO items, vendor products, and approval requests. Triggered by Action: shows the action's name and ID, and is blank when the record names no action. Operations: lists the operations of the run with Operation and Description; selecting one fills Operation Details: with Parameter and Value. When the status is anything but Succeed, the status turns red and an Error Message: panel appears. < and > step through the rows, and Go to Item opens the workflow manager at that item. - SSP Search opens SSP Search Log Record with Search Date:, Person Name:, Search Scope:, Search Text:, and Result Count:, read-only. < and > step through the rows without closing it.
- Error Log opens the Error Log Record window; see System Log and Alerts.
The SSP Search log
The SSP Search log lists the search date, the person's name, the search scope, the search text, and the number of results.
The Self Service Portal adds a record once a search reads its results, whether the search was typed in the portal's search box or run by the search tool of the portal's AI chat. The record carries the search text and the number of results that belong to the portal's enabled modules, and its scope reads All. A search that ends before it reads its results, for example because no data came back for it, is not recorded. Filtering a list in the portal, such as with Filter items (/) in the service catalog, is not a search and adds no record.
The log's toolbar holds, in this order, the view selector, View Log, Clear All, Refresh, a delete button, Settings..., and a quick-filter box. The view selector shows the current view's name; its list offers the views and then Save Current View, Save View As..., and Customize View.... Records are never added or edited here. View Log and Clear All are available only while a record row, not a group row, is selected.
This log uses its own questions: "Are you sure you want to delete the selected item?" or "Are you sure you want to delete <n> selected items?" for Delete, and "You are about to delete all entries from the SSP Search Log. Are you sure you want to proceed?" for Clear All. When the log is read-only for you, the toolbar's delete button is hidden, and Delete Selected Item(s) in the right-click menu stays visible but unavailable. When the log is too large to load, it reports "Unable to refresh the view because the log contains too many records (<n>). Delete some records and try again."
Set how long a log keeps records
You need the Manage right.
- In the log, click Settings....
- In the Settings dialog, under Retention Policy, set Remove records older than to a number of day(s) from 1 to 999.
- Click OK.
OK saves the value and tells the Automation Server to reload its settings, so the daily purge uses the new number without a restart.
- A tool log has its own value. The dialog opens on that value, or on the common value for tool logs when the log has none of its own, and always saves the log's own value, so changing one tool log never changes another.
- The Error Log, the workflow log, and the SSP Search log each have their own value.
- The User Sessions log and the Deleted Objects log each have their own value too, and offer the same Settings... command and Settings dialog.
The workflow log's Settings dialog also holds Enable workflow logging and, under it, Log only failed executions. Both are on by default. When workflow logging is off, Log only failed executions and the retention box are unavailable.
In Alloy Navigator Cloud, the retention box is unavailable, and so is Log only failed executions in the workflow log's dialog; see Retention in Alloy Navigator Cloud.
Logs in the Admin Center
Find a log
The Admin Center's Logs page shows a tile per log: AD Synchronization, Archiving, Deleted Objects, Discovery Synchronization, AlloyScan, Incoming Mail, On Condition Triggers, Outgoing Notifications, Recurrent Tickets, Reporting, Scheduled Tasks, User Sessions, SSP AI Assistant, SSP Search, Workflow, and All Errors. The same list drives the menu. In Alloy Navigator Cloud, the Archiving tile and its menu entry are hidden.
The SSP AI Assistant log is shown only in the Admin Center. It holds the conversations of the Self Service Portal's AI assistant, one row per conversation. A conversation opens in SSP AI Assistant Log Details, with the tabs Chat and Relevant Search. Relevant Search lists the knowledge base searches the assistant ran during that conversation, with Search Date, Results, and Has Error; each search records the query, the models used, and the articles found with their relevance, and its details open in Vector Search Log Details.
A job's log can also be reached from its service page. A job's form ends on a Sessions tab once the job exists, and the job pages have a Logs page beside the job list. The Alloy Discovery Integration page has Logs as one of its top-level tabs.
Work with a log
A log's page, such as Workflow or Deleted Objects, has View Log, Clear All, Delete, and Settings... on its toolbar, with the management commands shown only as described in What you can see and change.
- Delete asks "Are you sure you want to delete the selected item?" or "Are you sure you want to delete <n> selected items?".
- Clear All asks one Yes or No question before it removes the entries.
Set how long a log keeps records
A log's settings form in the Admin Center holds its retention. The forms store the same values as the Settings App. You need Log Management or Manage; see What you can see and change.
Every log page except Workflow has the same Settings panel, including Error Log under All Errors. The Alerts page under All Errors has no Settings....
- On the Logs page, open the log.
- Click Settings....
- In the Settings panel, under Retention Policy, set Remove records older than to a number of day(s) from 1 to 999.
- Click Ok.
The box shows no message for a value out of range. When you leave it, an empty box or 0 becomes 1, and a number above 999 becomes 999; letters are not accepted. When a log has no stored value of its own, the panel shows 30 days, except 999 days for Deleted Objects and 7 days for SSP AI Assistant.
The SSP AI Assistant page and the Relevant Search tab of a conversation offer Settings... too, with 7 days when nothing is stored.
For the workflow log:
- On the Logs page, open Workflow.
- Click Settings....
- In the Settings panel, select or clear Enable workflow logging and Log only failed execution, and under Retention Policy set Remove records older than to a number of day(s).
- Click Ok.
As in the Settings App, when Enable workflow logging is cleared, Log only failed execution and the retention box are unavailable.
In Alloy Navigator Cloud, these forms show fixed values; see Retention in Alloy Navigator Cloud.
How retention is applied
The Automation Server removes old records once a day. Cleanup covers workflow, system, and tool logs, user sessions, deleted objects, the SSP Search log, and SSP AI Assistant conversations and their associated searches.
- Retention is applied only while the Automation Server runs as the active node. While the Automation Server is stopped, the daily purge removes nothing.
- A tool-log record marked as critical is never removed. Outside the System Log, a record that is locked at that moment is skipped.
- A user session that has no logout time is never removed.
- The Outgoing Notifications retention period also removes failed e-mail from the queue and old delivered push notifications.
- If cleanup fails, the error is recorded in the System Log and cleanup stops.
You can also remove records manually with Clear All in a log.
Retention in Alloy Navigator Cloud
In Alloy Navigator Cloud, the Admin Center fixes log retention, and the Settings App does not let you change it:
- In the Admin Center, most logs' settings forms show 30 days with the retention box unavailable. The SSP AI Assistant and its searches show 7 days. The workflow log's settings form shows 7 days with Log only failed execution selected, both unavailable, while Enable workflow logging stays available. Saving stores 7 days and failed executions only for the workflow log, 7 days for the SSP AI Assistant and its searches, and 30 days for the other logs.
- The Settings App shows the retention box unavailable, with the stored value. In the workflow log's Settings dialog, Log only failed executions is unavailable too, while Enable workflow logging stays available; OK keeps the stored values of the unavailable controls.
See Administering Alloy Navigator Cloud.