IssueTracker

This is a feature request for a method to get execution ID from within a PubSub triggered cloud function.

Currently, our default python logs have an execution ID label automatically attached in Stackdriver.

However, when we send logs using google cloud logger python library, we need to to pass label parameters. We have not found a way to get execution id from within a pubsub triggered cloud function so all we can do is attach an event id label. Then we also have to add an event id label to our python logs to tie those logs to logs created by cloud logger.

This crowds the log label space and makes it more complicated to tie all logs from one execution to one another.

So our current logs look like:

<execution id label><event id label> python log 1

<execution id label><event id label> python log 2

<event id label> cloud logger log (we use this to add traceback in one blob, python logs get split up line by line on stackdriver)

Ideally we could just have:

<execution id label> python log 1

<execution id label> python log 2

<execution id label> cloud logger log