---
title: Rudder
description: >-
  Collect compliance data, directives, groups, techniques, rules, nodes,
  vulnerabilities, and user telemetry from Rudder.
breadcrumbs: Docs > Integrations > Rudder
---

# Rudder
Supported OS marketplaceIntegration version1.0.0           Rudder OverviewRudder - NodesRudder - GroupsRudder - DirectivesRudder - Change RequestsRudder - RulesRudder - Techniques
## Overview{% #overview %}

[**Rudder**](https://www.rudder.io/) is a robust, user-friendly web-based solution designed for IT infrastructure automation and compliance. It continuously monitors configurations, ensures compliance, and offers real-time status updates for infrastructure. Whether managing servers, cloud instances, or embedded IoT devices, Rudder centralizes configuration management in a single platform.

This integration ingests the following Rudder events as logs and metrics in Datadog:

### Metrics{% #metrics %}

- Global compliance

### Logs{% #logs %}

- Nodes compliance
- Directives
- Groups
- Techniques
- Rules
- Node vulnerabilities
- Change requests
- User management

**Note**: By default, logs for nodes are collected, capturing key information such as inventory, operating system details, and machine-related data.

### Dashboards{% #dashboards %}

This integration includes **seven out-of-the-box dashboards**:

1. **Rudder Overview**: Displays a comprehensive overview of key areas (global compliance, directives, groups, techniques, rules, nodes, change requests, user management) and insights into node-related vulnerabilities and compliance.
1. **Rudder - Nodes**
1. **Rudder - Directives**
1. **Rudder - Techniques**
1. **Rudder - Groups**
1. **Rudder - Rules**
1. **Rudder - Change Requests**

## Data Collected{% #data-collected %}

### Metrics{% #metrics-1 %}

|  |
|  |
| **cd.rudder.compliance\_stats.global\_compliance**(gauge)             | The Global Compliance score reflects overall adherence to standards. |
| **cd.rudder.compliance\_stats.compliance\_unknown\_report**(gauge)    | An unknown component was found during check                          |
| **cd.rudder.compliance\_stats.compliance\_success**(gauge)            | Compliance is already in a good state. No further action needed      |
| **cd.rudder.compliance\_stats.compliance\_repaired**(gauge)           | The non-compliance issue was repaired successfully                   |
| **cd.rudder.compliance\_stats.compliance\_not\_applicable**(gauge)    | Compliance check is not applicable in this case                      |
| **cd.rudder.compliance\_stats.compliance\_no\_report**(gauge)         | No compliance report available for the evaluation                    |
| **cd.rudder.compliance\_stats.compliance\_missing\_component**(gauge) | A component expected for compliance is missing                       |
| **cd.rudder.compliance\_stats.compliance\_error**(gauge)              | A error occurred during compliance checking                          |

### Service Checks{% #service-checks %}

**cds.rudder.can\_connect**

Returns `CRITICAL` if the Authenticating Server is Failed. Returns `OK` otherwise.

*Statuses: ok, critical*

## Support{% #support %}

For support or feature requests, contact Crest Data through the following channels:

- Support email: [datadog.integrations@crestdata.ai](mailto:datadog.integrations@crestdata.ai)
- Sales email: [datadog-sales@crestdata.ai](mailto:datadog-sales@crestdata.ai)
- Website: [crestdata.ai](https://www.crestdata.ai/)
- FAQ: [Crest Data Datadog Marketplace Integrations FAQ](https://docs.crestdata.ai/datadog-integrations-readme/Crest_Data_Datadog_Integrations_FAQ.pdf)

This application is made available through the Marketplace and is supported by a Datadog Technology Partner. Click Here to purchase this application.