Consul
Rapport de recherche Datadog : Bilan sur l'adoption de l'informatique sans serveur Rapport : Bilan sur l'adoption de l'informatique sans serveur

Consul

Agent Check Check de l'Agent

Supported OS: Linux Mac OS Windows

Dashboard Consul

Présentation

L’Agent Datadog recueille de nombreuses métriques sur les nœuds Consul, notamment pour :

  • Le nombre total de pairs Consul
  • La santé des services : le nombre de nœuds avec le statut Up, Passing, Warning ou Critical d’un service donné
  • La santé des nœuds : le nombre de services avec le statut Up, Passing, Warning ou Critical d’un nœud donné
  • Les coordonnées réseau : latences entre les centres de données et au sein de ces derniers

L’Agent Consul peut fournir davantage de métriques via DogStatsD. Ces métriques sont davantage orientées sur la santé interne de Consul, et non sur celle des services qui dépendent de Consul. Elles concernent :

  • Les événements Serf et les bagottements de membre
  • Le protocole Raft
  • Les performances DNS

Et bien plus encore.

Enfin, en plus des métriques, l’Agent Datadog envoie également un check de service pour chaque check de santé de Consul, ainsi qu’un événement après chaque nouvelle élection de leader.

Configuration

Installation

Le check Consul de l’Agent Datadog est inclus avec le paquet de l’Agent Datadog : vous n’avez donc rien d’autre à installer sur vos nœuds Consul.

Configuration

Host

Suivez les instructions ci-dessous pour configurer ce check lorsque l’Agent est exécuté sur un host. Consultez la section Environnement conteneurisé pour en savoir plus sur les environnements conteneurisés.

Collecte de métriques
  1. Modifiez le fichier consul.d/conf.yaml dans le dossier conf.d/ à la racine du répertoire de configuration de votre Agent pour commencer à recueillir vos métriques Consul. Consultez le fichier d’exemple consul.d/conf.yaml pour découvrir toutes les options de configuration disponibles.

    init_config:
    
    instances:
     ## @param url - string - required
     ## Where your Consul HTTP Server Lives
     ## Point the URL at the leader to get metrics about your Consul Cluster.
     ## Remind to use https instead of http if your Consul setup is configured to do so.
     #
     - url: http://localhost:8500
  2. Redémarrez l’Agent.

Rechargez l’Agent Consul pour commencer à envoyer davantage de métriques Consul à DogStatsD.

Collecte de logs

Disponible à partir des versions > 6.0 de l’Agent

  1. La collecte de logs est désactivée par défaut dans l’Agent Datadog. Vous devez l’activer dans datadog.yaml avec :

    logs_enabled: true
  2. Ajoutez ce bloc de configuration à votre fichier consul.yaml pour commencer à recueillir vos logs Consul :

    logs:
     - type: file
       path: /var/log/consul_server.log
       source: consul
       service: myservice

Modifiez les valeurs des paramètres path et service et configurez-les pour votre environnement. Consultez le fichier d’exemple consul.d/conf.yaml pour découvrir toutes les options de configuration disponibles.

  1. Redémarrez l’Agent.

Environnement conteneurisé

Consultez la documentation relative aux modèles d’intégration Autodiscovery pour découvrir comment appliquer les paramètres ci-dessous à un environnement conteneurisé.

Collecte de métriques
ParamètreValeur
<NOM_INTÉGRATION>consul
<CONFIG_INIT>vide ou {}
<CONFIG_INSTANCE>{"url": "https://%%host%%:8500"}
Collecte de logs

Disponible à partir des versions > 6.0 de l’Agent

La collecte des logs est désactivée par défaut dans l’Agent Datadog. Pour l’activer, consultez la section Collecte de logs avec Kubernetes.

ParamètreValeur
<CONFIG_LOG>{"source": "consul", "service": "<NOM_SERVICE>"}

DogStatsD

