App
BasicsMonitoring & operations
Basics

Monitoring & operations

Uslimato is monitored around the clock. There is nothing for you as a customer to configure — this article describes what happens in the background and what you can inspect yourself.

#What is monitored

  • Availability — whether every service is reachable and working. Outages are detected immediately
  • Performance — response times and system load. If they degrade, the platform team is informed before it becomes noticeable day to day
  • Security — unusual access patterns and error rates are evaluated so anomalies can be investigated early
  • Capacity — figures such as open tickets, managed assets, licensed users and storage usage per tenant, so growth can be planned ahead

#Alerting

When something looks unusual the platform team is notified automatically — whatever the time or day. Alerting is tiered and covers both technical measures and business thresholds.

#Error log for administration

Your tenant's administration has access to an error log — not just the platform team. It shows errors that occurred, with filters by severity, affected function and period; the detail view supplies the context for an entry.

Entries are cleaned up automatically after 30 days.

Note
The error log is deliberately accessible to tenants. If something goes wrong in your tenant you should be able to see it — not have to ask support whether there was a problem.

#What this means for you

  • Nothing to set up — monitoring runs entirely automatically
  • Proactive care — the platform team is alerted to anomalies and acts, often before you notice anything
  • Traceability — technical incidents in your tenant are visible to you

Who made which business change and when is not here but in the Audit log. The two logs answer different questions: the error log "what went wrong technically?", the audit log "who changed what?".

Was this helpful?
Suggest an edit