The humio-usage Repository
humio-usage contains aggregated data based on measurements, used by the UI Usage Page. This repository is available directly to self-hosted customers. Cloud customers use the humio-organization-usage view. The logs in this repository are the results of an hourly query to the humio-measurements repository. It differs from the humio-measurements repository in the following: it has unlimited retention, data is being logged once every hour, and it does not include data on ingestion source. Moreover, the usage measurements are provided as fields in the log.
You can filter the logs by which repository they come from by using the repo field in the humio-usage repository.
The table below contains some of the more interesting fields a log line could have:
Field | Example Value | Explanation |
---|---|---|
#sampleRate | hour | To which period the values in this log pertain to. 1 hour in most cases. |
#sampleType | usageTag | If this log line refers to a repository, or a set of repositories that are grouped under the same usageTag. The value can be one of the following: organization, usageTag or repository. |
repo | your_repo_name | The repository name measurements in this log line pertain to, if #sampleType is repository. |
dataScanned | 123546 | The amount of data that was scanned in the last hour in #sampleType. |
ingestBytes | 23123 | The amount of data that was ingested to this #sampleType in the last #sampleRate, measured in bytes. |
segmentWriteBytes | 12313214 | The amount of data in bytes written to the disk in the last hour. |
storageSize | 129071068836 | Total disk usage in the #sampleType. |
queryStart | 2021-06-28T07:31:23.044Z | The time window beginning of querying the humio-measurements repository. |
queryEnd | 2021-06-28T07:31:23.044Z | The time window end of querying the humio-measurements repository. |
logId | 21 | The id that binds the logs of different #sampleType together. See the section on LogId below. |
LogId in LogScale Usage Repository
The logs with different #sampleTypes
share one value,
which is the logId.
#sampleType | processedEventsSize | logId |
---|---|---|
repository | 2909 | 2 |
repository | 1290 | 2 |
repository | 879 | 2 |
organization | 5078 | 2 |
By tracing the logId, it is possible drill down into usage, and find out what the usage was in a specific time period, down to an hour, by repository. Since there is unlimited retention on this repository, it is always possible to see usage from the beginning of your usage of LogScale.