Skip to main content

Graph Lakehouse Deployment with continuous logging

Overview and Use case​

This Custom Resource (CR) manifest defines a Graph Lakehouse database deployment configured with an integrated logging sidecar. This use case supports production observability pipelines where database engine logs, management daemon logs, and UDX execution logs need to be captured and streamed to centralized logging platforms.

Key Highlights​

  • Automated Sidecar Activation: Setting deployLoggerSidecar: true instructs the operator to spin up and orchestrate the sidecar logging lifecycle.
  • Multi-Container Pod Spec: Declares both the primary database container (anzograph-db) and the dedicated log forwarder (logger using Fluent-Bit) inside the StatefulSet pod template.
  • Log Stream Capture: Automatically links log volumes and parsing configurations for engine logs (boot.log, azgmgrd.log) and custom extensions (java-udx.log, cplus-udx.log).
  • Standardized Resource Allocation: Configures independent resource requests and limits for both application and sidecar containers.

Custom Resource Definition​

apiVersion: anzograph.clusters.cambridgesemantics.com/v2
kind: AnzoGraph
metadata:
name: azg-logger-sidecar
namespace: "${NAMESPACE}"
spec:
db:
licensing:
licenseType: CSI
csi:
legacyLicense: "${CSI_LICENSE}"
deployLoggerSidecar: true
nodeConfig:
spec:
replicas: 1
serviceName: anzograph-azg-logger
selector:
matchLabels:
app_mgmt: anzograph-mgmt-grpc
app_data: anzograph-data-grpc
template:
metadata:
labels:
app_mgmt: anzograph-mgmt-grpc
app_data: anzograph-data-grpc
spec:
serviceAccountName: anzograph-operator
containers:
- name: anzograph-db
image: aartifacts.altair.com/graph-docker/anzograph-db:3.5.0
imagePullPolicy: Always
resources:
requests:
cpu: "2000m"
memory: "9000Mi"
limits:
cpu: "16000m"
memory: "48000Mi"
- name: logger
image: artifacts.altair.com/graph-docker/fluent-bit:4.2.5
imagePullPolicy: Always
resources:
requests:
cpu: "2001m"
memory: "2001Mi"
limits:
cpu: "16000m"
memory: "48000Mi"