Environments

September 13 Bullet_white By Andre Bullet_white Posted in Features Bullet_white Comments Comments

With the introduction of server roles, we made it easier to manage large setups. Most Scout customers have multiple servers of each type (example: app1, app2, app3), and roles have been a big hit:

72%
of new accounts use roles

But, we got some feedback

You said you needed flexibility on alerts, even when servers are in the same role. An application server in staging has different alerting needs than an application server in production.

Introducing environments

Now you can assign environments to your servers in Scout, and manage notifications accordingly:

  • create any number of environments (production, development, etc).
  • apply roles across environments. For example, production and staging servers can both be part of your "database" role.
  • customize notification settings by environment
  • filter your account homepage by environment. You'll see only the servers you want to see, with less noise.

Here's an example of a trigger with notification groups customized by environment:

Get Started

First, select Environments from the account menu, and create one or more environments.

Next, specify an environment with the agent's -e parameter on your server. You'll need the Scout agent version of at least 5.7.0 to use environments.

Don't need environments yet? They'll stay out of your way

If you're using Scout in only one environment, the new feature won't add any complexity. You'll only see the new settings after you've added multiple environments via the account menu.

Learn more

Read up on environments in our docs.

Get notified of new posts.

Once a month, we'll deliver a finely-curated selection of optimization tips to your inbox.

Comments

comments powered by Disqus