mirror of https://github.com/status-im/consul.git
/docs/agent
This commit is contained in:
parent
add1b0a61c
commit
f91f01c891
|
@ -1,12 +1,11 @@
|
|||
---
|
||||
layout: docs
|
||||
page_title: Configuration Entries
|
||||
page_title: How to Use Configuration Entries
|
||||
description: >-
|
||||
Consul allows storing configuration entries centrally to be used as defaults
|
||||
for configuring other aspects of Consul.
|
||||
Configuration entries define default properties for Consul components. Learn how to use the `consul config` command to create, manage, and delete configuration entries.
|
||||
---
|
||||
|
||||
# Configuration Entries
|
||||
# How to Use Configuration Entries
|
||||
|
||||
Configuration entries can be created to provide cluster-wide defaults for
|
||||
various aspects of Consul.
|
||||
|
|
|
@ -1,13 +1,11 @@
|
|||
---
|
||||
layout: docs
|
||||
page_title: Agent
|
||||
page_title: Agents Overview
|
||||
description: >-
|
||||
The Consul agent is the core process of Consul. The agent maintains membership
|
||||
information, registers services, runs checks, responds to queries, and more.
|
||||
The agent must run on every node that is part of a Consul cluster.
|
||||
Agents maintain membership, register services, respond to queries, and make most of Consul’s functions possible. Learn how to start, stop, and configure agents, as well as their requirements and lifecycles.
|
||||
---
|
||||
|
||||
# Consul Agent
|
||||
# Agents Overview
|
||||
|
||||
This topic provides an overview of the Consul agent, which is the core process of Consul.
|
||||
The agent maintains membership information, registers services, runs checks, responds to queries, and more.
|
||||
|
|
|
@ -1,11 +1,8 @@
|
|||
---
|
||||
layout: docs
|
||||
page_title: RPC
|
||||
page_title: Legacy RPC Protocol
|
||||
description: >-
|
||||
The Consul agent provides a complete RPC mechanism that can be used to control
|
||||
the agent programmatically. This RPC mechanism is the same one used by the CLI
|
||||
but can be used by other applications to easily leverage the power of Consul
|
||||
without directly embedding.
|
||||
Consul agents originally could be controlled through the RPC protocol. This feature was deprecated in version 0.8 in favor of the HTTP API. Learn about agent RPC interactions and how they worked.
|
||||
---
|
||||
|
||||
# RPC Protocol
|
||||
|
|
|
@ -1,13 +1,11 @@
|
|||
---
|
||||
layout: docs
|
||||
page_title: Sentinel in Consul
|
||||
page_title: Sentinel ACL Policies (Enterprise)
|
||||
description: >-
|
||||
Consul Enterprise uses Sentinel to augment the built-in ACL system to provide
|
||||
advanced policy enforcement. Sentinel policies can currently execute on KV
|
||||
modify and service registration.
|
||||
Sentinel allows you to include conditional logic when formatting policies. Learn how Consul can use Sentinel policies to extend the ACL system's capabilities.
|
||||
---
|
||||
|
||||
# Sentinel Overview
|
||||
# Sentinel ACL Policies
|
||||
|
||||
<EnterpriseAlert />
|
||||
|
||||
|
|
|
@ -1,13 +1,11 @@
|
|||
---
|
||||
layout: docs
|
||||
page_title: Telemetry
|
||||
page_title: Agents: Enable Metrics
|
||||
description: >-
|
||||
The Consul agent collects various runtime metrics about the performance of
|
||||
different libraries and subsystems. These metrics are aggregated on a ten
|
||||
second interval and are retained for one minute.
|
||||
Configure agent telemetry to collect operations metrics you can use to debug and observe deployments. Learn about configuration options, the metrics you can collect, and why they're important.
|
||||
---
|
||||
|
||||
# Telemetry
|
||||
# Agent Telemetry
|
||||
|
||||
The Consul agent collects various runtime metrics about the performance of
|
||||
different libraries and subsystems. These metrics are aggregated on a ten
|
||||
|
|
Loading…
Reference in New Issue