# Causely documentation: goals > Full content of the "goals" section of the Causely documentation. This file contains all documentation content in a single document following the llmstxt.org standard. ## Accelerate Resolution This page explains how Causely helps you accelerate incident resolution by providing precise Diagnosis insights when you need them most, reducing alert noise, and enabling faster problem resolution. Once you've [installed Causely](/getting-started/quick-setup), the system automatically generates your topology graph and infers Diagnoses that explain observed Signals. For more details on how Causely builds this understanding, see [How Causely Works](/getting-started/how-causely-works). ### Configure Workflow Notifications To receive Diagnosis insights during incidents, configure a workflow integration such as [Slack](/workflows/slack), [Microsoft Teams](/workflows/microsoft-teams), or [Alertmanager](/workflows/prometheus-alertmanager/). See the [workflows overview](/workflows) for all available integrations. #### Noise Reduction When incidents occur, Causely sends notifications for your Issues, including their Diagnoses, directly to your configured workflow. Unlike traditional alerting systems that create alert storms with one alert per Signal, Causely sends a single Issue notification that explains multiple Signals. This dramatically reduces noise and helps you focus on what actually matters. #### Example As an example, Causely sends a message to slack about a [`Slow Consumer`](/reference/root-causes/applications/#slow-consumer), which is the cause of 7 Signals across multiple services and key customer interactions. ### Use Issue View for Fast Resolution The [Issue view](/in-action/root-causes) provides detailed information about each identified Diagnosis: - **Evidence**: Metrics, logs, and traces that support the inference - **Impact**: Which services, entities, and operations are affected (blast radius) - **Causality Graph**: Visual representation of how the cause relates to Signals - **Remediation Guidance**: Actionable remediation steps tailored to the specific issue Urgent Issues are marked red and indicate problems currently impacting your services and SLOs. Use this view to quickly understand what's wrong, why it's happening, and how to fix it. ### Improve Resolution Speed To further accelerate resolution: - **Define service priorities**: Configure [service tiers](/configuration/service-tiers) to help Causely prioritize which services matter most when identifying urgent Diagnoses. - **Connect more telemetry**: Add additional [telemetry sources](/telemetry-sources) to provide more comprehensive coverage and more accurate Diagnoses. More telemetry means more accurate and complete causal insights. - **Configure thresholds**: Set up [thresholds](/configuration/thresholds) to fine-tune when Signals are considered problematic, helping Causely better identify urgent issues. - **Configure Signal activation delay**: Adjust [Signal activation delay](/configuration/symptom-delay) to balance between quick detection and reducing false positives. Shorter delays (1-3 minutes) enable faster Diagnosis for critical services, while longer delays (5-10 minutes) help filter out temporary spikes. - **Set up SLOs**: Configure [SLOs](/configuration/slo-configuration) to help Causely understand your reliability goals and better identify when Diagnoses are putting your SLOs at risk. ### Related Features - [Issues](/in-action/root-causes) - Explore all identified Issues - [MCP Server](/agent-integration/mcp-server/) - Query the system during incidents - [Topology](/in-action/topology) - Investigate affected entities - [Workflows](/workflows) - Configure notifications --- ## Optimize Performance This page explains how Causely helps you continuously improve system performance by providing actionable insights into bottlenecks, inefficiencies, and optimization opportunities. Once you've [installed Causely](/getting-started/quick-setup), the system automatically generates your topology graph and identifies performance bottlenecks, resource contention, and optimization opportunities. For more details on how Causely builds this understanding, see [How Causely Works](/getting-started/how-causely-works). ### Identify Performance Issues Causely identifies performance issues through root cause analysis that reveals: - **Resource contention and bottlenecks**: Understand where resources are constrained and causing performance degradation - **Inefficient operations and queries**: Identify operations that are consuming excessive resources or taking too long - **Scaling opportunities**: Find services or components that would benefit from scaling - **Optimization targets**: Pinpoint specific areas where performance improvements would have the most impact The [Issues view](/in-action/root-causes) shows performance-related Issues with detailed evidence, impact analysis, and remediation guidance. ### Track Performance Trends Use historical Issues and the [Topology view](/in-action/topology) to track performance trends over time and understand: - **How changes impact performance**: See how deployments, configuration changes, or infrastructure updates affect system performance - **Seasonal or cyclical patterns**: Identify recurring performance patterns that might indicate optimization opportunities - **Long-term degradation or improvement**: Track whether performance is improving or degrading over time The [Reliability Delta](/in-action/reliability-delta) feature allows you to compare performance snapshots and track improvements or regressions. ### Get Actionable Recommendations Issues include specific remediation guidance that helps you optimize performance, such as: - Scaling recommendations for services or infrastructure - Query optimizations for databases - Infrastructure improvements - Configuration adjustments You can also use your favorite AI agent through our [MCP Server](/agent-integration/mcp-server/) to query performance-related questions and get insights about optimization opportunities. ### Improve Performance Optimization To better identify and act on performance optimization opportunities: - **Connect more telemetry**: Add additional [telemetry sources](/telemetry-sources) to provide more comprehensive performance data. More telemetry means better identification of bottlenecks and optimization targets. - **Configure thresholds**: Set up [thresholds](/configuration/thresholds) to fine-tune when performance issues are considered problematic, helping Causely better identify optimization opportunities. - **Define service priorities**: Configure [service tiers](/configuration/service-tiers) to help Causely prioritize which services' performance matters most. - **Automate remediation**: Use [Automate Remediation](/in-action/automate-remediation) to automatically scale resources or take other actions when performance issues are identified. ### Related Features - [Issues](/in-action/root-causes) - Find performance-related Issues - [Automate Remediation](/in-action/automate-remediation) - Automatically scale resources - [Topology](/in-action/topology) - Analyze entity performance metrics - [MCP Server](/agent-integration/mcp-server/) - Query performance-related questions --- ## What are your goals? --- ## Proactively Prevent Incidents This page explains how Causely enables proactive incident prevention by identifying emerging risks before they impact your services and SLOs, helping you address issues before they escalate into incidents. Once you've [installed Causely](/getting-started/quick-setup), the system automatically generates your topology graph and infers both urgent Diagnoses and non-urgent Diagnoses (emerging risks). For more details on how Causely builds this understanding, see [How Causely Works](/getting-started/how-causely-works). ### Configure Workflow Notifications To receive Diagnosis insights, configure a workflow integration such as [Slack](/workflows/slack), [Microsoft Teams](/workflows/microsoft-teams), or [Alertmanager](/workflows/prometheus-alertmanager/). See the [workflows overview](/workflows) for all available integrations. Causely sends **urgent Issues** directly to your configured workflow when incidents occur, helping you [accelerate resolution](/goals/accelerate-resolution). Additionally, Causely continuously creates **non-urgent Issues** that often call out reliability issues and emerging risks before they escalate into incidents. ### Identify Emerging Risks Causely continuously monitors your environment and identifies potential issues before they escalate into incidents. Non-urgent Issues often represent emerging risks that can be addressed proactively. These are Issues that are active but not yet impacting your services and SLOs. By detecting issues early, Causely helps protect your Service Level Objectives (SLOs) and error budgets. You can address problems before they impact user experience or violate SLO commitments. ### Monitor Trends and Patterns Use the [Issue view](/in-action/root-causes) to monitor patterns and trends over time. Review historical Issues to identify: - Recurring issues that might indicate systemic problems - Gradual degradation that might not trigger immediate alerts but could lead to problems - Patterns that help you understand your system's behavior over time The [Reliability Delta](/in-action/reliability-delta) feature helps shift reliability left by allowing you to compare reliability snapshots and track improvements or regressions over time. Before deploying changes, you can create a snapshot to establish a baseline. After deployment, compare the new snapshot to identify any reliability regressions. ### Improve Prevention To better identify and prevent incidents: - **Configure workflow connections**: Set up workflow integrations such as [Slack](/workflows/slack), [Microsoft Teams](/workflows/microsoft-teams), or [incident.io](/workflows/incident-io) to receive both urgent and non-urgent Diagnosis notifications. This ensures you're notified about emerging risks as soon as they're identified. - **Configure SLOs**: Set up [SLOs](/configuration/slo-configuration) to help Causely understand your reliability goals and better identify when Diagnoses are putting your SLOs at risk, even before they become urgent. - **Set thresholds**: Configure [thresholds](/configuration/thresholds) to fine-tune when Signals are considered problematic, helping Causely identify emerging risks earlier. - **Connect more telemetry**: Add additional [telemetry sources](/telemetry-sources) to provide more comprehensive coverage and more accurate Diagnoses. More telemetry means earlier detection of potential issues. - **Define service priorities**: Configure [service tiers](/configuration/service-tiers) to help Causely prioritize which services matter most when identifying risks. ### Related Features - [Reliability Delta](/in-action/reliability-delta) - Compare reliability snapshots - [Issues](/in-action/root-causes) - Review non-urgent Diagnoses and emerging risks - [Configuration](/configuration) - Set up thresholds and SLOs --- ## Scale Reliability This page explains how Causely helps you maintain reliability across complex, fast-changing systems at scale by automatically understanding your entire environment and reducing alert noise. Once you've [installed Causely](/getting-started/quick-setup), the system automatically generates your topology graph and infers Diagnoses, even as your system grows and changes. For more details on how Causely builds this understanding, see [How Causely Works](/getting-started/how-causely-works). ### Automatic Discovery at Scale As your system evolves, Causely automatically discovers new services, entities, and relationships without manual configuration. This keeps your reliability insights current as you scale, whether you're: - Deploying new services or applications - Adding infrastructure components - Changing service dependencies - Scaling horizontally or vertically The system continuously updates its understanding of your environment, adapting to new deployments, releases, infrastructure changes, and performance patterns. ### Reduce Alert Noise At scale, alert noise becomes overwhelming. Traditional alerting systems create one alert per Signal, leading to alert storms that make it impossible to identify what actually matters. Causely reduces noise by inferring Diagnoses that explain multiple Signals. Instead of receiving hundreds of alerts, you get a single notification that explains the underlying issue. This helps you focus on what matters and maintain reliability even as your system grows. ### Improve Reliability at Scale To better maintain reliability as you scale: - **Connect more telemetry**: Add additional [telemetry sources](/telemetry-sources) to provide comprehensive coverage across your entire system. More telemetry means better discovery and more accurate Diagnoses. - **Configure scopes**: Set up [scopes](/configuration/scopes) to organize your entities and manage complexity as your system grows. - **Define service priorities**: Configure [service tiers](/configuration/service-tiers) to help Causely prioritize which services matter most, especially important at scale when you have many services. - **Set up SLOs**: Configure [SLOs](/configuration/slo-configuration) to help Causely understand your reliability goals across all your services and better identify when Diagnoses are putting your SLOs at risk. - **Use Reliability Delta**: Track reliability trends over time with [Reliability Delta](/in-action/reliability-delta) to understand how your system's reliability changes as it scales. ### Related Features - [Topology](/in-action/topology) - View all discovered entities - [Reliability Delta](/in-action/reliability-delta) - Track reliability at scale - [Configuration](/configuration) - Configure scopes and service tiers --- ## Understand System Behavior This page explains how Causely provides deep insights into why your systems behave the way they do by applying its causal models to your entire environment, producing a live causality graph that is queryable. Once you've [installed Causely](/getting-started/quick-setup), the system automatically generates your topology graph and builds a comprehensive understanding of your system's behavior and relationships. For more details on how Causely builds this understanding, see [How Causely Works](/getting-started/how-causely-works). ### Explore Your System Topology The [Topology view](/in-action/topology) provides a comprehensive view of your entire system. You can explore: - **Service dependencies and relationships**: Understand how services connect and depend on each other - **Data flow across operations**: See how data moves through your system - **Infrastructure stack**: View the infrastructure components that support each entity - **Historical behavior patterns**: Analyze how your system has behaved over time This topology graph forms the foundation for understanding system behavior, blast radius analysis, causal attribution, and cross-service impact modeling. ### MCP Server Use your favorite agent with our [MCP Server](/agent-integration/mcp-server/) to query your system's behavior using natural language. Ask questions like: - "Why is service X slow?" - "What changed in the last hour?" - "Show me the dependencies for service Y" - "What's causing the latency in my API?" Causely uses its causality graph to provide intelligent answers about your system's behavior, helping you understand not just what happened, but why it happened. ### Improve Understanding To gain deeper insights into your system: - **Connect more telemetry**: Add additional [telemetry sources](/telemetry-sources) to provide more comprehensive coverage. More telemetry means a more comprehensive topology graph and better causal insights. - **Configure scopes**: Set up [scopes](/configuration/scopes) to organize your entities and focus on specific parts of your system. - **Use MCP Server regularly**: Regularly query your system to build familiarity with how it behaves and to identify patterns and relationships. ### Related Features - [Topology](/in-action/topology) - Browse system entities and relationships - [MCP Server](/agent-integration/mcp-server/) - Query system behavior - [How Causely Works](/getting-started/how-causely-works) - Learn about causal models and the causality graph