There are steps to getting your data into Humio:
Sending data to Humio (also called data shipping) can be done in a couple of ways:
In most cases you will want to use a data shipper or one of our platform integrations.
If you are just interested in getting some data into Humio quickly, take a look at the getting started: sending application logs guide.
Below is an overview of how the respective flows of sending data to Humio work:
A Data Shipper is a small system tool that looks at files and system properties on a server and send it to Humio. Data shippers take care of buffering, retransmitting lost messages, log file rolling, network disconnects, and a slew of other things so your data or logs are send to Humio in a reliable.
In this example “Your Application” is writing logs to a “Log File”. The “Data Shipper” reads the data and pre-processes it (e.g. this could be converting a multiline stack-trace into a single event). It then ships the data to Humio on one of our Ingest APIs.
If you want to get logs and metrics from your deployment platform, e.g. a Kubernetes cluster or your company PaaS, you can use one of our Platform Integrations.
Depending on your platform the data flow will look slightly different. Some systems use a built-in logging subsystem, others you start a container running with a data shipper. Usually you will assign containers/instances in some way to indicate which repository and parser should be used at ingestion.
Take a look at the individual integrations pages for more details.
If your needs are simple and you don’t care too much about potential data loss due to e.g. network problem, you can also use Humio’s Ingest API directly or through one of Humio’s client libraries.
As you can see, this is by far the simplest flow, and is completely appropriate for some scenarios e.g. analytics.