Vision App Maker gives administrators logs, session tracking and process views to monitor the platform from the internal portal. A built-in task scheduler runs configured activities automatically as cron jobs.
What administrators can monitor
| Area | What is visible | Where |
|---|---|---|
| Application activity | Entries generated by the App Maker Engine for every installed application domain | Logs screen |
| Sign-in activity | Every authentication attempt and its result | Logs screen |
| Data changes | Changes made to selected data entities | Entity audit |
| Current access | Active user sessions | User sessions screen |
| Portal load | Active users, users in the waiting queue, available capacity | Application settings |
| Processes | Running instances, history per case, bottlenecks and durations | Workflow views |
| API calls | Requests and responses, and live calls to published endpoints | API Gateway logs, endpoint console |
Logs
The logs screen lists entries with user, date, type, source context and technical message. Administrators can open each entry for audit, troubleshooting, monitoring or incident investigation.
Logged events include:
- general system events and application engine entries;
- successful and failed sign-in attempts;
- user actions and administrative operations;
- changes to data and documents;
- workflow events;
- requests and responses processed by the API Gateway.
Application logs are stored in the database and shown in the administration area. Only users with the matching rights can view them.
User sessions and portal capacity
The user sessions screen shows who is currently connected to the portal. Administrators use it to identify active sessions, check operational behavior and apply internal policies.
Session monitoring works together with other controls:
- authentication logs record each sign-in attempt;
- an inactivity timeout signs out idle users;
- a limit on concurrent users places extra users in a waiting queue.
Administrators can follow the number of active users, the number of users waiting and the remaining capacity.
Process monitoring
Workflows offer their own monitoring. Process instances can be viewed in real time, with the full history of each case. The platform also provides statistics on bottlenecks, durations and performance.
Each task can have a deadline. An alert is triggered when the deadline is exceeded.
API monitoring
The API Gateway logs all requests and responses for audit, debugging and metrics. Each published REST endpoint has a live console that shows its calls as they happen. Calls made through the MCP server are logged and streamed to the same console.
Identity provider monitoring
When the platform uses Keycloak, Keycloak records its own events: sign-in and sign-out, configuration changes and administrative actions. These logs can be exported to external systems such as Splunk or ELK. Keycloak also integrates with Prometheus and Grafana for performance and usage metrics.
Automatic task scheduler
The scheduler, also called robots, automates configured activities through cron jobs. Parameters are defined for each automation. Users with the required rights configure the behavior of automated jobs in the content management area.
Automated jobs are used for:
- recurring activities and scheduled operations;
- synchronizations, including user synchronization and updates of access rights;
- background processing and document processing;
- imports and updates.
Jobs run in controlled contexts, with clearly defined rights and traceable execution.
Scheduling in workflows and integrations
- Workflows can include timed steps and scheduled (cron) triggers.
- Data from external systems can be refreshed by polling at a set interval, through a cron job, worker or scheduled task.
