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.
To configure this check for an Agent running on a host:
-
Edit the
harbor.d/conf.yaml
file, in theconf.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 versions >6.0
-
Collecting logs is disabled by default in the Datadog Agent, you need to enable it in
datadog.yaml
:logs_enabled: true
-
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.
Parameter | Value |
---|---|
<INTEGRATION_NAME> |
harbor |
<INIT_CONFIG> |
blank or {} |
<INSTANCE_CONFIG> |
{"url": "https://%%host%%", "username": "<USER_ID>", "password": "<USER_PASSWORD>"} |
Available for Agent versions >6.0
Collecting logs is disabled by default in the Datadog Agent. To enable it, see Kubernetes Log Collection.
Parameter | Value |
---|---|
<LOG_CONFIG> |
{"source": "harbor", "service": "<SERVICE_NAME>"} |
Run the Agent's status subcommand and look for harbor
under the Checks section.
See metadata.csv for a list of metrics provided by this integration.
The Harbor integration does not include any events.
See service_checks.json for a list of service checks provided by this integration.
Need help? Contact Datadog support.