Getting execution-id / trace in background functions

Environment details

• OS: MacOS 10.13.6
• Node.js version: 10.15.3
• npm version: 6.4.1
• @google-cloud/logging version: 5.3.1
• Firebase Cloud Functions

Steps to reproduce

1. In a Firebase cloud functions (scheduler or pubsub or httpRequest)

console.log('Init');

This gets taged correctly with an execution and the correct labels. 2.

import { Logging, detectServiceContext } from '@google-cloud/logging';

I’ve tried stealing export function getCurrentTraceFromAgent() { and the detectServiceContext trick from @google-cloud/logging-bunyan": “^1.2.3”, it didn’t work either. Also went around https://stackoverflow.com/questions/49185824/log-jsonpayload-in-firebase-cloud-functions it didn’t work.

It’s been 5hours and I’m starting to get a bit crazy on how to achieve the same behavior than a console.log and adding my own metadata

[jpreynat]

Same here, being able to reproduce the behavior of console.log for Node 10 in order to customize it using this module seems essential.

[Elyx0]

Any updates? It’s a must have to me to be able to follow an error with additional jsonPayload alongside its execution id