Setup Organization Hierarchy

A hierarchy is used to organize your ingested data, and can be as simple or as complex as your workspace needs. In addition to making it easy/quick to filter data you query using the org tree, it also is the basis of limiting access to information to the users in your workspace.

To setup in the app, click the Configure sidebar button:

and then click the Organizations tab.

You can then create your hierarchical organizations as needed. There is already a root organization that matches your workspace name by default. Here is one example:

Consider how you want to control/grant access to data scope for other users. Users are granted permission to see any data in organizations they are granted access to and all related sub-organizations. Shape your organization hierarchy accordingly.

For dev/SRE teams, you might consider setting up different organizations for your different environments (dev, QA, staging, prod), different apps, and different regions, etc. For internal IT teams, you might consider setting up different organizations for different departments in your company. For MSPs, you could setup a different organization for each end-user client that you have (and for large clients that have multiple locations, you could setup sub-organizations representing locations if you wished).

As a best practice, you normally would not setup a different organization for each agent/device that collects log data. Each log event already records which system it was generated by, and a standard source field will include information about the source device that a log event was collected for. Organizations thus typically group data from multiple agents together.