This check monitors Harbor through the Datadog Agent.
The Harbor check is included in the Datadog Agent package. No additional installation is needed on your server.
Follow the instructions below to configure this check for an Agent running on a host. For containerized environments, see the Containerized section.
harbor.d/conf.yaml file, in the
conf.d/ folder at the root of your Agent’s configuration directory to start collecting your Harbor performance data. See the sample harbor.d/conf.yaml for all available configuration options.
Note: You can specify any type of user in the config but an account with admin permissions is required to fetch disk metrics. The metric
harbor.projects.count only reflects the number of projects the provided user can access.
Available for Agent >6.0
Collecting logs is disabled by default in the Datadog Agent, you need to enable it in
Add this configuration block to your
harbor.d/conf.yaml file to start collecting your Harbor logs:
logs: - type: file path: /var/log/harbor/*.log source: harbor service: <SERVICE_NAME>
For containerized environments, see the Autodiscovery Integration Templates for guidance on applying the parameters below.
|blank or |
Available for Agent v6.5+
Collecting logs is disabled by default in the Datadog Agent. To enable it, see Docker log collection.
Run the Agent’s status subcommand and look for
harbor under the Checks section.
|The total number of projects.|
|The amount of storage space that is free.|
Shown as byte
|The total amount of storage space.|
Shown as byte
OK if the Harbor API is reachable and authentication is successful, otherwise returns
OK if the specified Harbor component is healthy, otherwise returns
UNKNOWN with Harbor < 1.5.
OK if the service is healthy, otherwise returns
CRITICAL. Monitors the health of external registries used by Harbor for replication.
The Harbor integration does not include any events.
Need help? Contact Datadog support.