Configuration Overview
Once Causely is deployed and connected to your telemetry, this section covers how to configure how it detects, prioritizes, and reasons about issues in your environment.
Alerts & Root Causes
Configure how external alerts are ingested and how Causely reasons about issues it doesn't automatically recognize:
- Alert Ingestion and Mapping: How Causely maps external alerts to entities and Signals so they participate in causal analysis
- Custom Causes: Define your own causes for alerts Causely does not automatically recognize
Reliability Prioritization
Configure which services matter most and how aggressively Causely detects and surfaces issues:
- Service Prioritization: Assign priority tiers to services so alerts and Diagnoses reflect what matters most
- SLO Targets and Burn Rates: Configure SLO targets and burn rate behavior for services, HTTP paths, RPC methods, and queues
- Thresholds: Configure the thresholds used for Signal detection and SLI-based SLO evaluation
- Signal Delay: Configure activation and deactivation delays to avoid reacting to temporary spikes
Many of these settings can be configured through the Causely UI, Kubernetes/Nomad/Consul labels, or the API. See each page for the methods it supports.
Views
- Scopes: Define custom scopes to focus on the subset of your topology that matters most to your role or current task
Discovery
- Credentials Autodiscovery: Add new scraping targets without updating the Causely configuration, by labeling the corresponding Kubernetes Secret
General Settings
Accessible through the Causely UI under Preferences:
- Screen View Mode: Choose the layout mode for large screens.
- Auto Refresh Interval: Choose the frequency at which the user interface views should refresh automatically.
Deployment Configuration
The Helm values file (causely-values.yaml) is the primary method for configuring your Causely deployment.
For a complete list of available configuration options, you can view your current values using:
helm get values causely --namespace causely --all
Read more about the Helm values configuration.