Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.jitera.ai/llms.txt

Use this file to discover all available pages before exploring further.

Jitera Self-Hosted provides two complementary layers of monitoring:
  • Infrastructure monitoring — tracks the health of your Kubernetes cluster, pods, nodes, and data stores. Answers questions like “Is the system running?” and “Are resources sufficient?” This is provided by the in-cluster stack (Prometheus, Grafana, Loki) or your cloud provider’s managed services.
  • Application error tracking — captures unhandled exceptions and errors from Jitera’s application code (Automation, Ultron, Boost, Frontend). Answers questions like “Why did this user action fail?” and “Which code path threw an error?” This is provided by Rollbar.
Audit log forwarding to external destinations (AWS S3, Azure Data Explorer, Azure Blob Storage) is configured separately. See Audit Logging for details.

​
Infrastructure Monitoring

​
In-Cluster

The Helm chart includes a full observability stack — Prometheus, Grafana, Loki, Tempo, and OpenTelemetry — deployed directly into your cluster with a single toggle.

In-Cluster Monitoring

Deploy and configure the built-in monitoring stack: metrics, dashboards, log aggregation, distributed tracing, and health probes

​
Cloud Provider

Use your cloud provider’s managed monitoring services for integrated observability without deploying additional in-cluster components.

Cloud Provider Monitoring

AWS CloudWatch, Azure Monitor, and other managed monitoring services for EKS and AKS clusters

​
Application Error Tracking

Rollbar captures runtime errors and exceptions from Jitera’s application services. Use it when you need to diagnose application-level failures, track error trends, or receive alerts when new error types appear.

Error Monitoring (Rollbar)

Configure Rollbar error tracking across all Jitera services