Support & Documentation
Follow

How Do I Setup Configuration for Different Environments?

It's often necessary to view or even monitor your app and servers differently based on which environment they live in. With Stackify, it's easy to filter your views and customize your application and server monitoring based on environment.

Something that is a little different about Stackify is that we like to think app-first in how we approach most monitoring situations. Rather than setting up multiple server monitoring templates for different types of servers and different environments, with customizations based on Apps installed per server, instead you can apply base server templates that factor in the server's role in a more generic sense (web server, database server), and the rest of your monitor configuration happens at the application configuration.

When you configure monitors for an application, which can include app monitoring, server monitoring, resource monitoring, error monitoring, and more, all of those monitoring configurations are applied everywhere that application is found, and can be configured to be different per environment or the same across environments. Those per-environment settings can include who is notified and what thresholds are used, among others.

This approach simplifies server templates drastically, and monitors applications and all of the resources they depend on consistently per application and per environment. Specify once per app and environment, and those settings are applied on every server and every instance of the application on every environment consistently and with no effort.

For a little more color on how environments, Apps, servers, and resources play together, read on for key points.  

Applying Monitors By Environment

Applying Monitors By Environment

By configuring Apps in a certain Environment, you can tailor monitoring differently than you would at the server level.  By performing Per-Environment configuration you can set up monitors independently for different Apps running on the same server.  A good practice to take advantage of this capability would be to create generic server templates for each server role, and then configure each App by its environment.        

To configure monitors for an App click the "Configure" button on the App Dashboard.  From here you can select which environment you wish to use.  In this window you can set up App monitors, Server monitors, Performance monitors, Custom Metrics, Error monitoring, Resources monitoring, and Notifications.  Once you configure these monitors here at the App level, they will be applied on every instance.

Save and Copy Across Environments

Save and Copy Across Environments

You can easily copy configuration items from one environment and apply it to another environment.  This makes configuration across multiple environments a quick process.

Viewing the Different Environments

Viewing the Different Environments

To see what environments your Web App is associated with, go to the Monitoring tab of the App Dashboard located in the Stacks page.  Here you will see the different environments that your App lives in, and you will notice that differences in monitors at the server level will also show up here under the active server monitors for each environment.

Filter Out Unwanted Environments in the Dashboard

Filter Out Unwanted Environments in the Dashboard

If you want to view a customized view of one environment in the dashboard, you can easily apply filters to isolate the data.  After applying the Environment filter, only data from the selected environments will appear in the App Dashboard.

Managing Access to Environments

Managing Access to Environments

By clicking the Cog wheel on the right, you can manage which role or user has access to a certain environment.  To learn more about this, look at Managing Users and Roles.

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request

Comments

Powered by Zendesk