This feature is available from 4.23.0 and onwards.
This feature is not available in SaaS.
If your security policies require logging of the user activities in the system, such logging can be configured on Allure Testops side.
Services supporting audit logging
There are two components in Allure Testops allowing logging users activities.
logs actions related to
logs actions related to
work of the end users in projects
creation of entities
editing of entities
deletion of entities
Overall logging in the system can be in JSON format or in text format.
The format of logs provided by Allure Testops is defined by configuration parameter SPRING_PROFILES_ACTIVE which always present all the configurations of Allure Testops.
SPRING_PROFILES_ACTIVE configuration parameters accepts many profiles divided by comma.
There are the following profiles:
This profile is set as default one when running the application in Kubernetes. Events will be logged to the console (stdout) JSON format.
This profile is set as default one when running the application in docker compose. Events will be logged to the console (stdout) in text format with elements divided by spaces.
This profile is set as default one when running the application deployed via Linux packages (deb or rpm). Events will be logged to the console (stdout) in in text format with elements divided by spaces.
Events will be logged to the console (stdout) in JSON format.
Events will be logged to a file in JSON format. The path to the file need must be specified via LOG_FILE environment variable (described below).
For the audit logging there are two levels, defining the type of events logged by the system defined via parameter LOGGING_LEVEL_ACCESSLOG.
POST, DELETE, PATCH, PUT events will be logged
this generally means users' actions related to creation, changing/updating, deleting of entities will be logged
GET, HEAD, OPTION events will be logged
this type of logging will show all the users' actions and will be very excessive
Logging to a file
The logging can be performed to a file which can be processed by an application like logstash.
To log the events to a file, the configuration must contain LOG_FILE parameter pointing to a file where the logs need to be written to.
Full logging configuration
The following piece of the configuration allows logging POST, DELETE, PATCH, PUT events in JSON format to stdout and to the file /var/log/testops/testops.log