--- title: Silverstripe CMS description: Monitor Silverstripe CMS content, and user activity. breadcrumbs: Docs > Integrations > Silverstripe CMS --- # Silverstripe CMS Supported OS Integration version1.8.0Silverstripe CMS - Overview ## Overview{% #overview %} Silverstripe CMS is an open-source platform for creating and managing websites and web applications. It offers an intuitive admin panel for easy content editing and customization without coding. Its flexible framework makes it ideal for both simple sites and complex projects. The SilverStripe CMS integration collects metrics for files, pages, and failed login attempts, and sends them to Datadog for analysis and monitoring. **Minimum Agent version:** 7.65.0 ## Setup{% #setup %} ### Installation{% #installation %} The Silverstripe CMS integration is included in the [Datadog Agent package](https://app.datadoghq.com/account/settings/agent/latest). No additional installation is necessary. ### Get Database credentials from Silverstripe CMS{% #get-database-credentials-from-silverstripe-cms %} | **Parameter** | **Description** | | ------------------ | -------------------------------------------------------- | | Database Type | The type of database server, either MySQL or PostgreSQL. | | Database Name | The name of the configured database. | | Database Username | The username used to connect to the database. | | Database Password | The password associated with the database user. | | Database Server IP | The IP address of the database server. | | Database Port | The Port Number of the database server. | ### Connect your Silverstripe CMS account to agent{% #connect-your-silverstripe-cms-account-to-agent %} 1. Copy the `conf.yaml.example` file. ```sh cp /etc/datadog-agent/conf.d/silverstripe_cms.d/conf.yaml.example /etc/datadog-agent/conf.d/silverstripe_cms.d/conf.yaml ``` 1. Add this configuration block to your `silverstripe_cms.d/conf.yaml` file to start collecting your metrics. - See the sample [silverstripe_cms.d/conf.yaml](https://github.com/DataDog/integrations-core/blob/master/silverstripe_cms/datadog_checks/silverstripe_cms/data/conf.yaml.example) for available configuration options. - If you need to configure multiple instances of Silverstripe CMS in the `conf.yaml` file, reference the following example: ```yaml init_config: instances: - SILVERSTRIPE_DATABASE_TYPE: PostgreSQL SILVERSTRIPE_DATABASE_NAME: SILVERSTRIPE_DATABASE_SERVER_IP: SILVERSTRIPE_DATABASE_PORT: SILVERSTRIPE_DATABASE_USERNAME: SILVERSTRIPE_DATABASE_PASSWORD: min_collection_interval: 300 - SILVERSTRIPE_DATABASE_TYPE: MySQL SILVERSTRIPE_DATABASE_NAME: SILVERSTRIPE_DATABASE_SERVER_IP: SILVERSTRIPE_DATABASE_PORT: SILVERSTRIPE_DATABASE_USERNAME: SILVERSTRIPE_DATABASE_PASSWORD: min_collection_interval: 300 ``` 1. [Restart the Agent](https://docs.datadoghq.com/agent/guide/agent-commands/#start-stop-and-restart-the-agent). ### Validation{% #validation %} - [Run the Agent's status subcommand](https://docs.datadoghq.com/agent/guide/agent-commands/#agent-status-and-information) and look for `silverstripe_cms` under the **Checks** section. - Alternatively, use the following command to obtain detailed information about the integration: ```sh sudo datadog-agent check silverstripe_cms ``` The check returns OK if all the configurations are correct and the Agent is able to communicate with Silverstripe CMS. ## Data Collected{% #data-collected %} ### Log{% #log %} The Silverstripe CMS integration does not include any logs. ### Metrics{% #metrics %} | | | | | **silverstripe\_cms.failed\_login\_count**(gauge) | Number of Failed logins | | **silverstripe\_cms.files.count**(gauge) | Number of Files/images available in CMS | | **silverstripe\_cms.files.public\_count**(gauge) | Number of files/images that can be accessed by anyone | | **silverstripe\_cms.files\_live.count**(gauge) | Number of files currently published | | **silverstripe\_cms.files\_live.public\_count**(gauge) | Number of files published and accessible by anyone | | **silverstripe\_cms.pages.broken\_content**(gauge) | Number of pages that have broken content(link/file) | | **silverstripe\_cms.pages.broken\_file\_count**(gauge) | Number of pages that have broken files | | **silverstripe\_cms.pages.broken\_link\_count**(gauge) | Number of pages that have broken links | | **silverstripe\_cms.pages.count**(gauge) | Number of pages available in CMS | | **silverstripe\_cms.pages\_live.broken\_content**(gauge) | Number of published pages that have broken content(link/file) | | **silverstripe\_cms.pages\_live.broken\_file\_count**(gauge) | Number of published pages with broken files | | **silverstripe\_cms.pages\_live.broken\_link\_count**(gauge) | Number of published pages with broken links | | **silverstripe\_cms.pages\_live.count**(gauge) | Number of published pages | | **silverstripe\_cms.pages\_live.deleted\_count**(gauge) | Number of pages/versions deleted | ### Service Checks{% #service-checks %} The Silverstripe CMS includes service checks that are listed in the [service_checks.json](https://github.com/DataDog/integrations-core/blob/master/silverstripe_cms/assets/service_checks.json) file. ### Events{% #events %} - `Silverstripe.CMS.silverstripe_cms_authentication` triggered for authentication of the provided parameters. ## Uninstallation{% #uninstallation %} For integrations running on the Agent: - Fully remove the integration using the `datadog-agent integration remove` command. For more information, see [Integration management](https://docs.datadoghq.com/agent/guide/integration-management/?tab=linux#remove). ## Support{% #support %} For further assistance, contact [Datadog support](https://docs.datadoghq.com/help).