> ## Documentation Index
> Fetch the complete documentation index at: https://docs.appsignal.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Ignore Actions

<Tip>
  Ignoring actions will **ignore error and performance data** from those
  actions. [Custom metrics data](/metrics/custom) and [logs](/logging)
  recorded in an action will still be reported.
</Tip>

There may be specific actions in your application you don't want to report to AppSignal. The most common use case is a web endpoint that your load balancer uses to check if your application is still responding or all actions that occur within your application's admin panel.

These endpoints may receive a lot of traffic but are not crucial endpoints to have AppSignal monitor and may disrupt the usability of metrics AppSignal provides you for your application's [namespaces](/application/namespaces).

# Ignoring Actions

<Tip>
  If you're unsure of the action names to configure in your application
  configuration, find the action name to ignore in your application on
  AppSignal.com, and copy it into your AppSignal configuration.
</Tip>

Specific actions can ignore actions by using the "ignore actions" option in your application's AppSignal integration configuration. The "ignore actions" configuration option allows you to define a denylist of actions you want to ignore. All actions in this list will be ignored, meaning the data from these actions will not be sent to the AppSignal servers and will not count towards your [organization's billing plan](https://www.appsignal.com/plans).

This guide will show you how to configure your ignore action denylist in the language your application uses:

* [Ruby](#ruby)
* [Elixir](#elixir)
* [Node.js](#nodejs)
* [Python](#python)
* [Go](#go)
* [Java](#java)
* [PHP](#php)

**Note:** This configuration is not available for Front-end JavaScript.

## Ruby

To ignore actions in Ruby, add the following to your AppSignal configuration file. The [`ignore_actions`][ruby ignore_actions] value is an Array of Strings.

The below example is for a Rails application.

<CodeGroup>
  ```ruby Ruby theme={null}
  Appsignal.configure do |config|
    config.ignore_actions += [
      "UptimeController#healthcheck",
      "AdminController#index",
      "Admin::UsersController#show"
    ]
  end
  ```

  ```yaml YAML theme={null}
  production:
    ignore_actions:
      - "UptimeController#healthcheck"
      - "AdminController#index"
      - "Admin::UsersController#show"
  ```
</CodeGroup>

If you use Sinatra or any other framework, use the HTTP method and path you used to specify your route, for example:

<CodeGroup>
  ```ruby Ruby theme={null}
  Appsignal.configure do |config|
    config.ignore_actions += [
      "GET /healthcheck",
      "GET /pages/:id",
      "POST /pages/create"
    ]
  end
  ```

  ```yaml YAML theme={null}
  production:
    ignore_actions:
      - "GET /healthcheck"
      - "GET /pages/:id"
      - "POST /pages/create"
  ```
</CodeGroup>

[ruby ignore_actions]: /ruby/configuration/options.html#option-ignore_actions

## Elixir

To ignore actions in Elixir, add the following to your AppSignal configuration file. The [`ignore_actions`][elixir ignore_actions] value is a List of Strings.

<CodeGroup>
  ```elixir Elixir theme={null}
  config :appsignal, :config,
    ignore_actions: ["AppsignalPhoenixExampleWeb.UptimeController#healthcheck", "AppsignalPhoenixExampleWeb.AdminController#index"]
  ```
</CodeGroup>

[elixir ignore_actions]: /elixir/configuration/options.html#option-ignore_actions

## Node.js

To ignore actions in Node.js, add the following to your AppSignal configuration file. The [`ignoreActions`][nodejs ignore_actions] value is an Array of Strings.

Action names are used to group errors and performance issues. Their names are usually a controller/endpoint or background job. You can see a list of these in the "Action name" column of the *Issue list* under [Performance](https://appsignal.com/redirect-to/app?to=performance) in the sidebar. To ignore a specific action, copy the name as it appears in the UI and add it to the `ignoreActions` option.

<CodeGroup>
  ```javascript Node.js theme={null}
  const { Appsignal } = require("@appsignal/nodejs");

  new Appsignal({
    // Other config
    ignoreActions: ["GET /pages/:id", "GET /healthcheck", "GET /admin"],
  });
  ```
</CodeGroup>

[nodejs ignore_actions]: /nodejs/3.x/configuration/options.html#option-ignoreactions

## Python

To ignore actions in Python, add the following to your AppSignal configuration file. The [`ignore_actions`][python ignore_actions] value is a list of strings.

Action names are used to group errors and performance issues. Their names are usually a controller/endpoint or background job. You can see a list of these in the "Action name" column of the *Issue list* under [Performance](https://appsignal.com/redirect-to/app?to=performance) in the sidebar. To ignore a specific action, copy the name as it appears in the UI and add it to the `ignore_actions` option.

<CodeGroup>
  ```python Python theme={null}
  from appsignal import Appsignal

  appsignal = Appsignal(
      # Other config
      ignore_actions=["GET /pages/:id", "GET /healthcheck", "GET /admin"]
  )
  ```
</CodeGroup>

[python ignore_actions]: /python/configuration/options.html#option-ignore_actions

## Go

To ignore actions in Go applications, configure the [`ignore_actions`][go ignore_actions] config option.

Action names are used to group errors and performance issues. Their names are usually a controller/endpoint or background job. You can see a list of these in the "Action name" column of the *Issue list* under [Performance](https://appsignal.com/redirect-to/app?to=traces) in the sidebar. To ignore a specific action, copy the name as it appears in the UI and add it to the `ignore_actions` option.

See the [Go configuration page](/go/configuration/options) for more information on how to configure OpenTelemetry for Go apps.

<CodeGroup>
  ```go Go theme={null}
  res := resource.NewWithAttributes(
  	attribute.StringSlice("appsignal.config.ignore_actions", []string{"GET /heath_check", "POST /ping"}),
  	// And other resource attributes
  )
  ```
</CodeGroup>

[go ignore_actions]: /go/configuration/options.html#option-ignore_actions

## Java

To ignore actions in Java applications, configure the [`ignore_actions`][java ignore_actions] option.

Action names are used to group errors and performance issues. Their names are usually a controller/endpoint or background job. You can see a list of these in the "Action name" column of the *Issue list* under [Performance](https://appsignal.com/redirect-to/app?to=traces) in the sidebar. To ignore a specific action, copy the name as it appears in the UI and add it to the `ignore_actions` option.

See the [Java configuration page](/java/configuration/options) for more information on how to configure OpenTelemetry for Java apps.

<CodeGroup>
  ```bash Bash theme={null}
  function encode() {
    echo -n "$@" | sed 's/,/%2C/g'
  }

  export OTEL_RESOURCE_ATTRIBUTES="\
    appsignal.config.ignore_actions=$(encode "UptimeController#healthcheck,AdminController#index"),\
    ..."
  ```
</CodeGroup>

### Read More {/* id: java-read-more */}

* Read more about the [Java `ignore_actions` config option][java ignore_actions].

[java ignore_actions]: /java/configuration/options.html#option-ignore_actions

## PHP

To ignore actions in PHP applications, configure the [`ignore_actions`][php ignore_actions] option.

<CodeGroup>
  ```php PHP theme={null}
  return [
      'ignore_actions' => ['GET /admin', 'GET /ignored-route'],
      // ... other options
  ];
  ```
</CodeGroup>

### Read More {/* id: php-read-more */}

* Read more about the [PHP `ignore_actions` config option][php ignore_actions].

[php ignore_actions]: /php/configuration/options.html#option-ignore_actions

[notifications]: /application/notification-settings.html