-
Task
-
Resolution: Done
-
Major
-
None
-
5
-
False
-
None
-
False
-
NEW
-
Administer
-
NEW
-
new feature
-
Medium
-
-
-
5
-
Log Collection - Sprint 237, Log Collection - Sprint 238, Log Collection - Sprint 239, Log Collection - Sprint 240, Log Collection - Sprint 241, Log Collection - Sprint 242
Requirements and Acceptance Criteria
Preview use case requirements:
- Receive kube-API audit logs as a WebHook to the kube-apiserver
- Forward received logs in the same way as logs scraped from /var/log/kube-apiserver/audit.log
The final HTTP receiver will address other use-cases, see LOG-4517
Design summary
An "input" can now have an (optional) "receiver".
The receiver specifies an alternate way of receiving logs, instead of default collection from the cluster log files.
The HTTP receiver has a name, port and format.
- Name and port are used to generate a service resource for the input.
- Preview format only supports `kubeAPIAudit`
- Final implementation will include others, see LOG-4517
- blocks
-
LOG-4517 COMPLETE: HTTP log receiver - collector acts as HTTP server
-
- To Do
-
- links to
- mentioned on
(2 mentioned on)