Environments

Environments create groups of related incidents so that different users can focus on the most relevant incidents. You can define custom Environments based on the areas of responsibility and processes in your organization. The built-in All incidents Environment includes every incident.

To use Environments, click the Incidents tab at the top of the screen. Your Environments appear in the left pane.

Common Use Cases

Define custom Environments that help your users focus on the most relevant information to them. Common use cases include Environments that are based on areas of responsibility within IT and DevOps teams, processes, or escalation paths. For example, you can define an Environment for:

  • A DBA team that focuses on incidents related to production databases.

  • An engineering team that is responsible for incidents related to a particular set of applications.

  • Level-1 or NOC operators that work only on high-severity incidents.

  • The emergency contacts of a customer-facing service. Include only critical alerts from the service, and then set up an AutoShare to immediately notify the emergency contacts.

Enviroments in BigPanda

You can use Environments with several BigPanda features for enhanced efficiency and functionality.

Defining Environments

Define custom Environments to organize incidents based on the areas of responsibility and processes in your organization. You can also edit, duplicate, or delete Environments based on your needs.

Prerequisites

Defining New Environments

An Environment creates a group of related incidents by filtering on incident properties, such as source and attribute. You can define the rules that determine which incidents are included in an Environment. The rules construct a simple and/or boolean expression that is evaluated against the incident properties.

  1. At the top of the screen, click the Incidents tab.
  2. At the bottom of the left pane, click New Environment.
  3. Enter an Environment Name.
  4. Select a Source.

    • You can include all incidents from a source type (such as Nagios or New Relic).

    • Alternatively, you can include incidents only from a specific instance of the source type (for example, Nagios-US-EAST1).

  5. Decide which incident statuses to include.

    • Clear all of the check boxes to include only incidents with critical alerts.

    • Select the Warning check box to include warning alerts.

    • Select the Ack/Maintenance check box to include alerts that have been acknowledged in the source system and alerts that were sent during a scheduled maintenance window for the object.

Incidents with critical alerts are always included.

  1. (Optional) Define a dependent condition that filters incidents from the source you selected in Step 4. Skip this step to include all incidents from the selected source.

    • Click the plus sign inside the same box as the source.

    • Select a tag.

BigPanda normalizes alert data into attributes called tags. You can filter the incidents in the Environment by values in any standard or custom tags.

  • Select an operator.

  • Enter a value.

Matching Multiple Values And Using Wildcards

When using the Equals To or Not Equals To operators, enter the value you want to match. You can use an asterisk () as a wildcard to match multiple values that contain a common element. For example, entering hostname.suffix finds all values that end with hostname.suffix. Similarly, entering db-.domain.com finds all values that start with db- and end with domain.com.

When using the In or Not In operators, enter a comma-separated list of the exact values you want to match. Do not use spaces between comma-separated values. For example, enter host1.domain.com,host2.domain.com to find all incidents that match either host1.domain.com or host1.domain.com. You cannot use wildcards with the In List and Not In List operators.

  1. Add or remove conditions to construct the desired filter:

    • To add a top-level condition or another source, click Add Another, then repeat Steps 4 – 7.

    • To add a dependent condition for the same source, click the plus sign inside the same box as the source. Then, select a tag, select an operator, and enter a value.

    • To delete a condition, click the trash icon beside it.

Testing Filter Conditions

In the right pane, you can see a live preview of the incidents that match the current conditions.

  1. Click Save Environment. The Environment is saved and is listed in the left pane.

Filtering Logic For Incidents With Multiple Alerts

An incident is included in an Environment if at least one of the active alerts meets the filter criteria. For example, if you add a condition that the check value must be cpu, an incident that contains a cpu alert and a memory alert is included. Similarly, if you configure the Environment to include only critical alerts, an incident that contains one active critical alert and several warning alerts is included.

This logic provides you with maximum visibility into any incidents that are potentially related.

Managing Enviroments

On the left pane, point to the Environment name, and then click the gear icon. You can edit, duplicate, or delete an Environment.

Users can also maintain a personal list of their favorite Environments.

Post-Requisites

Example: Defining Environments By Areas Of Responsibility

You can create Environments based on the different responsibilities within your Ops teams. This example demonstrates how to define an Environment for a DBA team that focuses on incidents for production databases and related analytics applications.

Prerequisites

Defining The DBA Team Environment

  1. At the top of the screen, click the Incidents tab.
  2. At the bottom of the left pane, click New Environment.
  3. In Environment Name, enter DBA.
  4. In the Source field, select Nagios (ALL).
  5. Click the plus sign inside the same box as the source.
  6. Select the tag, select the operator, and enter the value as listed in a row of the following table.
Tag
Operator
Value

Host

Equals To

*db.*

Hostgroups

Not Equals To

staging

Check

Not Equals To

keepalive

These filter conditions are defined for a hypothetical sample environment. You can adapt the conditions as necessary to meet your infrastructure configuration and the needs of your teams.

  1. Repeat Steps 5 – 7 for each row in the table.
  2. Click Add Another. A new top-level condition box appears.
  3. In the Source field, select New Relic (ALL).
  4. Click the plus sign inside the same box as the source selected in step 9.
  5. Select the tag, select the operator, and enter the value as listed in a row of the following table.
  6. Repeat Steps 10 – 12 for each row in the table.
  7. Click Save Environment.
Tag
Operator
Value

Application

Equals To

Analytics

Description

Equals To

*ping*

Post-Requisites

Environment Groups

An Environment Group adds another level of hierarchy and is a category of one or more environment. It can be used to organize common functions, for example, business services, teams, and infrastructure areas.

The Environment Group is a title and not an actual environment, and therefore does not contain incidents.

The default Environment Group is called "General" and contains all environments not explicitly moved or created under a new group.

To avoid duplication, each environment can only be associated with one Environment Group.

An exception exists for environments that are specifically starred, as they will appear in both their assigned Environment Group and also in the pinned Starred section.

When hovering over an Environment Group's name, the option to Hide and Show its respective environment list appears.

Creating a New Environment Group

  1. Select the New Group link at the bottom of the Environments list in the left-most pane.
  2. Input a desired Name for the new group.
  3. Select Create Group.

Assigning an Environment to an Environment Group

  1. Hover over a desired Environment's name in the left-most pane.
  2. Select the Ellipsis (...) context link.
  3. Select Edit.
  4. Under the Apply to group dropdown, select the desired group name.
  5. Select Save Environment.

Environment Filtering

At the top of the Environments pane, a search bar is present to allow for filtering of environments. The filter is applied by querying Environment Names and is case insensitive. Matching results will appear in real-time.

This feature is particularly helpful for organizations with numerous environments and helps users to quickly isolate and refine the list.

Clearing the filter search bar will revert the list and show all environments.

Environments


Environments create groups of related incidents so that different users can focus on the most relevant incidents. You can define custom Environments based on the areas of responsibility and processes in your organization. The built-in All incidents Environment includes every incident.

Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.