LogExporter
Ship logs to Opensearch
This task is designed to send logs from kestra to an Opensearch database.
type: "io.kestra.plugin.ee.opensearch.LogExporter"Ship logs to Opensearch
id: log_shipper
namespace: company.team
triggers:
- id: daily
type: io.kestra.plugin.core.trigger.Schedule
cron: "@daily"
tasks:
- id: logSync
type: io.kestra.plugin.ee.core.log.LogShipper
logLevelFilter: INFO
batchSize: 1000
lookbackPeriod: P1D
logExporters:
- id: OpensearchLogExporter
type: io.kestra.plugin.ee.opensearch.LogExporter
connection:
hosts:
- "http://localhost:9200/"
indexName: "logs"
NOThe connection properties.
NO^[a-zA-Z0-9][a-zA-Z0-9_-]*1YESThe name of the index to send logs to
YES1000The chunk size for every bulk request.
YESBasic auth password.
YESBasic auth username.
YESList of HTTP OpenSearch servers.
Must be an URI like https://opensearch.com: 9200 with scheme and port.
NOBasic auth configuration.
YESList of HTTP headers to be send on every request.
Must be a string with key value separated with : , ex: Authorization: Token XYZ.
YESSets the path's prefix for every request used by the HTTP client.
For example, if this is set to /my/path, then any client request will become /my/path/ + endpoint.
In essence, every request's endpoint is prefixed by this pathPrefix.
The path prefix is useful for when OpenSearch is behind a proxy that provides a base path or a proxy that requires all paths to start with '/'; it is not intended for other purposes and it should not be supplied in other scenarios.
YESWhether the REST client should return any response containing at least one warning header as a failure.
YESTrust all SSL CA certificates.
Use this if the server is using a self signed SSL certificate.