FAQ & Help
Here you will find frequently asked questions and the relevant answers on topics relating to Seewara. If your question is not listed, our customer service team will be happy to provide you with further assistance – Monday to Sunday from 6am to 10pm.
How to reach us
Do you have questions or need help? Talk to us: Monday to Sunday from 6 a.m. to 10 p.m.
What are activities?
Activities in a software, also known as a logbook, are records or logs of events and actions performed within the software. They provide a detailed overview of the actions performed by users or the system itself at specific times. These activities are particularly important for traceability, troubleshooting, security monitoring and the administration of processes within the software.
Features and functions of a logbook/activity log:
- Logging user actions
- A logbook records user interactions with the software. These can be, for example, logins, opening documents, creating or editing records, sending messages or completing tasks.
- This information may include the user name, the time of the action, and the action performed.
- System events and errors
- In addition to user actions, the logbook also logs system events such as errors, warnings, or automatic processes. For example, there could be an error log for system crashes, database queries, or system updates.
- Security events, such as unauthorised access attempts, are also often noted in the logbook.
- Automated activities
- In many modern software systems, there are automated processes or batch processing. These actions are also recorded in the logbook. An example would be an automated import of data that takes place at a specific time and is logged when it is complete.
- Time synchronisation
- Activities are often time stamped (with the date and time) to make the exact sequence of events traceable.
- Detailed descriptions and context
- In many logbook systems, a detailed description of the action is recorded, e.g. who did what, when and what the result was. This helps to identify the causes of problems and to understand changes in software development or usage.
Examples of information that may be included in a logbook or activity log:
- User data: Who performed the action (e.g. the user name or system ID)?
- Action type: What action was performed? (e.g. ‘data saved’, ‘user added’, ‘error occurred’).
- Timestamp: When did the action take place (date and time)?
- Data changes: Which data was changed, created or deleted?
- Error reports: If an error occurs, the error code and a brief description of the cause are logged.
- IP addresses or device information: For security-related actions, the IP address or the device used can also be logged.
Types of logbooks in software systems:
User activity logs
- These log all actions performed by users within the software, such as logging on, entering data, changing data or navigating.
- System logs
- These logs relate to the activities of the system itself, such as server requests, database access, system errors or updates. They often help to diagnose technical problems.
- Security logs
- These logs record security-related events, such as login attempts, failed authentications, attempts to access sensitive data or changes to user rights.
- Error logs
- In error logs, system errors, exceptions or software crashes are documented, including the cause of the error and the affected system components.
Advantages of a logbook/activity logging:
Traceability and transparency
- A logbook makes all actions within the software traceable, which is particularly important for error analysis, auditing and audit security.
- Security
- The logging of security-relevant events helps to quickly detect and respond to unauthorised access attempts or manipulation.
- Troubleshooting
- Logbooks provide detailed information that helps to locate and fix errors. If software crashes or a problem occurs, developers or system administrators can use the error logs to determine the cause.
- Compliance and legal security
- In many industries, companies are required to log data and user activities in order to comply with legal requirements, e.g. under the General Data Protection Regulation (GDPR) or ISO standards.
- Auditing and monitoring
- A logbook makes it possible to carry out audits and monitor the progress of actions. This is particularly important when monitoring business processes or ensuring compliance with company guidelines.
Areas of application for logbooks:
- Web applications: Activity logging is used to track user interactions and movements in a web application.
- Enterprise software (e.g. ERP systems): Business processes and transactions are recorded here.
- Accounting and financial software: Logbooks help to record all accounting transactions and changes.
- IT infrastructure: logbooks are used on servers, databases and networks to monitor the health of the system and any issues that arise.
Conclusion:
A software logbook (or activity log) is a powerful tool for monitoring and documenting activities within the system. It ensures transparency, enables troubleshooting, helps with security monitoring and is an indispensable tool for compliance and audit security.