User Guide Functional Overview Requirements Architecture System Installation NetEye Additional Components Installation Setup The neteye Command Director NetEye Self Monitoring Tornado Business Service Monitoring IT Operation Analytics - Telemetry Geo Maps NagVis Audit Log Shutdown Manager Reporting ntopng Visual Monitoring with Alyvix Elastic Stack IT Operations (Command Orchestrator) Asset Management Service Level Management Cyber Threat Intelligence - SATAYO NetEye Update & Upgrade How To NetEye Extension Packs Troubleshooting Security Policy Glossary
module icon Audit Log
Director NetEye Self Monitoring Tornado Business Service Monitoring IT Operation Analytics - Telemetry Geo Maps NagVis Audit Log Shutdown Manager Reporting Introduction to NetEye Monitoring Business Service Monitoring IT Operation Analytics Visualization Network Visibility Log Management & Security Orchestrated Datacenter Shutdown Application Performance Monitoring User Experience Service Management Service Level Management & Reporting Requirements for a Node Cluster Requirements and Best Practices NetEye Satellite Requirements TCP and UDP Ports Requirements Additional Software Installation Introduction Single Node Cluster NetEye Master Master-Satellite Architecture Underlying Operating System Acquiring NetEye ISO Image Installing ISO Image Single Nodes and Satellites Cluster Nodes Configuration of Tenants Satellite Nodes Only Nodes behind a Proxy Additional NetEye Components Single Node Cluster Node Satellites Nodes only Verify if a module is running correctly Accessing the New Module Cluster Satellite Security Identity and Access Management External Identity Providers Configure federated LDAP/AD Emergency Reset of Keycloak Configuration Advanced Configuration Authorization Resources Tuning Advanced Topics Basic Concepts & Usage Advanced Topics Monitoring Environment Templates Monitored Objects Import Monitored Objects Data Fields Deployment Icinga 2 Agents Configuration Baskets Dashboard Monitoring Status VMD Permissions Notifications Jobs API Configuring Icinga Monitoring Retention Policy NetEye Self Monitoring 3b Concepts Collecting Events Add a Filter Node WHERE Conditions Iterating over Event fields Retrieving Payload of an Event Extract Variables Create a Rule Tornado Actions Test your Configuration Export and Import Configuration Example Under the hood Development Retry Strategy Configuration Thread Pool Configuration API Reference Configure a new Business Process Create your first Business Process Node Importing Processes Operators The ITOA Module Configuring User Permissions Telegraf Metrics in NetEye Telegraf Configuration Telegraf on Monitored Hosts Visualizing Dashboards Customizing Performance Graph The NetEye Geo Map Visualizer Map Viewer Configuring Geo Maps NagVis 3b Audit Log 3b Overview Shutdown Manager user Shutdown Manager GUI Shutdown Commands Advanced Topics Overview User Role Management Cube Use Cases ntopng and NetEye Integration Permissions Retention Advanced Topics Overview User Roles Nodes Test Cases Dashboard Use Cases Overview Architecture Authorization Elasticsearch Overview Enabling El Proxy Sending custom logs to El Proxy Configuration files Commands Elasticsearch Templates and Retentions El Proxy DLQ Blockchain Verification Handling Blockchain Corruptions El Proxy Metrics El Proxy Security El Proxy REST Endpoints Agents Logstash Elastic APM Elastic RUM Log Manager - Deprecated Overview Authorization in the Command Orchestrator Module Configuring CLI Commands Executing Commands Overview Permissions Installation Single Tenancy Multitenancy Communication through a Satellite Asset collection methods Display asset information in monitoring host page Overview Customers Availability Event Adjustment Outages Resource Advanced Topics Introduction Getting Started SATAYO Items Settings Managed Service Mitre Attack Coverage Changelog Before you start Update Procedure Single Node Upgrade from 4.41 to 4.42 Cluster Upgrade from 4.41 to 4.42 Satellite Upgrade from 4.41 to 4.42 DPO machine Upgrade from 4.41 to 4.42 Create a mirror of the RPM repository Sprint Releases Feature Troubleshooting Tornado Networking Service Management - Incident Response IT Operation Analytics - Telemetry Identity Provider (IdP) Configuration Introduction to NEP Getting Started with NEPs Online Resources Obtaining NEP Insights Available Packages Advanced Topics Upgrade to NetEye 4.31 Setup Configure swappiness Restarting Stopped Services Enable stack traces in web UI How to access standard logs Director does not deploy when services assigned to a host have the same name How to enable/disable debug logging Activate Debug Logging for Tornado Modules/Services do not start Sync Rule fails when trying to recreate Icinga object How to disable InfluxDB query logging Managing an Elasticsearch Cluster with a Full Disk Some logs are not indexed in Elasticsearch Elasticsearch is not functioning properly Reporting: Error when opening a report Debugging Logstash file input filter Bugfix Policy Reporting Vulnerabilities Glossary 3b