Si vous le souhaitez, vous pouvez configurer Consul de façon à ce qu’il envoie les données à l’Agent via DogStatsD au lieu de demander à l’Agent de récupérer les données auprès de Consul.

  1. Pour configurer Consul de façon à ce qu’il envoie des métriques DogStatsD, ajoutez votre dogstatsd_addr imbriqué sous la clé telemetry de premier niveau dans le fichier de configuration principal de Consul :

    {
      ...
      "telemetry": {
        "dogstatsd_addr": "127.0.0.1:8125"
      },
      ...
    }
  2. Pour veiller à ce que les métriques soient correctement taguées, modifiez le fichier de configuration principal de l’Agent Datadog datadog.yaml en y ajoutant les paramètres suivants :

    # dogstatsd_mapper_cache_size: 1000  # default to 1000
    dogstatsd_mapper_profiles:
     - name: consul
       prefix: "consul."
       mappings:
         - match: 'consul\.http\.([a-zA-Z]+)\.(.*)'
           match_type: "regex"
           name: "consul.http.request"
           tags:
             http_method: "$1"
             path: "$2"
         - match: 'consul\.raft\.replication\.appendEntries\.logs\.([0-9a-f-]+)'
           match_type: "regex"
           name: "consul.raft.replication.appendEntries.logs"
           tags:
             consul_node_id: "$1"
         - match: 'consul\.raft\.replication\.appendEntries\.rpc\.([0-9a-f-]+)'
           match_type: "regex"
           name: "consul.raft.replication.appendEntries.rpc"
           tags:
             consul_node_id: "$1"
         - match: 'consul\.raft\.replication\.heartbeat\.([0-9a-f-]+)'
           match_type: "regex"
           name: "consul.raft.replication.heartbeat"
           tags:
             consul_node_id: "$1"
  3. Redémarrez l’Agent.

Validation

Lancez la sous-commande status de l’Agent et cherchez consul dans la section Checks.

Remarque : si la journalisation de debugging est activée sur vos nœuds Consul, l’interrogation habituelle de l’Agent Datadog s’affichera dans le log Consul :

2017/03/27 21:38:12 [DEBUG] http: Request GET /v1/status/leader (59.344us) from=127.0.0.1:53768
2017/03/27 21:38:12 [DEBUG] http: Request GET /v1/status/peers (62.678us) from=127.0.0.1:53770
2017/03/27 21:38:12 [DEBUG] http: Request GET /v1/health/state/any (106.725us) from=127.0.0.1:53772
2017/03/27 21:38:12 [DEBUG] http: Request GET /v1/catalog/services (79.657us) from=127.0.0.1:53774
2017/03/27 21:38:12 [DEBUG] http: Request GET /v1/health/service/consul (153.917us) from=127.0.0.1:53776
2017/03/27 21:38:12 [DEBUG] http: Request GET /v1/coordinate/datacenters (71.778us) from=127.0.0.1:53778
2017/03/27 21:38:12 [DEBUG] http: Request GET /v1/coordinate/nodes (84.95us) from=127.0.0.1:53780

De l’Agent Consul à DogStatsD

Utilisez netstat pour vérifier que Consul envoie également ses métriques :

$ sudo netstat -nup | grep "127.0.0.1:8125.*ESTABLISHED"
udp        0      0 127.0.0.1:53874         127.0.0.1:8125          ESTABLISHED 23176/consul

Données collectées

Métriques

