What is an Elastic integration?

This integration is powered by Elastic Agent. Elastic Agent is a single, unified way to add monitoring for logs, metrics, and other types of data to a host. It can also protect hosts from security threats, query data from operating systems, forward data from remote services or hardware, and more. Refer to our documentation for a detailed comparison between Beats and Elastic Agent.

Prefer to use Beats for this use case? See Filebeat modules for logs or Metricbeat modules for metrics.

Overview

The custom HTTP Endpoint Log integration initializes a listening HTTP server that collects incoming HTTP POST requests containing a JSON body. The body must be either an object or an array of objects. Any other data types will result in an HTTP 400 (Bad Request) response. For arrays, one document is created for each object in the array.

These are the possible response codes from the server.

HTTP Response CodeNameReason
200
OK
Returned on success.
400
Bad Request
Returned if JSON body decoding fails.
401
Unauthorized
Returned when basic auth, secret header, or HMAC validation fails.
405
Method Not Allowed
Returned if methods other than POST are used.
406
Not Acceptable
Returned if the POST request does not contain a body.
415
Unsupported Media Type
Returned if the Content-Type is not application/json.
500
Internal Server Error
Returned if an I/O error occurs reading the request.

Custom ingest pipelines may be added by adding the name to the pipeline configuration option, creating custom ingest pipelines can be done either through the API or the Ingest Node Pipeline UI.

Changelog

VersionDetails
1.3.0
Enhancement View pull request
Update package to ECS 8.4.0
1.2.0
Enhancement View pull request
Update package to ECS 8.3.0.
1.1.0
Enhancement View pull request
Update ECS to 8.2
1.0.1
Enhancement View pull request
Update readme
1.0.0
Enhancement View pull request
Initial Release