Humio is a flexible log management solution. We have customers that use our cloud solution, on-prem solutions, and hybrids of both options. Consider what works best for your application and organization and we are happy to help you ind the set up to best suit your needs.
Moving to Humio is easy! We have several common integrations to bring your logs into Humio and we even have a guide on moving from Elastic Stack to Humio - it’s as easy as following a few steps to getting your logs flowing.
Humio was built with containerization in mind! With integrations and existing setup for Kubernetes, Humio is a solution focused on modern deployment solutions.
While this list is not exhaustive, Humio recommends Beats, Logstash, or Rsyslog for shipping your logs. We can take advantage of other solutions, but these are the most common we’ve experienced.
No. Syslog data is sent to humio using ingest listeners, which are not supported by Humio Cloud.
Humio integrates with several common notification methods including email, Slack, and external services like OpsGenie. If you need Humio to work with your particular notification system, please contact our support team.
“Repository” is the new term. What used to be a “dataspace” in Humio is now a Repository.
The HTTP API includes the path /api/v1/dataspaces/$REPOSITORY_NAME/ to be compatible with existing clients.
In this context, the $REPOSITORY_NAME variable is the name of the repository. (It used to be the name of the dataspace).
Humio runs on either or both IP versions, depending on what you specify using HUMIO_JVM_ARGS. By default the process binds on both IPv4 and IPv6.
If you use the Docker images provided by Humio for Kafka and Zookeeper, or run the “humio/humio” image that includes both of them, you need to make sure those processe also get the same options regarding IP protocol as the Humio process.
IPv4 Only:
HUMIO_JVM_ARGS=-Djava.net.preferIPv4Stack=true
KAFKA_OPTS=-Djava.net.preferIPv4Stack=true
ZOOKEEPER_OPTS=-Djava.net.preferIPv4Stack=true
IPv6 Only:
HUMIO_JVM_ARGS=-Djava.net.preferIPv6Addresses=true
KAFKA_OPTS=-Djava.net.preferIPv6Addresses=true
ZOOKEEPER_OPTS=-Djava.net.preferIPv6Addresses=true
In Humio you can detect when a host or some other log source stops
sending logs using the now() function and groupby:
groupby(host, function=max(@timestamp, as=@timestamp))
| missing:=(now()-@timestamp)>(5*60*1000)
| missing=true
The above query shows a line for each host that we have not heard from in the last 5 minutes (timestamps in Humio are in milliseconds). You should run the query as a live search in a time interval that is longer than you “missing” threshold - when the last log from a log sources is older than your search time interval the log source will disappear from the result.
We have had reports of browser extensions such as “uBlock Origin” and other plugins that modify the page mistakenly by removing or hiding parts of the UI. Try disabling the plugin(s) on the pages of Humio if you suspect something is wrong. And please notify the Humio team when it happens, as we can likely change the specific element in the Humio page to not get filtered.
We have had reports of browser extensions such as “LastPass” for Chrome and other plugins that scan and/or modify the page slow down the UI a lot: The extensions think they need to inspect the full page for every change to the page, and the Humio UI changes the page content a lot… Please disable all browser plugin(s) on the pages of Humio.
We have seen issues with browser extensions such as “Full Page Screenshot” making the grid flicker in and out of existence. Try disabling your browser extensions and see if the issue still occurs.
Yes, via our GraphQL API (you need to be a root user). Below is a curl example to get you going.
Example:
HUMIO_BASE_URL=<example: https://example.com>
API_TOKEN=<you can find this in your account details>
LICENSE=<your license string>
curl ${HUMIO_BASE_URL}/graphql \
-H "Authorization: Bearer ${API_TOKEN}" \
-H "Content-type: application/json" \
-d @- << EOF
{"query":"mutation {updateLicenseKey(license: \"${LICENSE}\") {__typename}}"}
EOF
The browser sends its timezone to the server and that determines
cutoff for say timechart(span=1day). The timezone is not embedded
in the URL, so if a query is shared across timezones the day cutoff
will differ.
The bucket() and timechart() functions lets you specify an
explicit timezone (timechart(..., timezone=Z)). This will overrule
the timezone of the browser. Note, that the x-axis of time charts is
still shown in local time.
Yes! Humio does support receiving events with multiple lines. What Humio does not support is correlating multiple events into a single multiline event, which means that it is up to the log shipper to detect wether an event spans across multiple lines.
Filebeat has support for detecting multiline events.