Overview

Opsflw Connect ships a managed Elastic Stack cluster to centralize logs, metrics, and traces from every connected environment. The deployment follows a repeatable architecture so day-two operations stay predictable.

Cluster layout

• Ingest nodes scale horizontally to accept Beats, Elastic Agent, and API traffic.
• Data nodes store time-series indices with lifecycle policies tuned for 30-day hot, 90-day warm retention.
• Master nodes anchor cluster coordination and receive upgrades first during maintenance windows.

All nodes run inside hardened subnets with security groups allowing limited inbound ports. Outbound traffic routes through shared NAT gateways controlled by the network overview policies.

Deployment automation

The Elastic deployment is provisioned through Terraform modules managed in the Opsflw IaC repository. Pipelines ensure each change:

1. Validates the plan against staging.
2. Executes in production during an approved maintenance window.
3. Verifies cluster health and index lifecycle status before closing the change.

Integration points

• Control plane services ship audit logs through Beats shippers.
• Tenant workloads forward telemetry using fleet-managed Elastic Agents.
• Runbooks rely on Kibana dashboards for incident response and compliance reporting.

Continue with the profiles overview to understand how teams tailor Elastic access and dashboards per tenant.