All Categories
  • Authentication
  • Branding
  • Changelogs
  • Collaboration
  • Compliance
  • Customization
  • Desktop Client
  • External Storage
  • Frequently Asked Questions
  • Installation
  • Operations
  • Partner Products
  • Scalability
  • Security
  • Considerations on Monitoring

    Deploying Nextcloud on a large scale implies a close monitoring of critical software and infrastructure components. In companies, Nextcloud is most of the time run as load balanced n-tier web and requires infrastructure and application monitoring. In this section, we will provide you with an overview of what you should pay attention to when monitoring your Nextcloud instance.


    The monitoring best practices discussed here are based on the use of Web servers, a clustered database running a distributed database storage engine, such as MySQL NDB, and a clustered filesystem, such as Red Hat Storage. This is what a typical Nextcloud Deployment looks like, and it is assumed that monitoring is done with enterprise tools (log management, monitoring) already in use. Nextcloud will be considered as a target for these tools.

    Nextcloud's important components

    Nextcloud is a PHP application that depends on a filesystem for file storage, and a database for storing user and file meta data, as well as some application specific information. While the loss of an app server or a node in the database or storage clusters should not bring the system down, knowing that this happened and resolving it is essential to keeping the service running efficiently. Therefore it is important to monitor the Nextcloud servers, the Load Balancer, the Storage Cluster and the Database. This documentation starts with the Nextcloud application and works out from there through the layers of infrastructure.