Clients
The Clients console — connected edge nodes, remote command dispatch, host statistics and logs, and OpenStack interface/IP lookups.
The Clients console — connected edge nodes, remote command dispatch, host statistics and logs, and OpenStack interface/IP lookups.
Point an EDS cluster at another endpoints resource (backend-blue to backend-green, and back) for a blue/green release, from the elchi UI.
Point an Envoy EDS cluster at another endpoints resource (backend-blue to backend-green and back) with the Elchi automation API; every listener gets it at once.
Deploy services on an Elchi OS HA pair: one VIP for both members, on-link vs routed VIPs, floating next-hops, BGP and BFD, and standby-first changes.
An Elchi client's Network tab: netplan editing with rollback, static routes, routing policies and tables, and FRR/BGP with BFD, including VIP announcement.
How an Envoy edge host routes with one, two or three NICs: where listener VIPs live, reply and upstream paths, the default route, policy rules and BGP uplinks.
The Appliance tab of an Elchi OS client in the UI: release and boot slots, health, upgrades, firewall, network confirm, CIS check and support bundle downloads.
The Elchi OS management console: show, set and apply, network changes with commit-confirm, firewall, system, config, logs and diagnostics, with exact syntax.
Elchi OS is an edge appliance image bundling the Elchi agent and Shield WAF: what it includes, image formats, platforms, sizing, and when to use it.
The Elchi OS host firewall, open ports and who may reach them, outbound requirements, SSH and accounts, kernel settings, the CIS check and the support bundle.
Upgrade Elchi OS in place with A/B root slots, a health-gated trial boot and automatic rollback; update elchi-client or Shield alone; HA pair upgrade order.
Take an upstream endpoint (an IP or a hostname) out of rotation everywhere it is used in a project, and put it back, from the elchi UI.
Take an upstream IP or hostname (all ports or some) out of rotation everywhere it is used in an Elchi project, and put it back, with the automation API.
Search an Envoy listener's logs and access logs by time range with a histogram, field sidebar and query syntax, with totals and paging evaluated on the host.
The management console for a running Elchi fleet — deployed Envoy services, connected edge clients, and how the controller drives them.
Inspect and operate an Elchi OS HA pair on the appliance: show ha, system ha commands, elchi-client ha, the elchi-ha service, its files and the support bundle.
How HA pair members elect and take over, planned and forced failover, maintenance mode, flap suspension, replacing a member and upgrading a serving pair.
REST reference for HA pairs — list, create, update, delete, add a member, failover, maintenance, push, sync — and the HA client commands.
Active/passive pairs of Elchi OS edge appliances that share virtual IPs — how a pair elects its active member, fails over, and keeps services up without BGP.
Track a project's public and private IP blocks and addresses in Elchi, see which ones services hold and which are free, and pick one when deploying.
Watch an Envoy listener live: sampled requests flow through connection managers, domains, routes and clusters to endpoints, with rates, p99 and 5xx origin.
Pair statuses, member roles, alarms, heartbeat and data-plane indicators, and where HA state appears across the Elchi UI, audit log and metrics.
Elchi go-live checklist: TLS, HA, persistent datastores, hardening, monitoring, backups and Shield source-IP trust, plus a disaster-recovery runbook.
Project-wide Elchi reports: problems first, then traffic map, domains, certificates, security per filter chain, unused resources and changes, as CSV or JSON.
Tiered PromQL alerting rules for an Elchi platform: config health, Shield safety, collector backpressure and backend health, with starting thresholds.
The Services console — view deployed Envoy services, drill into a running Envoy, track configuration errors, and recover GSLB records.
Start an Elchi OS appliance in HA mode, create a pair from one or two clients, add or replace the second member, and tune heartbeat, fencing and next-hops.
Size an Elchi platform: CPU, memory and storage for the control plane, MongoDB, ClickHouse, VictoriaMetrics, the collector and Shield, and what grows.