Log source
BetaOpenTelemetry collector (OTLP/HTTP)
By OpenTelemetry
Point the log exporter of an OpenTelemetry collector you already run at Qorionix.
What you can connect
Capabilities and availability
Each capability has its own setup and status. Review the details before enabling it for your organisation.
Log collection
BetaSetup available in the console
OTLP/HTTP log records encoded as JSON are accepted; protobuf payloads, traces and metrics are not.
What to know before connecting
OTLP/HTTP log records encoded as JSON are accepted; protobuf payloads, traces and metrics are not.
More in Log source
Log source
HTTP Event Collector (Splunk-compatible)
A token-authenticated HTTP endpoint in the Splunk HEC shape. Anything that can POST JSON or raw lines with a token header can send logs: Splunk forwarders, Fluent Bit, Vector, the Docker splunk log driver and most SaaS log exporters.
Log source
Linux auditd
Authentication, privilege and process audit records from the Linux audit daemon, forwarded over syslog and parsed with the auditd parser.
Log source
Syslog (any firewall, switch or server)
Almost every firewall, switch, router, NAS and Linux server can send syslog. Events arrive over TLS or TCP, are parsed and stored as OCSF, and are searchable at once.