This query function counts the number of events in the repository, or
streaming through the function. Result is put in a field named,
_count. You can use this field name to pipe the results
to other query functions or general use.
It's possible to specify a field and only events containing that field are counted. It's also possible to do a distinct count. When having many distinct values Humio will not try to keep them all in memory. An estimate is then used, so the result will not be a precise match.
|string||false||_count||The name of the output field.|
|boolean||false||When specified, counts only distinct values. For many distinct values, Humio uses an estimate, which may return an inexact result.|
|string||false||The field for which only events are counted.|
Below are several examples using the
function. Some are simple and others are more complex, with functions
embedded within others.
Count All Events
Figure 251. Count All Events
Below is a simple example using the
function. The query just counts the number of events found in the
repository for the period of time selected. See
Figure 251, “Count All Events” for how
the following query is entered (see highlighted text):
The results is just a single number, the total count; this is how it displays it.
Group & Count
Figure 252. Group Count
In this example, the query uses the
function within the
groupBy() function. The first
parameter given is the field upon which to group the data. In this
case, it's the
http method (e.g.,
POST). The second parameter says to use the
count() to count the number occurrences
for each method found.
Figure 252, “Group Count” shows how this
query would be entered on the Search page for a repository — see
the highlighted text. It shows in the results a table with the column
with the values for each.
Chart of Daily Counts
count() Chart of Daily Counts
You can use the
count() function in conjunction
timeChart() function to count the number
occurrences of events or other factors. By default, the
timeChart() function will aggregate the data by
day. The results will look something like what you see in the
screenshot shown in
Figure 253, “
count() Chart of Daily Counts”.
Table of Daily Counts
Figure 254. Table of Daily Counts
When a user accesses a web site, the event is logged with a status
code. For instance, the status code
200 is returned
when the request is successful, and
404 when the
page is not found. To get a list of status codes returned and a count
of each for a given period, you would enter something like the
following in the query input box:
You can see an example of this query in
Figure 254, “Table of Daily Counts”. Notice
that in the results there is a table with the column headings
_count, and the
values for each status code in the rows below them.