System Log

The System Log provides an audit trail of actions performed within INTERA.

It allows administrators to see what happened in the system, when it happened, which INTERA object was involved, who or what initiated the action, and whether the operation was successful.

The System Log is particularly useful for answering questions such as:

• Did this Metric synchronize?
• Did an Asset Type collection run?
• When did the operation happen?
• Was it initiated by a user or automatically by INTERA?
• Did it succeed or fail?
• Which INTERA object was affected?

The System Log is available under:

Settings → System → System Log

What the System Log Records

INTERA records system actions that are useful for administration, troubleshooting and understanding automated activity.

Examples include:

• scheduled Metric synchronization;
• Asset Type synchronization;
• scheduled Collection Source runs;
• other system and user actions recorded by INTERA.

For example, a scheduled Metric update may appear as:

Sync · Metric · system · Success

with a summary identifying the Metric that was synchronized.

A scheduled collection may appear as:

Sync · Asset type · system · Success

with the Collection Source identified in the summary.

Log Information

Each System Log entry contains several pieces of information.

Time

The date and time when the action occurred.

Action

The operation that took place, such as:

Sync

Entity Type

The type of INTERA object affected by the action.

Examples include:

• Metric;
• Asset Type.

Entity ID

The unique INTERA identifier of the affected object.

This is primarily useful for administration and technical troubleshooting when objects have similar names or the original object is no longer immediately identifiable.

Actor

Shows who or what initiated the action.

For automatically scheduled operations, the actor is shown as:

system

Actions initiated by users can be associated with the corresponding actor where applicable.

Status

Shows the result of the operation.

For example:

Success

The status makes it possible to quickly distinguish normal system activity from operations that require investigation.

Summary

Provides a human-readable explanation of what happened.

For example:

Scheduled metric sync "zabbix-server-enigma-online"

or:

Scheduled collection source run (SCF-gsheet-telecom · Google Sheets rows)

The summary is normally the quickest way to understand a log entry without opening its technical details.

Viewing Details

Select Details on a System Log entry to inspect additional information about that specific action.

This is useful when the summary identifies a problem but more information is required to understand the operation.

Selecting a Time Period

System activity can become extensive, particularly when INTERA contains Metrics and Asset Types that synchronize frequently.

The System Log therefore allows administrators to select the period they want to inspect using:

• Day
• From
• To

For example, if a value appears incorrect at 14:30, an administrator can examine the System Log around that time rather than searching through all historical activity.

Search and Filters

The System Log includes Search and Filters controls to help narrow the activity being investigated.

This becomes particularly useful in installations with many Metrics, Assets, Integrations and scheduled synchronization jobs.

A typical investigation might start by selecting a narrow time window and then searching for the affected Metric or other object.

System Actions and User Actions

Not every action in INTERA is performed directly by a person.

Many INTERA operations happen automatically according to configured schedules.

The Actor field helps distinguish between these cases.

For example:

Actor: system

indicates an operation performed automatically by INTERA.

This is useful when determining whether a change or synchronization resulted from normal scheduled processing or from a user action.

System Log and Troubleshooting

The System Log should normally be one of the first places an administrator checks when information in INTERA has not updated as expected.

For example, if a Metric appears stale:

1. identify the affected Metric;
2. open Settings → System → System Log;
3. select the relevant time period;
4. search for the Metric;
5. check whether its synchronization ran;
6. check the status of the operation;
7. open Details if further information is required.

This helps distinguish between:

• an operation that never ran;
• an operation that ran successfully;
• an operation that ran but failed;
• a problem elsewhere in the data flow.

System Log Versus Metric History

The System Log records what INTERA did.

Metric history records what values a Metric had over time.

These are different types of history.

For example:

Metric history

12:00 → 84
13:00 → 87
14:00 → 91

answers:

What was the Metric value?

The System Log answers:

When did INTERA synchronize the Metric, who initiated the operation, and did it succeed?

Both can be useful when investigating an unexpected result.