OTOBO System Status – Monitoring & Performance
1. Overview
Section titled “1. Overview”Stable and high-performance operation of your OTOBO / Znuny system is essential to ensure fast support and smooth processes. The support data collector regularly provides a structured status report of your installation to Rother OSS, allowing you to identify critical metrics and potential vulnerabilities at an early stage.
2. Support Data Collector – How it works
Section titled “2. Support Data Collector – How it works”The support data collector automatically gathers:
- System information (OS, kernel, Perl version)
- Database insights (version, character set, indexes)
- Cluster and node status (Elasticsearch health)
- Memory and disk usage
- Mail queue and domain configuration
- OTP session data and active users
This data is sent (anonymized) to Rother OSS and visualized in an LED traffic light system:
| Section | Status LED | Meaning |
|---|---|---|
| Database | 🟢 Green | Everything within limits |
| Document search / Cluster | 🟡 Yellow | Observation recommended |
| System load & Memory | 🔴 Red | Immediate action required |
3. Detailed Status Sections
Section titled “3. Detailed Status Sections”3.1 System & OS
Section titled “3.1 System & OS”- Operating system incl. kernel version
- Perl interpreter (check compatibility)
- System load (1 / 5 / 15 min load averages)
3.2 Database
Section titled “3.2 Database”- DB version (MySQL, MariaDB, PostgreSQL)
- Character set: utf8 / utf8mb4 (client, DB server, tables)
- Index size & fragmentation
- Orphaned entries in
ticket_index&ticket_lock_index
3.3 Document Search (Elasticsearch)
Section titled “3.3 Document Search (Elasticsearch)”- Cluster health (Green/Yellow/Red)
- Shard distribution & replica status
- Index storage size
3.4 Mail Queue & Communication
Section titled “3.4 Mail Queue & Communication”- Pending mails in the send queue
- SMTP domain & reverse DNS
3.5 OTOBO Application
Section titled “3.5 OTOBO Application”- Active sessions (maximum vs. current)
- Daemon status
- Cache backend & TTL settings
- PHP/Perl modules (versions & availability)
4. System Logs & Performance Logs
Section titled “4. System Logs & Performance Logs”4.1 System Log
Section titled “4.1 System Log”A central log view in the Admin interface allows:
- Filtering by date, log level, module
- Direct search for error messages, warnings, system events
Tip: Define the log level in SysConfig according to your deployment (e.g., “WARNING” for production operation).
4.2 Performance Log
Section titled “4.2 Performance Log”Activate performance logging to:
- Collect min/max/avg response times of individual actions
- Identify bottlenecks in your widgets, modules, or database queries
- Feed dashboards with real-time metrics
Note: A short interval (e.g., 1 second) provides more granular data but may cause higher load.
5. Proactive Monitoring & Alerts
Section titled “5. Proactive Monitoring & Alerts”- Traffic light dashboard in the Admin interface shows the overall status at a glance.
- Email notifications for critical status changes (e.g., database red).
- Webhooks / SNMP traps via GenericAgent for external monitoring solutions (e.g., Z-Mon, Nagios).
6. Summary
Section titled “6. Summary”The OTOBO / Znuny support data collector and the integrated monitoring tools provide you with:
- Transparency regarding the system state
- Early warning system for performance or stability issues
- Data-driven decisions for capacity planning and optimization
Rely on regular evaluation and alerting to keep your helpdesk platform performing, secure, and fail-safe at all times!
Frequently asked questions
What is the OTOBO support data collector and what information does it gather?
The OTOBO support data collector is a crucial tool designed to gather comprehensive system health and configuration information. Its primary purpose is to help diagnose potential stability and performance issues within your OTOBO / Znuny installation, ensuring efficient management and maximum stability. It automatically collects a wide array of data, including operating system details (OS, kernel, Perl version), in-depth database insights (version, character set, indexes), cluster and node status for Elasticsearch, memory and disk usage statistics, mail queue and domain configurations, OTP session data, and information about active users. This anonymized data is then sent to Rother OSS for visualization, often presented through an LED traffic light system that indicates the severity of any detected issues (Green for good, Yellow for observation, Red for immediate action).
Where can administrators access and monitor OTOBO system status?
Administrators can check the OTOBO system status directly within the Admin area of the OTOBO interface. Specifically, under the 'System Status / support data' section, they will find various views that summarize key monitoring and performance indicators. This area often includes a traffic light dashboard, providing an at-a-glance overview of the overall system health. Beyond this summary, detailed status sections for components like the database, document search, and application status are available. Furthermore, the Admin interface offers a central log view for system logs, allowing filtering by date, log level, and module, alongside a performance log for identifying bottlenecks. Regular monitoring in these areas helps administrators proactively manage system health.
What specific areas of the OTOBO system are monitored in detail?
The OTOBO system status monitoring provides detailed insights across several critical areas to ensure optimal performance and stability. These include:
System & OS: Monitors the operating system (including kernel version), Perl interpreter compatibility, and system load averages (1, 5, and 15 minutes).
Database: Tracks the database version (MySQL, MariaDB, PostgreSQL), character set consistency (
utf8/utf8mb4across client, server, and tables), index size and fragmentation, and checks for orphaned entries inticket_indexandticket_lock_index.Document Search (Elasticsearch): Assesses cluster health (Green/Yellow/Red), shard distribution, replica status, and index storage size.
Mail Queue & Communication: Monitors pending mails in the send queue, SMTP domain configuration, and reverse DNS status.
OTOBO Application: Keeps an eye on active sessions (maximum vs. current), daemon status, cache backend and TTL settings, and the versions and availability of required PHP/Perl modules.
How can OTOBO's system and performance logs assist in troubleshooting and optimization?
OTOBO's integrated logging capabilities are invaluable for troubleshooting and optimizing system performance. The System Log, accessible via the Admin interface, provides a central view where administrators can filter by date, log level (e.g., 'WARNING' for production), and module, as well as directly search for specific error messages, warnings, or system events. This allows for quick identification of issues. The Performance Log, when activated, collects minimum, maximum, and average response times for individual actions. This data is crucial for identifying bottlenecks within widgets, modules, or database queries, and can even feed real-time metrics into dashboards. While a short logging interval provides more granular data, it's important to note it may also cause higher system load. Both logs provide data-driven insights essential for maintaining a high-performing OTOBO environment.
What proactive monitoring and alerting capabilities does OTOBO offer for critical system changes?
OTOBO provides robust proactive monitoring and alerting features to ensure administrators are promptly informed of critical system changes. A prominent traffic light dashboard in the Admin interface offers an immediate visual summary of the overall system status. For more urgent notifications, OTOBO can be configured to send email notifications when critical status changes occur, such as a database status turning 'red,' indicating an immediate need for action. Furthermore, OTOBO supports integration with external monitoring solutions through webhooks and SNMP traps via the GenericAgent. This allows for seamless communication with systems like Z-Mon or Nagios, enabling a comprehensive and centralized monitoring strategy. These capabilities collectively form an early warning system, crucial for maintaining system reliability and preventing service disruptions.
What are the key benefits of regularly monitoring OTOBO system status?
Regularly monitoring OTOBO system status offers several significant benefits for maintaining a robust and efficient helpdesk platform. Firstly, it provides complete transparency regarding the current system state, allowing administrators to understand how various components are performing. Secondly, it acts as an early warning system for potential performance degradation or stability issues, enabling proactive intervention before problems escalate and affect ticket handling or user experience. Thirdly, the collected data facilitates data-driven decisions for capacity planning, resource allocation, and overall system optimization. By consistently evaluating status reports and responding to alerts, organizations can ensure their OTOBO / Znuny helpdesk platform remains performing, secure, and fail-safe at all times, ultimately supporting fast support and smooth processes.