Audit Log

Audit Log Introduction

The Audit Log allows administrators to look back at changes that have been made to NetEye. This is useful should you need to troubleshoot a problem, or if you need to keep a record of important events, such as changes to global permissions.

The Audit Log module centrally records information about events such as the creation, modification, deletion or deployment of module objects for all those modules that implement an object structure that is compatible with this module.

To view the Audit Log, select System / Audit Log.

Features

The Audit Log makes (compatible) configuration changes persistent in a database, including:

  • An ID of the modified object

  • The user that made the change

  • The type of action (Create, Modify, Delete and Deploy*)

  • The type of object that was changed

  • A copy of the new object (for Create and Modify)

  • The module that originated the change

  • The time and date the change was made

Audit Log can also show the differences between the previous and new versions of an object in a separate panel.

NetEye’s permissions system allows administrators to restrict Audit Log viewing rights based on the Roles belonging to a NetEye user and their groups. By default, users can only see their own changes. If an administrator adds the role Allow viewing of all logs in Activity Log, then that user can see changes made by all users.

The Audit Log View

The main Audit Log View displays a table where each row is a change to an object. Changes are grouped by the day of the change, and divided into pages.

The controls above the table allow you to quickly navigate between the pages and to filter changes according to:

  • Changes made by the current user (“My changes”)

  • The user account that made that change (if the viewer is an administrative user)

  • The module that the change was made in

  • The date on which the change was made (via the “Select date” date picker widget)

Clicking on the linked object in a row will take you to the configuration panel for that object. Clicking anywhere else on a row will take you to the Difference View panel described below.

You can configure the number of rows displayed per page by changing the “Default page size” option under the My Account tab available from the “gear” settings icon at the bottom left of the browser window.

The Difference View Panel

The Difference View panel shows a brief summary of the recorded information (author, date, action and checksum) and both the old and new objects in a side-by-side diff format.

The Audit Log Retention Policy

The Audit Log Retention policy defines the amount o time Logs will be stored. This should prevent the database from continuous increase with new entries being added. By default the retention policy is set to 365 days. You can change the parameter in Configuration / Modules / Auditlog / Configuration or manually in the file /neteye/shared/icingaweb2/conf/modules/auditlog/config.ini. Setting Retention policy to 0 days will keep the logs stored for an infinite period of time or until the parameter is set to a different value.

The Audit Log Database Structure

The Audit Log module relies on a simple but secure database structure that ensures log integrity.

The following diagram shows the structure of the Audit Log database, where id is the primary key.

Table 13 Audit Log Database Structure (audit_log)

Field

Type

Description

id

bigint(20)

The primary, unique key that distinguishes an Audit Log record from the others.

module_name

varchar(64)

The name of the module (Log Manager, Geo Map, etc.) that originated the action.

obj_type

varchar(64)

The type of the object subjected to the action.

obj_name

varchar(255)

The name of the object.

action_name

varchar(255)

The type of action performed by the user (create, modify, delete or deploy).

old_properties

text

A complete copy of the properties of the object before the update.

new_properties

text

The object’s new properties after the update.

user

varchar(64)

The user name of the user who performed the action.

url

varchar(255)”

A URL pointing to the object (the old object for a delete action, the new object for an add action, etc.)

message

text

An optional field containing a custom message (potentially including HTML markup) that replaces the action, object type, and URL fields shown in the table row.

change_time

timestamp

The Unix timestamp when the action was performed.

checksum

varbinary(20)

The chained SHA-1 value calculated from all the other fields in this database row, including the parent checksum.

parent_checksum

varbinary(20)

The SHA-1 checksum of the previous row in the table (the action before this one), used to create the chained checksum.
Blog Online Demo Training
Contact Us
© 2025, Wuerth Phoenix S.r.l.
VAT ID 01054690217
Privacy Cookies