Logs

Qisutu creates installation, update, web-server, daemon, and communication logs.

Overview

This page explains how to use logs and describes their main effects. Test changes in a test environment first whenever they may affect existing tickets, permissions, notifications, or automations.

Typical workflow

1. Locate the relevant logs. Perform the function in the designated form and immediately verify the result in the corresponding overview or on the affected ticket.

2. Distinguish between instance-specific services. Perform the function in the designated form and immediately verify the result in the corresponding overview or on the affected ticket.

3. Use the communication log in the interface. Perform the function in the designated form and immediately verify the result in the corresponding overview or on the affected ticket.

4. Do not store secrets or message bodies in technical logs. Perform the function in the designated form and immediately verify the result in the corresponding overview or on the affected ticket.

Notes

• Visible menu items and actions depend on the signed-in agent’s group and program permissions.

• Deactivated entries are often retained for existing tickets and reports, but are no longer available for new assignments.

• After making changes, test at least one realistic use case with a user in the affected role.