Applications (previously known as "sites", also referred to as "apps") are Ruby and Elixir applications monitored by AppSignal. Every application is unique by the combination of its name and environment.
A list of Applications appears on the Application index and in the application quick switcher. Every application has a parent organization, which can have multiple applications. (Exception: Organizations created by the Heroku add-on only support one application.)
- Registering applications
- Running multiple applications on one host
- Link templates
- Integrations (full list)
AppSignal will detect and register new applications when it receives data from the Application and not before it. Using the Ruby and Elixir installers this should be done automatically. When installing AppSignal manually, please use the demo command line tool (Ruby / Elixir) or start your application and perform some requests/jobs.
- "Demo application" - development
- "Demo application" - production
- "Demo application" - staging
- "Demo application" - test
When running multiple applications on one host some odd behavior may occur. This is because the default configuration of our AppSignal libraries assume a one application per host setting.
One common problem we've seen is that Applications start reporting under different names and/or environments. Such as an application switching between the staging and production environment after a deploy or restart of an application process or worker.
To allow AppSignal to be used for multiple applications on one host we need to set the
working_dir_path configuration option (Ruby / Elixir). Using this configuration option, set a working directory path per application so that the AppSignal agent will not stop agents for other Applications that are running.
Want to help us improve this documentation page? Create a pull request