Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Don't start for 'rails runner' and 'rails db' #2623

Merged
merged 1 commit into from
May 3, 2024
Merged

Commits on May 3, 2024

  1. Don't start for 'rails runner' and 'rails db'

    Add `Rails::Command::RunnerCommand` for `bin/rails runner` commands
    and `Rails::Command::RakeCommand` for `bin/rails db` command to the list
    of denylisted constants that will prevent the agent from autostarting
    when seen.
    
    Now when `bin/rails runner` and `bin/rails db` commands are ran, the
    agent will recognize those contexts and not start
    automatically.
    
    Older agent versions that are still supported by New Relic can update to
    the new list of denylisted constants by having the following line added
    to the `newrelic.yml` configuration file:
    
    ```yaml
    autostart.denylisted_constants: "Rails::Command::ConsoleCommand,Rails::Command::CredentialsCommand,Rails::Command::Db::System::ChangeCommand,Rails::Command::DbConsoleCommand,Rails::Command::DestroyCommand,Rails::Command::DevCommand,Rails::Command::EncryptedCommand,Rails::Command::GenerateCommand,Rails::Command::InitializersCommand,Rails::Command::NotesCommand,Rails::Command::RakeCommand,Rails::Command::RoutesCommand,Rails::Command::RunnerCommand,Rails::Command::SecretsCommand,Rails::Console,Rails::DBConsole"
    ```
    fallwith committed May 3, 2024
    Configuration menu
    Copy the full SHA
    00b6f72 View commit details
    Browse the repository at this point in the history