You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
#822 changed a few spec details for metadata.cloud.project.* fields collected for GCP. Here are the things you should change/check in your implementation. See the spec PR for justification for each change:
Change cloud.project.id to use GCE metadata project.projectId, instead of project.numericProjectId (aka "project number").
Stop collecting cloud.project.name.
Check that you collect cloud.instance.id correctly. The instance.id from the GCE metadata is an int that typically has values larger than 2**53 – 1. It is possible your JSON parser could be surprised by it. For example, the JavaScript one gets it wrong, because JavaScript is weird and uses floats for all numbers and the big int here exceeds JavaScript's Number.MAX_SAFE_INTEGER:
Check that you collect cloud.region correctly. The spec's previous description for how to get the cloud.region was wrong. For example, given GCE metadata with {"instance": {"zone": "projects/123456789012/zones/us-west1-b"}} you should collect us-west1.
All the relevant agents (not PHP because it doesn't yet do cloud metadata collection) have a fix in now. I'm not tracking what release has it for each agent.
Description
#822 changed a few spec details for
metadata.cloud.project.*
fields collected for GCP. Here are the things you should change/check in your implementation. See the spec PR for justification for each change:cloud.project.id
to use GCE metadataproject.projectId
, instead ofproject.numericProjectId
(aka "project number").cloud.project.name
.cloud.instance.id
correctly. Theinstance.id
from the GCE metadata is an int that typically has values larger than2**53 – 1
. It is possible your JSON parser could be surprised by it. For example, the JavaScript one gets it wrong, because JavaScript is weird and uses floats for all numbers and the big int here exceeds JavaScript'sNumber.MAX_SAFE_INTEGER
:cloud.region
correctly. The spec's previous description for how to get thecloud.region
was wrong. For example, given GCE metadata with{"instance": {"zone": "projects/123456789012/zones/us-west1-b"}}
you should collectus-west1
.Agent Issues
metadata.cloud.project.*
fields collected for GCP apm-agent-java#3311metadata.cloud.project.*
fields collected for GCP apm-agent-dotnet#2177metadata.cloud.project.*
fields collected for GCP apm-agent-nodejs#3614metadata.cloud.project.*
fields collected for GCP apm-agent-python#1899metadata.cloud.project.*
fields collected for GCP apm-agent-go#1509metadata.cloud.project.*
fields collected for GCP apm-agent-php#1053metadata.cloud.project.*
fields collected for GCP apm-agent-ruby#1414The text was updated successfully, but these errors were encountered: