Observability, security & storage

AlchemiStudio integrates with the SUSE platform stack for monitoring, runtime security, and storage.

Observability

AlchemiStudio ships its own OpenObserve (logs, metrics, traces) as part of the chart, and can also feed SUSE Observability (StackState).

• In-app: OpenObserve captures the platform’s logs/metrics/traces out of the box. Retention and alerting are configurable.
• SUSE Observability (StackState): deploy the SUSE Observability agent to add cluster topology, APM, and correlated traces across the whole cluster. AlchemiStudio can export OpenTelemetry to the SUSE Observability collector when you provide the endpoint and API key.

Validated: SUSE Observability (StackState 2.10.3) running with its agent capturing cluster topology and traces alongside AlchemiStudio.

Ship only the agent into a customer cluster and point it at their SUSE Observability server — never bundle the server itself.

Security — SUSE Security (NeuVector)

Run SUSE Security (NeuVector) for runtime container security, network policy, and vulnerability scanning across the cluster, including the AlchemiStudio workloads.

Validated: NeuVector deployed on the test cluster.

AlchemiStudio adds its own application-layer guardrails (PII, jailbreak, toxicity, content filtering, secret detection, topical) on top of platform security — the two are complementary.

Storage

File download is served through APISIX (/filestore) with signed access, so large artifacts stream through the gateway rather than exposing the object store directly.

Secrets

Provider secrets (LLM API keys, SMTP, etc.) can be supplied three ways:

1. Helm values → Kubernetes Secret (simplest).
2. OpenBao + External Secrets Operator — store in OpenBao, sync into Kubernetes Secrets (optional; gated by openbao.enabled / eso.enabled).

Back to AlchemiStudio on SUSE AI Factory · Support.