Settings–User Interface

After selecting a repository in the User Interface, you can go to the Settings tab to set some basic information and user permissions, and to get authentication tokens for other software to access the repository.


Figure 1, Setting Basin Information

In Figure 1 here is a screenshot of the Settings tab, specifically the General section where you may enter some Basic Information on the repository you’ve selected earlier. As you can see, the first input box is for entering a description of the repository. This description, along with the name of the repository, will appear on the Repositories tab when you first log into the Humio Interface.

When you select a repository, you’re taken directly to the Search tab. If the box for Automatic Search isn’t checked, no search will be run automatically. By checking the box, the default search will be run—which initially will be to show all events for the repository. If there’s a search you want to start by default, you can save it in the Search tab (see Search page). Then you can choose it here from the list under Default Query, as you can see we’ve done in the Figure 1.

Access Control, Basic Information

Figure 2, User Permissions

While still on the Settings tab for a particular repository, you can control access to the repository. Click on Users under Access Control and you’ll be able to add users and set permissions for them.

To add a user, click on the button labeled, + Add. A small dialog box will appear in which you can enter either the email address or user name for the user. This is what they will enter when logging into the Humio User Interface. You won’t be able to set their password here: the user will do that when they first log in.

Once you create a user, you can then click on the user’s name to see what permissions they have. A new user will initially be given a Member role, giving them very few privileges—mainly, the ability to view and search data. For a user with the Admin role, you’ll see a screen similar to the one in Figure 2 here. You can see what privileges it has in the screenshot. Notice the other user role is Eliminator. This type of user is the only one that can delete data. A user can be designated one, two, or three roles—or none.

To change a user’s role, click on the user’s name and then the text where it says, Edit user permissions… You can only set roles here. There’s no where you can edit or create roles. You can remove a user here, though.


The process of receiving data into a repository from a server or an application is known as ingesting data. So that data will load automatically, so that it will stream into your repository, you’ll first need an encryption key to pass to your server or app, for it to use when authenticating with Humio.

API Tokens

Figure 3, Ingest - API Tokens

To get an encryption key or token, click on the link labeled API Tokens, in the left margin of the User Interface labeled, under Ingest (see Figure 3 here). There will be a default token already generated for you. However, you may want to create more tokens, perhaps one for each log shipper (i.e., the software on your server that sends the data to Humio).

To create an API token, first enter whatever you want to name the token. It can be anything, but should be something you’ll recognize. Then click +Create Token. You’ll see the tokens you created, along with the default one, listed on the same panel. In Figure 3 you can see that we created two tokens and associated parsers for each. These are related to the type of data they will sending Humio. See the Parser page for more information on them.

To copy the key, you can click on the double-page icon for the token, under the Copy column. Or you click on the eye icon under the Token column, as shown in Figure 3, and copy the contents.

Data Sources

Figure 4, Ingest - Data Sources

Humio segments data into indexes called, data sources. They’re created automatically as data is ingested into the repository. You can’t create them in this section of the User Interface. You can only delete them. You might do this if a data source is old and no longer needed and you want to save the space.

Notice in the screenshot shown in Figure 4, it shows that each data space has at least one tag associated with it. Starting in version 1.19 of Humio, you’ll be able to create your own tags and assign them to events. See the Tagging documentation page for more information on tags.


Figure 5, Data - Archiving


This feature is not supported within the Humio Community Edition

The last section of the Settings in the User Interface is the Data section. In the previous section we mentioned the possibility of deleting data sources to save space in your repository. You can also use Amazon’s S3 Archiving service to archive old data. Archived logs will still be available for processing in any external system that integrates with S3.

As for the input boxes in the User Interface, enter the name of the S3 Bucket you want to use. Then the Amazon region where the server is located (e.g., eu-central-1). Next, choose the format for the archives files: Raw or NDJSON by default. When you’re done, hit Save.