Containers

Containers represent a logical grouping of monitored infrastructure assets in the InfraSonar platform

Usage

Here's how InfraSonar uses containers:

• Grouping and managing assets: Containers act as organizational units for assets, collectors, alerts, notifications, rules and views.
• Querying and filtering: InfraSonar allows users to query containers and their associated data, such as IDs, alerts, assets, and collectors
• Configuration:
  • Containers have configurable properties like mode, properties, zones, external notification rules etc.
  • Authorizations, labels and conditions propagate form their parents to their children.
  • Authorization is inherited to "lower" containers. Inheritance can be "broken" down the chain.

The picture below outlines our container conceptually:

graph LR
  A[InfraSonar] --> B[container 1];
  B -->C((assets));
  A -->D[container 2];
  D -->E[container 2.1];
  D -->F[container 2.2];
  E -->G((assets));
  F -->H((assets));
  A -->I[container 3];
  I -->J((assets));
  I -->K[container 3.1];
  K -->L[container 3.1.1];
  L -->N[container 3.1.1.1];
  L -->O((assets));
  N -->S((assets));

Don't overthink this, InfraSonar makes it easy to move containers and assets. Labels and conditions can also be moved but only to an "upstream" parent.

Note

When you are new to InfraSonar and sign in for the first time, you will see the message:

Welcome to InfraSonar! It appears that you are not yet a member of an InfraSonar container. If you are a member of an organization that uses InfraSonar, ask for permission from an authorized person to add you to the relevant container. Otherwise, request a free demo via the website!

Service provider specific

Containers are a useful feature for managed service providers as it allows them to create a container per customer.

If you feel our container concept might fit your needs we suggest to use your top level container as an organization placeholder and not to add assets here.

An example hierarchy implementation for a service provider using an elaborate container hierarchy

graph LR
  A[InfraSonar] --> B[service provider];
  B --> C[internal infrastructure]
  B --> D[monitoring only]
  B --> E[managed service]
  C --> F((assets))
  D --> customer1[customer 1]
  D --> customer2[customer 2]
  customer1 --> I((assets))
  customer2 --> J((assets))
  E --> customer3[customer 3]
  customer3 --> K((assets))
  E --> customer4[customer 4]
  customer4 --> L((assets))
  E --> customer5[customer 5]
  customer5 --> M[development]
  customer5 --> N[acceptance]
  customer5 --> O[production]
  M --> Q((assets))
  N --> R((assets))
  O --> S((assets))

Limitations

A container can contain a maximum of 2.000 assets.

If you have the need to add more assets please reach out to support so we can discuss potential solutions.