K2View’s auditing capability is now available to K2Cloud SaaS customers. This feature offers detailed visibility into user and system activity across Fabric.
Note: Customers using self-hosted K2Cloud environments are not eligible for this capability.
Auditing is particularly useful in production environments, where system integrity, accountability, and regulatory compliance are essential. Enabling auditing ensures that user actions and system events are accurately recorded for analysis, compliance, and troubleshooting purposes.
Here’s a list of common activities audited in production:
Auditing is not recommended in development environments, particularly when using Fabric Web Studio.
Why?
In development environments, Fabric Web Studio often executes actions on behalf of the user. If auditing is enabled:
Recommendation:
Do not enable auditing in development environments where Fabric Web Studio is employed. It provides no added value and may introduce confusion in interpreting activity logs.
When auditing is enabled, audit entries are integrated into the logs shown on the Monitoring page, under the Fabric Monitor Logs panel. These entries are interspersed with standard logs and can be filtered using the search feature.
To view only audit records, enter AUDIT
into the search bar (case-sensitive).
Audit data can be downloaded in either CSV or plain text formats using one of the following methods:
Using the UI’s Vertical 3-dot Menu (⋮):
Inspect > Data
Using a Keyboard Shortcut:
i
key to access the same Inspect > Data
option and initiate export.By default, Auditing is set to OFF. To enable Auditing in Fabric, set AUDIT=ON using K2admin's Configuration panel and set a configuration override for AUDIT. You then need to restart the K2cloud space.
AUDIT=ON
Fabric auditing tracks the following activity types:
When an activity is captured by the Fabric Auditing mechanism, it is logged with the following fields:
Fabric has a robust Auditing mechanism that logs various activities running on Fabric. These can be logins, Web Service calls, and various Fabric commands.
Two major Auditing features can be controlled:
The Auditing mechanism can be configured via the [audit] and [audit_kafka_producer] sections of the config.ini. By default, the persistence strategy is Cassandra, and the data is written into the k2_auditing table of the k2audit keyspace.
When an activity is logged by the Fabric Auditing mechanism, it has the following structure:
For example, when the user performs login and authentication to the Web Framework, the activity is audited as follows:
When the user performs login to the Fabric console, it is audited as follows:
Logouts are not audited.
The following activities in Fabric can be captured by the auditing mechanism:
Click for more information about the User Identification and Access Management Auditing.
By default, Auditing is set to OFF. To enable Auditing in Fabric, set AUDIT=ON in the config.ini file and then restart Fabric.
AUDIT=ON
K2View’s auditing capability is now available to K2Cloud SaaS customers. This feature offers detailed visibility into user and system activity across Fabric.
Note: Customers using self-hosted K2Cloud environments are not eligible for this capability.
Auditing is particularly useful in production environments, where system integrity, accountability, and regulatory compliance are essential. Enabling auditing ensures that user actions and system events are accurately recorded for analysis, compliance, and troubleshooting purposes.
Here’s a list of common activities audited in production:
Auditing is not recommended in development environments, particularly when using Fabric Web Studio.
Why?
In development environments, Fabric Web Studio often executes actions on behalf of the user. If auditing is enabled:
Recommendation:
Do not enable auditing in development environments where Fabric Web Studio is employed. It provides no added value and may introduce confusion in interpreting activity logs.
When auditing is enabled, audit entries are integrated into the logs shown on the Monitoring page, under the Fabric Monitor Logs panel. These entries are interspersed with standard logs and can be filtered using the search feature.
To view only audit records, enter AUDIT
into the search bar (case-sensitive).
Audit data can be downloaded in either CSV or plain text formats using one of the following methods:
Using the UI’s Vertical 3-dot Menu (⋮):
Inspect > Data
Using a Keyboard Shortcut:
i
key to access the same Inspect > Data
option and initiate export.By default, Auditing is set to OFF. To enable Auditing in Fabric, set AUDIT=ON using K2admin's Configuration panel and set a configuration override for AUDIT. You then need to restart the K2cloud space.
AUDIT=ON
Fabric auditing tracks the following activity types:
When an activity is captured by the Fabric Auditing mechanism, it is logged with the following fields:
Fabric has a robust Auditing mechanism that logs various activities running on Fabric. These can be logins, Web Service calls, and various Fabric commands.
Two major Auditing features can be controlled:
The Auditing mechanism can be configured via the [audit] and [audit_kafka_producer] sections of the config.ini. By default, the persistence strategy is Cassandra, and the data is written into the k2_auditing table of the k2audit keyspace.
When an activity is logged by the Fabric Auditing mechanism, it has the following structure:
For example, when the user performs login and authentication to the Web Framework, the activity is audited as follows:
When the user performs login to the Fabric console, it is audited as follows:
Logouts are not audited.
The following activities in Fabric can be captured by the auditing mechanism:
Click for more information about the User Identification and Access Management Auditing.
By default, Auditing is set to OFF. To enable Auditing in Fabric, set AUDIT=ON in the config.ini file and then restart Fabric.
AUDIT=ON