Skip to main content

Defining and managing Environments

Environments accumulate data, summarize it, visualize it and offer tools for managing it. An environment comprises all components which make up an application. To give you an example, when your application utilizes two separate Kubernets clusters you should add both to a single environment. All data is then aggregated within this environment and you start to manage all interactions across clusters.

In the navigation bar from the Dashboard the drop down menu Environments will show the name of the currently active Environment. Clicking on it opens a dropdown with link to Environments page. If you recently have been using other environments as well, you can find them in this list too.

Environments page

To create new Environment, click + Add environment button, and specify the name.

On the Environments page, you can manage your Environments. There are 4 options:

  • On/Off toggles allows you to start or stop loading the data for the Environment.
  • Settings will bring up the dialog to manage the Environment settings.
    • Change name and description of the Environment-
    • Manager users and teams
    • Manage cluster networks
    • Configure webhooks.
  • Load will select the Environment and you'll be able to view data for this Environment.
  • Delete allows you to delete the environment and all data associated with it.

Environment Settings

Each environment needs to have a name and an optional description. You can update these at any time in the Environment Settings dialog. Make sure to press save to persist the changes.

Network settings

Each environment can have multiple networks (clusters) which represent the application architecture. You can create a new network ID by clicking + Add network button. The network ID is used by the data plane to connect to the Glasnostic Cloud and send data to the correct environment.

Multiple clusters can be added into a single Environment. Each cluster should be identified by a unique network ID. This allows you to aggregate data across clusters and allows you to build resilient architectures where different components are hosted within different Kubernetes clusters.

When you install Glasnostic for Kubernetes, you provide the network ID during installation. The cluster will then connect and send data to the Environment with the specified network ID.


Permission management is done on the Environment level as well. You can assign different permissions to either individual users or a group of users, called a Team. There are three different levels of access you can assign to a User or Team.

  • Admin: Can manage the environment and apply control policies.
  • Write: Can view the environment and apply control policies.
  • Read: Can view the environment but not apply any policies.


Webhooks allow you to integrate with other services. For example, you can integrate with a monitoring service to send data from Glasnostic to your paging systems (e.g. PagerDuty). See the guide on Integrating with other services for more details.

Adding and managing webhooks is also done in the Envionrment settings dialog. Webhooks apply to the entire Environment, so data from all connected networks will be used to trigger webhook events.