Documentation Grafana Alloy Reference Components discovery discovery.ovhcloud

discovery.ovhcloud

discovery.ovhcloud discovers scrape targets from the OVHcloud dedicated servers and VPS using their API. Alloy periodically checks the REST endpoint and create a target for every discovered server. The public IPv4 address is used by default. If there’s no IPv4 address, the IPv6 address is used. This may be changed via relabeling with discovery.relabel. For the OVHcloud public cloud instances you can use discovery.openstack.

Usage

alloy Copy

discovery.ovhcloud "<LABEL>" {
    application_key    = "<APPLICATION_KEY>"
    application_secret = "<APPLICATION_SECRET>"
    consumer_key       = "<CONSUMER_KEY>"
    service            = "<SERVICE>"
}

Arguments

You can use the following arguments with discovery.ovhcloud:

service must be either vps or dedicated_server.

endpoint must be one of the supported API endpoints.

Blocks

The discovery.ovhcloud component doesn’t support any blocks. You can configure this component with arguments.

Exported fields

The following fields are exported and can be referenced by other components:

Multiple meta labels are available on targets and can be used by the discovery.relabel component.

VPS meta labels:

• __meta_ovhcloud_vps_cluster: The cluster of the server.
• __meta_ovhcloud_vps_datacenter: The data center of the server.
• __meta_ovhcloud_vps_disk: The disk of the server.
• __meta_ovhcloud_vps_display_name: The display name of the server.
• __meta_ovhcloud_vps_ipv4: The IPv4 of the server.
• __meta_ovhcloud_vps_ipv6: The IPv6 of the server.
• __meta_ovhcloud_vps_keymap: The KVM keyboard layout of the server.
• __meta_ovhcloud_vps_maximum_additional_ip: The maximum additional IP addresses of the server.
• __meta_ovhcloud_vps_memory_limit: The memory limit of the server.
• __meta_ovhcloud_vps_memory: The memory of the server.
• __meta_ovhcloud_vps_monitoring_ip_blocks: The monitoring IP blocks of the server.
• __meta_ovhcloud_vps_name: The name of the server.
• __meta_ovhcloud_vps_netboot_mode: The netboot mode of the server.
• __meta_ovhcloud_vps_offer_type: The offer type of the server.
• __meta_ovhcloud_vps_offer: The offer of the server.
• __meta_ovhcloud_vps_state: The state of the server.
• __meta_ovhcloud_vps_vcore: The number of virtual cores of the server.
• __meta_ovhcloud_vps_version: The version of the server.
• __meta_ovhcloud_vps_zone: The zone of the server.

Dedicated servers meta labels:

• __meta_ovhcloud_dedicated_server_commercial_range: The commercial range of the server.
• __meta_ovhcloud_dedicated_server_datacenter: The datacenter of the server.
• __meta_ovhcloud_dedicated_server_ipv4: The IPv4 of the server.
• __meta_ovhcloud_dedicated_server_ipv6: The IPv6 of the server.
• __meta_ovhcloud_dedicated_server_link_speed: The link speed of the server.
• __meta_ovhcloud_dedicated_server_name: The name of the server.
• __meta_ovhcloud_dedicated_server_os: The operating system of the server.
• __meta_ovhcloud_dedicated_server_rack: The rack of the server.
• __meta_ovhcloud_dedicated_server_reverse: The reverse DNS name of the server.
• __meta_ovhcloud_dedicated_server_server_id: The ID of the server.
• __meta_ovhcloud_dedicated_server_state: The state of the server.
• __meta_ovhcloud_dedicated_server_support_level: The support level of the server.

Component health

discovery.ovhcloud is only reported as unhealthy when given an invalid configuration. In those cases, exported fields retain their last healthy values.

Debug information

discovery.ovhcloud doesn’t expose any component-specific debug information.

Debug metrics

discovery.ovhcloud doesn’t expose any component-specific debug metrics.

Example

alloy Copy

discovery.ovhcloud "example" {
    application_key    = "<APPLICATION_KEY>"
    application_secret = "<APPLICATION_SECRET>"
    consumer_key       = "<CONSUMER_KEY>"
    service            = "<SERVICE>"
}

prometheus.scrape "demo" {
    targets    = discovery.ovhcloud.example.targets
    forward_to = [prometheus.remote_write.demo.receiver]
}

prometheus.remote_write "demo" {
    endpoint {
        url = "<PROMETHEUS_REMOTE_WRITE_URL>"
        basic_auth {
            username = "<USERNAME>"
            password = "<PASSWORD>"
        }
    }
}

Replace the following:

• <APPLICATION_KEY>: The OVHcloud API application key.
• <APPLICATION_SECRET>: The OVHcloud API application secret.
• <CONSUMER_KEY>: The OVHcloud API consumer key.
• <SERVICE>: The OVHcloud service of the targets to retrieve.
• <PROMETHEUS_REMOTE_WRITE_URL>: The URL of the Prometheus remote_write-compatible server to send metrics to.
• <USERNAME>: The username to use for authentication to the remote_write API.
• <PASSWORD>: The password to use for authentication to the remote_write API.

Compatible components

discovery.ovhcloud has exports that can be consumed by the following components:

• Components that consume Targets