NXLog Platform architecture on Kubernetes
With this deployment type, NXLog Platform runs in your Kubernetes cluster. You are responsible for administering the Kubernetes environment, including managing namespaces, persistent storage, and ingress configurations. This page describes the components and network configuration of the NXLog Platform stack.
Components
The following table lists the NXLog Platform components and their corresponding pods.
| Component | Pod(s) | Description |
|---|---|---|
Portal |
|
NXLog Platform UI and backend applications. |
Agent management |
|
Agent management UI and API. |
Log management |
|
ClickHouse and Portal application middleware that exposes HTTP APIs related to log search, log retention management, and custom dashboards. |
Agent relay |
|
NXLog Agent instances for collecting and processing internal and external telemetry data. |
Postgres |
|
Database for storing user-specific metadata, such as saved searches, custom dashboards, filters, and log retention. |
ClickHouse |
|
Database for log storage. |
Vault |
|
Manages secrets and protects sensitive data. |
Network
The NXLog Platform stack runs within a customer-managed Kubernetes cluster. The following diagram shows a non-exhaustive list of the network configuration:
The ingress controller routes incoming traffic to the NXLog Platform stack, such as:
-
Client requests to the NXLog Platform web interface.
-
NXLog Agent communication with agent management.
-
NXLog Agent forwarding logs to NXLog Platform.
Within the cluster, the portal and agent management pods communicate with the internal NXLog Platform resources, such as the configuration and logs databases.