Ignoring actions will ignore error and performance data from those actions. Custom metrics data and logs recorded in an action will still be reported.

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.

Ignoring Actions

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.

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. This guide will show you how to configure your ignore action denylist in the language your application uses:

Ruby
Elixir
Node.js
Python
Go
Java
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 value is an Array of Strings. The below example is for a Rails application.

Appsignal.configure do |config|
  config.ignore_actions += [
    "UptimeController#healthcheck",
    "AdminController#index",
    "Admin::UsersController#show"
  ]
end

production:
  ignore_actions:
    - "UptimeController#healthcheck"
    - "AdminController#index"
    - "Admin::UsersController#show"

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

Appsignal.configure do |config|
  config.ignore_actions += [
    "GET /healthcheck",
    "GET /pages/:id",
    "POST /pages/create"
  ]
end

production:
  ignore_actions:
    - "GET /healthcheck"
    - "GET /pages/:id"
    - "POST /pages/create"

Elixir

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

config :appsignal, :config,
  ignore_actions: ["AppsignalPhoenixExampleWeb.UptimeController#healthcheck", "AppsignalPhoenixExampleWeb.AdminController#index"]

Node.js

To ignore actions in Node.js, add the following to your AppSignal configuration file. The ignoreActions 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 Traces list under 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.

const { Appsignal } = require("@appsignal/nodejs");

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

Python

To ignore actions in Python, add the following to your AppSignal configuration file. The 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 Traces list under 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.

from appsignal import Appsignal

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

Go

To ignore actions in Go applications, configure the 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 Traces list under 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. See the Go configuration page for more information on how to configure OpenTelemetry for Go apps.

res := resource.NewWithAttributes(
	attribute.StringSlice("appsignal.config.ignore_actions", []string{"GET /heath_check", "POST /ping"}),
	// And other resource attributes
)

Java

To ignore actions in Java applications, configure the 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 Traces list under 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. See the Java configuration page for more information on how to configure OpenTelemetry for Java apps.

function encode() {
  echo -n "$@" | sed 's/,/%2C/g'
}

export OTEL_RESOURCE_ATTRIBUTES="\
  appsignal.config.ignore_actions=$(encode "UptimeController#healthcheck,AdminController#index"),\
  ..."

Read more about the Java ignore_actions config option.

PHP

To ignore actions in PHP applications, configure the ignore_actions option.

return [
    'ignore_actions' => ['GET /admin', 'GET /ignored-route'],
    // ... other options
];

Read more about the PHP ignore_actions config option.

Homepage

Guides

Ignore Actions

Ignoring Actions

Ruby

Elixir

Node.js

Python

Go

Java

Read More

PHP

Read More

​Ignoring Actions

​Ruby

​Elixir

​Node.js

​Python

​Go

​Java

​Read More

​PHP

​Read More

Ignoring Actions

Ruby

Elixir

Node.js

Python

Go

Java

Read More

PHP

Read More