When data is sent to Humio it will stored in a repository. This is how Humio organizes data and calls a collection of data. It’s a container for data with associated storage. Often there will be one physical repository per project or system. However, this may vary based on the data volume, user permissions and many other factors.
Within Humio, each repository has its own set of users, dashboards, saved queries, and parsers. In a repository, you can control data retention and create parsers to distinguish incoming data. Some of these steps and components are covered in this section of the Humio Documentation—some are covered in other sections.
When you first log into the Humio User Interface, you’ll see an opening page similar to the one shown in Figure 1 here. Click on it or any other image on this page to enlarge it.
Notice it shows a list of repositories—this account doesn’t have any views. To search the data contained in a repository, you would click on it’s name (e.g., Testeroo in the screenshot here). When you do, it will take you to the Search page. This is covered in the Search page of this section of the Humio Documentation.
Regarding the repositories shown, if you’re accessing Humio through a Humio Cloud account, you’ll see most of the repositories shown in Figure 1 here, but not Testeroo. That was created in the Getting Started tutorial in the Training section of the Humio Library.
humio-audit repository is where data internal to Humio is recorded. If you click on it, you’ll see that it shows log entries regarding you using the User Interface and other repositories. The humio-metrics shows Humio usage information. The
sandbox is reserved as a place for you to test Humio. You’ll have to set up log shippers to send data to this repository.
Although you might send actual server logs and metrics to the sandbox repository, you wouldn’t use it in production. Instead, when you’re ready, create a repository of your own—as we did when we created Testeroo, but name it something that doesn’t suggest it’s a test and not for production use.
Please note that to add a repository to a Humio Cloud account, at this time, you’ll have to ask Humio Support to do it for you. There are a couple of exceptions: Trial accounts may create a repository, in addition to the Sandbox—but only one. However, this feature is now available to some beta customers. Contact Humio Support if you want to join the beta testing of this upcoming feature.
To try this, click on the + Add Item icon. That will show a box similar to the one in Figure 2 here. Notice that you have the choice of creating a View or a Repository. We’ll stick with creating a repository—views are covered on the Views documentation page. If your account is new and a trial one, it’ll offer to let you create a temporary repository.
Choose Repository (or Trial Repository) to create a repository. This will lead to another screen that will ask you to name and describe the repository, like the one in Figure 3 here. As you can see, if you clicked on the image to enlarge it, we chose to name it Prognosticator. For more information on creating repositories, see the Create Repositories documentation page for more information.
When you’re finished, you would click + Create Repository. This will then bring you to a page in which you can set some basic information about the repository. You’ll also be able to get an encryption token for your server to use to send data to the repository. This is all covered on the User Interface Settings page of this section of the Humio Documentation. As for getting data into the repository, you will need to set up log shippers on your server. That’s outside the User Interface, so it’s covered in the Ingest Data and Log Shippers sections of the documentation.