-
Notifications
You must be signed in to change notification settings - Fork 29
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
Logs from GKE containers use the legacy resource types #132
Comments
@jebbench ,Thanks for filling issue.For a Kubernetes container instance set the name of the monitored resource
|
@suraj-qlogic thanks for looking into this. Adding the setting the resource type correctly sets the resource type however it doesn't fill in any of the resource labels:
My ultimate aim is to have the logs from my Java application correctly associated to the cluster/namespace/pod/container that creates them with the correct log levels. I can achive the correct association by simply logging to STDOUT however this doesn't correctly pick up the log levels - this library correctly sets the log levels but doesn't associate the logs with the container. I've tried emiting logs to STDOUT in the logstash JSON format but stackdriver doesn't parse the log level. |
@jebbench ,please follow here java-logging-206 for progress/work related to your request. |
Environment details
General, Core, and Other are also allowed as types
Steps to reproduce
Expexted:
Actual:
The text was updated successfully, but these errors were encountered: