DOCSEARCHbyAlgolia
Submit Docs

AppSignal Documentation

website·Indexed 39 days ago

https://docs.appsignal.com/

Documentation for AppSignal's application monitoring platform, covering error tracking, performance monitoring, and logging. Includes guides on alerting, anomaly detection, distributed tracing, browser monitoring, and custom instrumentation for Ruby, Elixir, and JavaScript applications.

Tokens
300.4K
Snippets
1.5K
Records
2.5K
Agent score
69%

What's inside AppSignal

  1. Overview of ignoring namespaces in AppSignal

    Ignoring namespaces allows you to filter out error and performance data for all actions within specified namespaces. This is an efficient alternative to ignoring many individual actions. Data from ignored namespaces is not sent to AppSignal servers and does not count toward your organization's billing plan. Note that custom metrics recorded within ignored namespaces will still be reported.

  2. Overview of AppSignal parameter filtering

    AppSignal collects request parameters, including form data (POST), query parameters, and route keys. To protect sensitive user-identifiable information (PII), you can configure a denylist of parameter keys to filter. When a key is matched, its value is replaced with [FILTERED] in the AppSignal dashboard, preserving the key for visibility while hiding the sensitive data.

  3. Overview of AppSignal Minutely Probes

    Minutely probes allow you to periodically send custom metrics to AppSignal. A user-defined function is executed asynchronously every minute (starting from the time the probe was created). You can globally enable or disable this feature using the enable_minutely_probes configuration option.

  4. Overview of AppSignal for Python

    AppSignal supports Python applications by leveraging OpenTelemetry's tracing component to collect and send error and performance data to the AppSignal platform.

  5. Overview of AppSignal for Elixir

    AppSignal provides an Elixir package for monitoring Elixir applications. It supports pure Elixir applications and the Phoenix framework out-of-the-box. For other frameworks or packages, custom instrumentation may be required.

  6. Overview of AppSignal Deploy markers

    Deploy markers are visual indicators in AppSignal graphs and the 'Deploys' section that mark a change in the deployed version of an application. They allow developers to group errors and performance issues within a specific time frame (from one deploy to the next). Deploy markers are required to enable backtrace links for an application. When a new deploy is detected, AppSignal starts a fresh list of incidents for that version.

  7. Overview of AppSignal MCP Authentication

    AppSignal MCP is available at the public HTTP endpoint https://appsignal.com/api/mcp. It supports two authentication methods:

    1. OAuth: The simplest setup. Users sign in via a browser. Access is granted at the application level and exposes all read and write tools.
    2. Bearer Token: Best for limiting agent capabilities. Users generate a long-lived MCP token with fine-grained permissions (read, write, or disabled) scoped to specific applications.

    To generate a Bearer token: Go to Account Settings > MCP Tokens in the AppSignal profile menu.

  8. Overview of AppSignal Active Job integration

    AppSignal integrates with Active Job to track job execution and events. It supports all standard Active Job adapters. For adapters that do not have a dedicated AppSignal integration (e.g., GoodJob), monitoring is performed via Active Job instrumentation. When Active Job metrics are detected, AppSignal automatically creates an Intelligence dashboard for visual monitoring.

  9. Overview of AppSignal Dashboard types

    AppSignal provides two types of dashboards for monitoring metrics:

    1. Custom Dashboards: User-created dashboards. You can create one by selecting Add dashboard in the app's sidebar and then using Add chart to visualize any metric the app reports (including custom metrics).
    2. Intelligence Dashboards: Automatically created by AppSignal when it recognizes metrics from supported integrations (e.g., Sidekiq, NGINX, Kubernetes, or AWS services). These are labeled Intelligence in the Dashboards section and are automatically maintained unless customized.

  10. Overview of ignoring actions in AppSignal

    The 'ignore actions' configuration option allows you to define a denylist of actions that AppSignal should ignore. Data from these actions will not be sent to AppSignal servers and will not count towards your organization's billing plan. If you are unsure of the exact action names to ignore, you can find them in the 'Action name' column of the Traces list under Performance in the AppSignal UI and copy them directly into your configuration. Note: This configuration is not available for Front-end JavaScript.

  11. Overview of AppSignal Logging

    AppSignal Logging consolidates application logs to allow for storage, viewing, and querying. It is designed to provide insights into application performance and behavior, complementing APM features by capturing events such as slow database queries, admin activity, and outgoing API calls.

  12. Overview of AppSignal Anomaly Detection

    Anomaly detection allows you to configure triggers that send notifications when a metric value crosses a defined threshold (e.g., error rate > 5% or free memory < 100 MB). AppSignal checks metric values once per minute. When a threshold is reached, an alert is opened and notifiers are notified; when the condition is no longer met, the alert is resolved and notifiers are notified again.