Skip to content
This repository was archived by the owner on Feb 7, 2026. It is now read-only.
This repository was archived by the owner on Feb 7, 2026. It is now read-only.

Incorrect GCE instance_id #148

@epgoranova

Description

@epgoranova

Environment details

  • OS: CentOS on a GCE instance
  • Node.js version: 8.9.3
  • npm version: yarn 1.4.0
  • @google-cloud/logging-bunyan version: 0.8.2

Steps to reproduce

Logging from within a GCE instance consistently produces wrong instance_id in resource.labels, e.g. 2554270933530966500 while the actual ID is 2554270933530966670. This makes using the GCP Console inconvenient where the logs are filtered by instance_id by default. Also while the project is correctly filled, the zone is missing:

resource: {
  labels: {
    instance_id:  "2554270933530966500"    
    project_id:  "my-project"    
    zone:  ""    
  }
  type:  "gce_instance"   
}

I suspect the instance_id issue has something to do with googleapis/gcp-metadata#74 but since the zone is missing as well there might be more to it.

Metadata

Metadata

Assignees

Labels

🚨This issue needs some love.api: loggingIssues related to the googleapis/nodejs-logging-bunyan API.triage meI really want to be triaged.

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions