Skip to content
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

logging: instance_name label is not valid for GCE Instance Resource #4272

Closed
hopkiw opened this issue Jun 16, 2021 · 3 comments · Fixed by #5461
Closed

logging: instance_name label is not valid for GCE Instance Resource #4272

hopkiw opened this issue Jun 16, 2021 · 3 comments · Fixed by #5461
Assignees
Labels
api: logging Issues related to the Cloud Logging API. priority: p2 Moderately-important priority. Fix may not be included in next release. type: feature request ‘Nice-to-have’ improvement, new feature or different behavior or design.

Comments

@hopkiw
Copy link

hopkiw commented Jun 16, 2021

"instance_name": name,

This code automatically detects and adds an instance_name label to the common resource object. However, the instance_name label never appears on any logs on the service side. I believe this is because the GCE instance resource only accepts a pre-validated set of labels which are the project, zone and instance ID. The code here should not add or send the instance_name label, and probably the service should reject resources with invalid labels to aid in discovery.

@hopkiw
Copy link
Author

hopkiw commented Jun 16, 2021

Alternately, the service could be updated to consider instance_name a valid label for a GCE Instance resource. This would have the added benefit of affecting existing software retroactively which is currently trying to send this label.

@codyoss codyoss changed the title instance_name label is not valid for GCE Instance Resource logging: instance_name label is not valid for GCE Instance Resource Jun 16, 2021
@codyoss codyoss added the api: logging Issues related to the Cloud Logging API. label Jun 16, 2021
@yoshi-automation yoshi-automation added triage me I really want to be triaged. 🚨 This issue needs some love. labels Jun 17, 2021
@0xSage 0xSage added priority: p2 Moderately-important priority. Fix may not be included in next release. type: question Request for information or clarification. Not an issue. type: feature request ‘Nice-to-have’ improvement, new feature or different behavior or design. and removed triage me I really want to be triaged. 🚨 This issue needs some love. labels Jun 23, 2021
@0xSage 0xSage assigned simonz130 and unassigned 0xSage Jun 29, 2021
@yoshi-automation yoshi-automation added 🚨 This issue needs some love. and removed 🚨 This issue needs some love. labels Nov 3, 2021
@yoshi-automation yoshi-automation added the 🚨 This issue needs some love. label Dec 13, 2021
@minherz minherz assigned minherz and unassigned simonz130 Jan 24, 2022
@minherz
Copy link
Contributor

minherz commented Feb 3, 2022

@hopkiw thank you for pointing to this problem. we will remove the code to align the behavior with the documented set of labels reported by logging agents for the GCE instances.

@minherz minherz removed 🚨 This issue needs some love. type: question Request for information or clarification. Not an issue. labels Feb 7, 2022
@minherz
Copy link
Contributor

minherz commented Feb 7, 2022

While it is possible to keep the instance_name label, its use is undesirable in events of GCE instance renaming.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
api: logging Issues related to the Cloud Logging API. priority: p2 Moderately-important priority. Fix may not be included in next release. type: feature request ‘Nice-to-have’ improvement, new feature or different behavior or design.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

6 participants