Active Directory Domain Services (AD DS)

Active Directory Domain Services (AD DS) stores information about objects on the network so that administrators and users can easily access this information.

For more information about AD DS, see the Active Directory Domain Services (AD DS) documentation.

Prerequisites

To collect AD DS telemetry, you must install the Ops Agent:

For metrics, install version 2.15.0 or higher.
For logs, install version 2.15.0 or higher.

This integration supports AD DS versions windows-server-2012-r2, windows-server-2016, and windows-server-2019.

Configure your AD DS instance

By default, Active Directory Windows event logs and performance counters are enabled.

Configure the Ops Agent for AD DS

Following the guide to configure the Ops Agent, add the required elements to collect telemetry from AD DS instances, and restart the agent.

Example configuration

The following commands create the configuration to collect and ingest telemetry for AD DS and restarts the Ops Agent:

$ErrorActionPreference = 'Stop'

# Create a back up of the existing file so existing configurations are not lost.
Copy-Item -Path 'C:\Program Files\Google\Cloud Operations\Ops Agent\config\config.yaml' -Destination 'C:\Program Files\Google\Cloud Operations\Ops Agent\config\config.yaml.bak'

# Configure the Ops Agent.
Add-Content 'C:\Program Files\Google\Cloud Operations\Ops Agent\config\config.yaml' "
logging:
  receivers:
    active_directory_ds:
      type: active_directory_ds
  service:
    pipelines:
      active_directory_ds:
        receivers:
        - active_directory_ds

metrics:
  receivers:
    active_directory_ds:
      type: active_directory_ds
  service:
    pipelines:
      active_directory_ds:
        receivers:
        - active_directory_ds
"

Stop-Service google-cloud-ops-agent -Force
Start-Service google-cloud-ops-agent*

Configure logs collection

To ingest logs from AD DS, you must create receivers for the logs that AD DS produces and then create a pipeline for the new receivers.

To configure a receiver for your active_directory_ds logs, specify the following fields:

Field	Default	Description
`type`		The value must be `active_directory_ds`.

What is logged

The logName is derived from the receiver IDs specified in the configuration. Detailed fields inside the LogEntry are as follows.

active_directory_ds logs contain the following fields in the LogEntry:

Field	Type	Description
`jsonPayload.Channel`	string	The event log channel where the log was logged.
`jsonPayload.ComputerName`	string	The name of the computer from which this log originates.
`jsonPayload.Data`	string	Extra event-specific data included with the log.
`jsonPayload.EventCategory`	number	The category of the event.
`jsonPayload.EventID`	number	An ID identifying the type of the event.
`jsonPayload.EventType`	string	The type of event.
`jsonPayload.Message`	string	The log message.
`jsonPayload.Qualifiers`	number	A qualifier number that is used for event identification.
`jsonPayload.RecordNumber`	number	The sequence number of the event log.
`jsonPayload.Sid`	string	The security identifier identifying a security principal or security group of the process that logged this message.
`jsonPayload.SourceName`	string	The source component that logged this message.
`jsonPayload.StringInserts`	[]string	Dynamic string data that was used to construct the log message.
`jsonPayload.TimeGenerated`	string	A timestamp representing when the record was generated.
`jsonPayload.TimeWritten`	string	A timestamp representing when the record was written to the event log.

Configure metrics collection

To ingest metrics from AD DS, you must create a receiver for the metrics that AD DS produces and then create a pipeline for the new receiver.

This receiver does not support the use of multiple instances in the configuration, for example, to monitor multiple endpoints. All such instances write to the same time series, and Cloud Monitoring has no way to distinguish among them.

To configure a receiver for your active_directory_ds metrics, specify the following fields:

Field	Default	Description
`collection_interval`	`60s`	A `time.Duration` value, such as `30s` or `5m`.
`type`		The value must be `active_directory_ds`.

What is monitored

The following table provides the list of metrics that the Ops Agent collects from the AD DS instance.

Metric type
Kind, Type Monitored resources	Labels
`workload.googleapis.com/active_directory.ds.bind.rate`
`GAUGE`, `DOUBLE` gce_instance	`type`
`workload.googleapis.com/active_directory.ds.ldap.bind.last_successful.time`
`GAUGE`, `INT64` gce_instance
`workload.googleapis.com/active_directory.ds.ldap.bind.rate`
`GAUGE`, `DOUBLE` gce_instance
`workload.googleapis.com/active_directory.ds.ldap.client.session.count`
`GAUGE`, `INT64` gce_instance
`workload.googleapis.com/active_directory.ds.ldap.search.rate`
`GAUGE`, `DOUBLE` gce_instance
`workload.googleapis.com/active_directory.ds.name_cache.hit_rate`
`GAUGE`, `DOUBLE` gce_instance
`workload.googleapis.com/active_directory.ds.notification.queued`
`GAUGE`, `INT64` gce_instance
`workload.googleapis.com/active_directory.ds.operation.rate`
`GAUGE`, `DOUBLE` gce_instance	`type`
`workload.googleapis.com/active_directory.ds.replication.network.io`
`CUMULATIVE`, `INT64` gce_instance	`direction` `type`
`workload.googleapis.com/active_directory.ds.replication.object.rate`
`GAUGE`, `DOUBLE` gce_instance	`direction`
`workload.googleapis.com/active_directory.ds.replication.operation.pending`
`GAUGE`, `INT64` gce_instance
`workload.googleapis.com/active_directory.ds.replication.property.rate`
`GAUGE`, `DOUBLE` gce_instance	`direction`
`workload.googleapis.com/active_directory.ds.replication.sync.object.pending`
`GAUGE`, `INT64` gce_instance
`workload.googleapis.com/active_directory.ds.replication.sync.request.count`
`CUMULATIVE`, `INT64` gce_instance	`result`
`workload.googleapis.com/active_directory.ds.replication.value.rate`
`GAUGE`, `DOUBLE` gce_instance	`direction` `type`
`workload.googleapis.com/active_directory.ds.security_descriptor_propagations_event.queued`
`GAUGE`, `INT64` gce_instance
`workload.googleapis.com/active_directory.ds.suboperation.rate`
`GAUGE`, `DOUBLE` gce_instance	`type`
`workload.googleapis.com/active_directory.ds.thread.count`
`GAUGE`, `INT64` gce_instance

Verify the configuration

This section describes how to verify that you correctly configured the AD DS receiver. It might take one or two minutes for the Ops Agent to begin collecting telemetry.

To verify that AD DS logs are being sent to Cloud Logging, do the following:

In the Google Cloud console, select Logging, and then select Logs Explorer, or click the following button:
Go to the Logs Explorer
Enter the following query in the editor, and then click Run query:
```
resource.type="gce_instance"
log_id("active_directory_ds")
```

To verify that AD DS metrics are being sent to Cloud Monitoring, do the following:

In the Google Cloud console, select Monitoring, and then select Metrics Explorer, or click the following button:
Go to Metrics Explorer
In the toolbar of the Select a metric pane, select the button whose name starts with Code.
Select MQL in the Language toggle. The language toggle is in the same toolbar that lets you format your query.

Enter the following query in the editor, and then click Run query:

fetch gce_instance
| metric 'workload.googleapis.com/active_directory.ds.bind.rate'
| every 1m

View dashboard

To view your AD DS metrics, you must have a chart or dashboard configured. The AD DS integration includes one or more dashboards for you. Any dashboards are automatically installed after you configure the integration and the Ops Agent has begun collecting metric data.

You can also view static previews of dashboards without installing the integration.

To view an installed dashboard, do the following:

In the Google Cloud console, select Monitoring, and then select Dashboards, or click the following button:
Go to Dashboards
Select the Dashboard List tab, and then choose the Integrations category.
Click the name of the dashboard you want to view.

If you have configured an integration but the dashboard has not been installed, then check that the Ops Agent is running. When there is no metric data for a chart in the dashboard, installation of the dashboard fails. After the Ops Agent begins collecting metrics, the dashboard is installed for you.

To view a static preview of the dashboard, do the following:

In the Google Cloud console, select Monitoring, and then select Integrations, or click the following button:
Go to Integrations
Click the Compute Engine deployment-platform filter.
Locate the entry for AD DS and click View Details.
Select the Dashboards tab to see a static preview. If the dashboard is installed, then you can navigate to it by clicking View dashboard.

For more information about dashboards in Cloud Monitoring, see Dashboards and charts.

For more information about using the Integrations page, see Manage integrations.

Install alerting policies

Alerting policies instruct Cloud Monitoring to notify you when specified conditions occur. The AD DS integration includes one or more alerting policies for you to use. You can view and install these alerting policies from the Integrations page in Monitoring.

To view the descriptions of available alerting policies and install them, do the following:

In the Google Cloud console, select Monitoring, and then select Integrations, or click the following button:
Go to Integrations
Locate the entry for AD DS and click View Details.
Select the Alerts tab. This tab provides descriptions of available alerting policies and provides an interface for installing them.
Install alerting policies. Alerting policies need to know where to send notifications that the alert has been triggered, so they require information from you for installation. To install alerting policies, do the following:
1. From the list of available alerting policies, select those that you want to install.
2. In the Configure notifications section, select one or more notification channels. You have the option to disable the use of notification channels, but if you do, then your alerting policies fire silently. You can check their status in Monitoring, but you receive no notifications.
  
  For more information about notification channels, see Manage notification channels.
3. Click Create Policies.

For more information about alerting policies in Cloud Monitoring, see Introduction to alerting.

For more information about using the Integrations page, see Manage integrations.

What's next

For a walkthrough on how to use Ansible to install the Ops Agent, configure a third-party application, and install a sample dashboard, see the Install the Ops Agent to troubleshoot third-party applications video.