consul.catalog.nodes_critical
(gauge)
The number of nodes with service status `critical` from those registered
Shown as node
consul.catalog.nodes_passing
(gauge)
The number of nodes with service status `passing` from those registered
Shown as node
consul.catalog.nodes_up
(gauge)
The number of nodes
Shown as node
consul.catalog.nodes_warning
(gauge)
The number of nodes with service status `warning` from those registered
Shown as node
consul.catalog.total_nodes
(gauge)
The number of nodes registered in the consul cluster
Shown as node
consul.catalog.services_critical
(gauge)
Total critical services on nodes
Shown as service
consul.catalog.services_passing
(gauge)
Total passing services on nodes
Shown as service
consul.catalog.services_up
(gauge)
Total services registered on nodes
Shown as service
consul.catalog.services_warning
(gauge)
Total warning services on nodes
Shown as service
consul.catalog.services_count
(gauge)
Metrics to count the number of services matching criteria like the service tag, the node name, or the status. To be queried using the `sum by` aggregator.
Shown as service
consul.net.node.latency.min
(gauge)
minimum latency from this node to all others
Shown as millisecond
consul.net.node.latency.p25
(gauge)
p25 latency from this node to all others
Shown as millisecond
consul.net.node.latency.median
(gauge)
median latency from this node to all others
Shown as millisecond
consul.net.node.latency.p75
(gauge)
p75 latency from this node to all others
Shown as millisecond
consul.net.node.latency.p90
(gauge)
p90 latency from this node to all others
Shown as millisecond
consul.net.node.latency.p95
(gauge)
p95 latency from this node to all others
Shown as millisecond
consul.net.node.latency.p99
(gauge)
p99 latency from this node to all others
Shown as millisecond
consul.net.node.latency.max
(gauge)
maximum latency from this node to all others
Shown as millisecond
consul.peers
(gauge)
The number of peers in the peer set
consul.memberlist.degraded.probe
(gauge)
[DogStatsD only] This metric counts the number of times the Consul agent has performed failure detection on another agent at a slower probe rate. The agent uses its own health metric as an indicator to perform this action. (If its health score is low, means that the node is healthy, and vice versa.)
consul.memberlist.gossip.95percentile
(gauge)
[DogStatsD only] The p95 for the number of gossips (messages) broadcasted to a set of randomly selected nodes.
Shown as message
consul.memberlist.gossip.avg
(gauge)
[DogStatsD only] The avg for the number of gossips (messages) broadcasted to a set of randomly selected nodes.
Shown as message
consul.memberlist.gossip.count
(rate)
[DogStatsD only] The number of samples of consul.memberlist.gossip
consul.memberlist.gossip.max
(gauge)
[DogStatsD only] The max for the number of gossips (messages) broadcasted to a set of randomly selected nodes.
Shown as message
consul.memberlist.gossip.median
(gauge)
[DogStatsD only] The median for the number of gossips (messages) broadcasted to a set of randomly selected nodes.
Shown as message
consul.memberlist.health.score
(gauge)
[DogStatsD only] This metric describes a node's perception of its own health based on how well it is meeting the soft real-time requirements of the protocol. This metric ranges from 0 to 8, where 0 indicates "totally healthy". For more details see section IV of the Lifeguard paper: https://arxiv.org/pdf/1707.00788.pdf
consul.memberlist.msg.alive
(gauge)
[DogStatsD only] This metric counts the number of alive Consul agents, that the agent has mapped out so far, based on the message information given by the network layer.
consul.memberlist.msg.dead
(gauge)
[DogStatsD only] This metric counts the number of times a Consul agent has marked another agent to be a dead node.
Shown as message
consul.memberlist.msg.suspect
(rate)
[DogStatsD only] The number of times a Consul agent suspects another as failed while probing during gossip protocol
consul.memberlist.msg_alive
(gauge)
[DogStatsD only] This metric counts the number of alive Consul agents, that the agent has mapped out so far, based on the message information given by the network layer.
Shown as node
consul.memberlist.msg_dead
(gauge)
[DogStatsD only] This metric gives the number of dead Consul agents, that the agent has mapped out so far, based on the message information given by the network layer.
Shown as node
consul.memberlist.probenode.95percentile
(gauge)
[DogStatsD only] The p95 for the time taken to perform a single round of failure detection on a select Consul agent.
Shown as node
consul.memberlist.probenode.avg
(gauge)
[DogStatsD only] The avg for the time taken to perform a single round of failure detection on a select Consul agent.
Shown as node
consul.memberlist.probenode.count
(rate)
[DogStatsD only] The number of samples of consul.memberlist.probenode
consul.memberlist.probenode.max
(gauge)
[DogStatsD only] The max for the time taken to perform a single round of failure detection on a select Consul agent.
Shown as node
consul.memberlist.probenode.median
(gauge)
[DogStatsD only] The median for the time taken to perform a single round of failure detection on a select Consul agent.
Shown as node
consul.memberlist.pushpullnode.95percentile
(gauge)
[DogStatsD only] The p95 for the number of Consul agents that have exchanged state with this agent.
Shown as node
consul.memberlist.pushpullnode.avg
(gauge)
[DogStatsD only] The avg for the number of Consul agents that have exchanged state with this agent.
Shown as node
consul.memberlist.pushpullnode.count
(rate)
[DogStatsD only] The number of samples of consul.memberlist.pushpullnode
consul.memberlist.pushpullnode.max
(gauge)
[DogStatsD only] The max for the number of Consul agents that have exchanged state with this agent.
Shown as node
consul.memberlist.pushpullnode.median
(gauge)
[DogStatsD only] The median for the number of Consul agents that have exchanged state with this agent.
Shown as node
consul.memberlist.tcp.accept
(gauge)
[DogStatsD only] This metric counts the number of times a Consul agent has accepted an incoming TCP stream connection.
Shown as connection
consul.memberlist.tcp.connect
(gauge)
[DogStatsD only] This metric counts the number of times a Consul agent has initiated a push/pull sync with an other agent.
Shown as connection
consul.memberlist.tcp.sent
(gauge)
[DogStatsD only] This metric measures the total number of bytes sent by a Consul agent through the TCP protocol
Shown as byte
consul.memberlist.udp.received
(gauge)
[DogStatsD only] This metric measures the total number of bytes sent/received by a Consul agent through the UDP protocol.
Shown as byte
consul.memberlist.udp.sent
(gauge)
[DogStatsD only] This metric measures the total number of bytes sent/received by a Consul agent through the UDP protocol.
Shown as byte
consul.client.rpc
(rate)
[DogStatsD only] This increments whenever a Consul agent in client mode makes an RPC request to a Consul server. This gives a measure of how much a given agent is loading the Consul servers. Currently, this is only generated by agents in client mode, not Consul servers.
Shown as request
consul.client.rpc.failed
(gauge)
[DogStatsD only] Increments whenever a Consul agent in client mode makes an RPC request to a Consul server and fails
Shown as request
consul.hosts_file.age
(gauge)
[DogStatsD only] Age of the hosts file
consul.http..
(gauge)
[DogStatsD only] This tracks how long it takes to service the given HTTP request for the given verb and path. Paths do not include details like service or key names, for these an underscore will be present as a placeholder (eg. consul.http.GET.v1.kv._)
Shown as millisecond
consul.runtime.num_goroutines
(gauge)
[DogStatsD only] The number of running goroutines
consul.runtime.alloc_bytes
(gauge)
[DogStatsD only] Current bytes allocated by the Consul process
Shown as byte
consul.runtime.heap_objects
(gauge)
[DogStatsD only] The number of objects allocated on the heap
Shown as object
consul.runtime.sys_bytes
(gauge)
[DogStatsD only] Total size of the virtual address space reserved by the Go runtime
Shown as byte
consul.runtime.malloc_count
(gauge)
[DogStatsD only] Cumulative count of heap objects allocated
Shown as object
consul.runtime.free_count
(gauge)
[DogStatsD only] Cumulative count of heap objects freed
Shown as object
consul.runtime.total_gc_pause_ns
(gauge)
[DogStatsD only] Cumulative nanoseconds in GC stop-the-world pauses since Consul started
Shown as nanosecond
consul.runtime.total_gc_runs
(gauge)
[DogStatsD only] The number of completed GC cycles
consul.runtime.gc_pause_ns.95percentile
(gauge)
[DogStatsD only] The p95 for the number of nanoseconds consumed by stop-the-world garbage collection (GC) pauses since Consul started.
Shown as nanosecond
consul.runtime.gc_pause_ns.avg
(gauge)
[DogStatsD only] The avg for the number of nanoseconds consumed by stop-the-world garbage collection (GC) pauses since Consul started.
Shown as nanosecond
consul.runtime.gc_pause_ns.count
(rate)
[DogStatsD only] The number of samples of consul.runtime.gc_pause_ns
consul.runtime.gc_pause_ns.max
(gauge)
[DogStatsD only] The max for the number of nanoseconds consumed by stop-the-world garbage collection (GC) pauses since Consul started.
Shown as nanosecond
consul.runtime.gc_pause_ns.median
(gauge)
[DogStatsD only] The median for the number of nanoseconds consumed by stop-the-world garbage collection (GC) pauses since Consul started.
Shown as nanosecond
consul.raft.state.leader
(rate)
[DogStatsD only] The number of completed leader elections
Shown as event
consul.raft.state.candidate
(rate)
[DogStatsD only] The number of initiated leader elections
Shown as event
consul.raft.apply
(rate)
[DogStatsD only] The number of raft transactions occurring
Shown as transaction
consul.raft.commitTime.avg
(gauge)
[DogStatsD only] The average time it takes to commit a new entry to the raft log on the leader
Shown as millisecond
consul.raft.commitTime.count
(rate)
[DogStatsD only] The number of samples of raft.commitTime
consul.raft.commitTime.max
(gauge)
[DogStatsD only] The max time it takes to commit a new entry to the raft log on the leader
Shown as millisecond
consul.raft.commitTime.median
(gauge)
[DogStatsD only] The median time it takes to commit a new entry to the raft log on the leader
Shown as millisecond
consul.raft.commitTime.95percentile
(gauge)
[DogStatsD only] The p95 time it takes to commit a new entry to the raft log on the leader
Shown as millisecond
consul.raft.leader.dispatchLog.avg
(gauge)
[DogStatsD only] The average time it takes for the leader to write log entries to disk
Shown as millisecond
consul.raft.leader.dispatchLog.count
(rate)
[DogStatsD only] The number of samples of raft.leader.dispatchLog
consul.raft.leader.dispatchLog.max
(gauge)
[DogStatsD only] The max time it takes for the leader to write log entries to disk
Shown as millisecond
consul.raft.leader.dispatchLog.median
(gauge)
[DogStatsD only] The median time it takes for the leader to write log entries to disk
Shown as millisecond
consul.raft.leader.dispatchLog.95percentile
(gauge)
[DogStatsD only] The p95 time it takes for the leader to write log entries to disk
Shown as millisecond
consul.raft.leader.lastContact.avg
(gauge)
[DogStatsD only] Average time elapsed since the leader was last able to check its lease with followers
Shown as millisecond
consul.raft.leader.lastContact.count
(rate)
[DogStatsD only] The number of samples of raft.leader.lastContact
consul.raft.leader.lastContact.max
(gauge)
[DogStatsD only] Max time elapsed since the leader was last able to check its lease with followers
Shown as millisecond
consul.raft.leader.lastContact.median
(gauge)
[DogStatsD only] Median time elapsed since the leader was last able to check its lease with followers
Shown as millisecond
consul.raft.leader.lastContact.95percentile
(gauge)
[DogStatsD only] P95 time elapsed since the leader was last able to check its lease with followers
Shown as millisecond
consul.serf.events
(rate)
[DogStatsD only] Incremented when a Consul agent processes a serf event
Shown as event
consul.serf.coordinate.adjustment_ms.95percentile
(gauge)
[DogStatsD only] The p95 in milliseconds for the node coordinate adjustment
Shown as millisecond
consul.serf.coordinate.adjustment_ms.avg
(gauge)
[DogStatsD only] The avg in milliseconds for the node coordinate adjustment
Shown as millisecond
consul.serf.coordinate.adjustment_ms.count
(rate)
[DogStatsD only] The number of samples of consul.serf.coordinate.adjustment_ms
consul.serf.coordinate.adjustment_ms.max
(gauge)
[DogStatsD only] The max in milliseconds for the node coordinate adjustment
Shown as millisecond
consul.serf.coordinate.adjustment_ms.median
(gauge)
[DogStatsD only] The median in milliseconds for the node coordinate adjustment
Shown as millisecond
consul.serf.member.flap
(rate)
[DogStatsD only] The number of times a Consul agent is marked dead and then quickly recovers
consul.serf.member.join
(rate)
[DogStatsD only] Incremented when a Consul agent processes a join event
Shown as event
consul.serf.member.update
(gauge)
[DogStatsD only] This increments when a Consul agent updates.
consul.serf.member.failed
(gauge)
[DogStatsD only] This increments when a Consul agent is marked dead. This can be an indicator of overloaded agents, network problems, or configuration errors where agents cannot connect to each other on the required ports.
consul.serf.member.left
(gauge)
[DogStatsD only] This increments when a Consul agent leaves the cluster.
consul.serf.msgs.received.95percentile
(gauge)
[DogStatsD only] The p95 for the number of serf messages received
Shown as message
consul.serf.msgs.received.avg
(gauge)
[DogStatsD only] The avg for the number of serf messages received
Shown as message
consul.serf.msgs.received.count
(rate)
[DogStatsD only] The count of serf messages received
consul.serf.msgs.received.max
(gauge)
[DogStatsD only] The max for the number of serf messages received
Shown as message
consul.serf.msgs.received.median
(gauge)
[DogStatsD only] The median for the number of serf messages received
Shown as message
consul.serf.msgs.sent.95percentile
(gauge)
[DogStatsD only] The p95 for the number of serf messages sent
Shown as message
consul.serf.msgs.sent.avg
(gauge)
[DogStatsD only] The avg for the number of serf messages sent
Shown as message
consul.serf.msgs.sent.count
(rate)
[DogStatsD only] The count of serf messages sent
consul.serf.msgs.sent.max
(gauge)
[DogStatsD only] The max for the number of serf messages sent
Shown as message
consul.serf.msgs.sent.median
(gauge)
[DogStatsD only] The median for the number of serf messages sent
Shown as message
consul.serf.queue.event.95percentile
(gauge)
[DogStatsD only] The p95 for the size of the serf event queue
consul.serf.queue.event.avg
(gauge)
[DogStatsD only] The avg size of the serf event queue
consul.serf.queue.event.count
(rate)
[DogStatsD only] The number of items in the serf event queue
consul.serf.queue.event.max
(gauge)
[DogStatsD only] The max size of the serf event queue
consul.serf.queue.event.median
(gauge)
[DogStatsD only] The median size of the serf event queue
consul.serf.queue.intent.95percentile
(gauge)
[DogStatsD only] The p95 for the size of the serf intent queue
consul.serf.queue.intent.avg
(gauge)
[DogStatsD only] The avg size of the serf intent queue
consul.serf.queue.intent.count
(rate)
[DogStatsD only] The number of items in the serf intent queue
consul.serf.queue.intent.max
(gauge)
[DogStatsD only] The max size of the serf intent queue
consul.serf.queue.intent.median
(gauge)
[DogStatsD only] The median size of the serf intent queue
consul.serf.queue.query.95percentile
(gauge)
[DogStatsD only] The p95 for the size of the serf query queue
consul.serf.queue.query.avg
(gauge)
[DogStatsD only] The avg size of the serf query queue
consul.serf.queue.query.count
(rate)
[DogStatsD only] The number of items in the serf query queue
consul.serf.queue.query.max
(gauge)
[DogStatsD only] The max size of the serf query queue
consul.serf.queue.query.median
(gauge)
[DogStatsD only] The median size of the serf query queue
consul.serf.snapshot.appendline.95percentile
(gauge)
[DogStatsD only] The p95 of the time taken by the Consul agent to append an entry into the existing log.
Shown as millisecond
consul.serf.snapshot.appendline.avg
(gauge)
[DogStatsD only] The avg of the time taken by the Consul agent to append an entry into the existing log.
Shown as millisecond
consul.serf.snapshot.appendline.count
(rate)
[DogStatsD only] The number of samples of consul.serf.snapshot.appendline
consul.serf.snapshot.appendline.max
(gauge)
[DogStatsD only] The max of the time taken by the Consul agent to append an entry into the existing log.
Shown as millisecond
consul.serf.snapshot.appendline.median
(gauge)
[DogStatsD only] The median of the time taken by the Consul agent to append an entry into the existing log.
Shown as millisecond
consul.serf.snapshot.compact.95percentile
(gauge)
[DogStatsD only] The p95 of the time taken by the Consul agent to compact a log. This operation occurs only when the snapshot becomes large enough to justify the compaction .
Shown as millisecond
consul.serf.snapshot.compact.avg
(gauge)
[DogStatsD only] The avg of the time taken by the Consul agent to compact a log. This operation occurs only when the snapshot becomes large enough to justify the compaction .
Shown as millisecond
consul.serf.snapshot.compact.count
(rate)
[DogStatsD only] The number of samples of consul.serf.snapshot.compact
consul.serf.snapshot.compact.max
(gauge)
[DogStatsD only] The max of the time taken by the Consul agent to compact a log. This operation occurs only when the snapshot becomes large enough to justify the compaction .
Shown as millisecond
consul.serf.snapshot.compact.median
(gauge)
[DogStatsD only] The median of the time taken by the Consul agent to compact a log. This operation occurs only when the snapshot becomes large enough to justify the compaction .
Shown as millisecond

Consultez la documentation relative à la télémétrie de Consul pour obtenir la description des métriques envoyées par l’agent Consul à DogStatsD.

Consultez la documentation relative aux coordonnées réseau de Consul pour découvrir comment les métriques de latence réseau sont calculées.

Événements

consul.new_leader :
L’Agent Datadog génère un événement lorsque le cluster Consul élit un nouveau leader, et lui attribue les tags prev_consul_leader, curr_consul_leader et consul_datacenter.

Checks de service

consul.check :
L’Agent Datadog envoie un check de service pour chaque check de santé de Consul, et lui attribue les tags :

  • service:<nom> si Consul transmet un ServiceName
  • consul_service_id:<id> si Consul transmet un ServiceID

Dépannage

Besoin d’aide ? Contactez l’assistance Datadog.

Pour aller plus loin