logz.io sub accounts

Back in February, we introduced a Sub Accounts feature that enables users to run sub-accounts under one single main account and allows for more efficient account control and management.

This lets people define different data volumes and retention periods for different environments under one main account. For example, under the main account, a manager could define one sub-account for development, one for staging, and another for production.

Let’s take a closer look.

Main Accounts vs. Sub Accounts

The Sub Accounts feature is accessed from the Logz.io Settings page.

In the Summary section at the top of the page, users can see their current data plan. In this example, the data plan in use is 5 GB per day with 14 days of retention.

manage sub accounts

The “Main Account” (displayed under the Summary section) has the ability to create and manage additional Logz.io sub-accounts as well as allocate different data volumes and retention periods accordingly.

Main accounts can have access to the data shipped to the sub-accounts, either by accessing the sub-accounts themselves or by viewing the data from within the same main account. This access depends on the settings configured when creating a sub-account (see below for more details).

As additional sub-accounts are added, they will be listed under the main account — each with details on the allocated data plan.

Adding a New Sub Account

Add new sub-accounts by hitting the Add Sub Account button.

add a new sub account

In addition to defining the name for the new sub-account, you can allocate the daily volume allowed for the new account as well as the retention period for the data. Of course, you cannot surpass the maximum amounts of data and retention for your overall Logz.io account.

As mentioned above, you also have the option to configure access to the data shipped to the new sub-account.

  • Selecting the “Enable Main account users…” check-box will allow all users of the main account to access the new sub-account (this is done by clicking the account name at the top-right corner of the UI and selecting the account from the drop-down menu)
  • Selecting the “Searchable from main account” check-box will allow you to view and search the logs shipped to the new sub-account from the same main account

Once created, the new sub-account appears under the main account with data volume and retention period information, an account ID, and a user token. The subaccount can be used just like any other Logz.io account — you can send logs, define users, create alerts, and more.

Summing It Up

Being able to logically differentiate logs according to the apps, services, teams, or the environments generating or managing them can help DevOps and IT operations teams analyze them more effectively.

Logz.io Sub-Accounts allows you to do exactly that.

Want Even More Capabilities From Your ELK Stack? Try Logz.io! Now with Sub-Accounts