-
-
Notifications
You must be signed in to change notification settings - Fork 61
K8s-ingestion #99
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
K8s-ingestion #99
Conversation
…d instead of host and service
|
It’s currently unclear what the expected behavior is when both --otlp-enabled and --k8s-enabled flags are used simultaneously. In practice, it appears that Kubernetes (--k8s-enabled) always takes precedence, rather than the last flag on the command line. If that’s the case, we should clean up the error handling logic to make it explicit which data source is intended to be used—especially given that Gonzo seems to support only a single input source at a time. |
j0nr33v3
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Docs looks good to me, didn't know if we should make the fact that the selector is pod specific more obvious like "--k8s-pod-selector" vs "--k8s-selector" but minor
Adds native kubernetes log ingest to Gonzo.
Allows selecting by namespaces and pods for filtering, as well as contexts. Point Gonzo at your kubeconfig and let it rip!
When in k8s mode, it will automatically change the columns in the log viewer to show namespace and pod for the log messages. It does it's best to transform the log data into a nice format, but some structured logs are not detected (even when not in k8s mode) so a custom format description file should be used for that.