Cloud functions - 2nd gen - trace property for log entries [269319904]

Duplicate

of 287654780

Bug

Status Update

No update yet.

Description

ya...@coro.net

created issue #1

Feb 15, 2023 09:29AM

Hi,
I have noticed that in Cloud functions - 2nd gen - log service does not display in the log two essential things:
1. When the function execution started/ended.
2. Execution ID

This information exists in the 1st gen log.

Can you please add it?

Comments

su...@google.com <su...@google.com> Feb 15, 2023 09:56AM

Assigned to su...@google.com.

su...@google.com <su...@google.com> #2Feb 15, 2023 02:13PM

Reassigned to gc...@google.com.

Hello,

Thanks for reaching out to us! This has been forwarded to the Engineering Team so that they may evaluate it. Note that there are no ETAs or guarantees of implementation for feature requests. All communication regarding this feature request is to be done here.

vi...@ext.carrefour.com <vi...@ext.carrefour.com> #3Mar 10, 2023 07:20PM

Hello,
Is there any release date for this feature ?
Thanks

jo...@intelipost.com.br <jo...@intelipost.com.br> #4Mar 18, 2023 12:49PM

really useful feature!

pe...@gmail.com <pe...@gmail.com> #5Mar 30, 2023 03:01PM

Really needed

va...@google.com <va...@google.com> Apr 4, 2023 09:58AM

Reassigned to su...@google.com.

su...@google.com <su...@google.com> Apr 4, 2023 12:51PM

Reassigned to gc...@google.com.

ni...@noovle.com <ni...@noovle.com> #6Apr 13, 2023 04:44PM

Hello,

I understand that right now the only way to achieve the same functionality of the 1st gen is like this: https://cloud.google.com/functions/docs/monitoring/logging#writing_structured_logs

If you log with the proper trace value, you can group all the log lines related to the same requests and also correlate them to the main request log entry (where you see status code and url).

So I guess that if you have the X-Cloud-Trace-Context header available for http functions, I guess you can use messageId or something for the counterpart on CloudEvents functions.

Not native of course, but while we wait can help you reach your goal.

su...@gmail.com <su...@gmail.com> #7Apr 13, 2023 09:41PM

Hi,

Thanks for sharing this info.

I did try this approach. The limitation of this approach is it will be limited to the source code that is being built. Even this approach requires updating every log statement.

The other main limitation is the log entries from the dependent libraries are still logged in the old format and are not able to trace the requests.

pe...@gmail.com <pe...@gmail.com> #8Apr 20, 2023 09:56AM

Yes that's right, hence you have to use a uuid instead that's generated for each invocation.

ar...@google.com <ar...@google.com> #9Jun 23, 2023 02:30PM

Comment has been deleted.

Message last modified on Jun 23, 2023 02:42PM

rm...@google.com <rm...@google.com> Jul 7, 2023 01:16AM

Status: Duplicate of

287654780

an...@gmail.com <an...@gmail.com> #10Jul 11, 2023 11:36AM

Please also make sure that the solution for this also covers database triggers as well in all the systems you can write firestore function triggers for (e.g. realtime db and firestore).

[Deleted User] <[Deleted User]> #11Mar 1, 2024 03:05PM

Hi Google Team,

Any update over this issue this issue is impacting us to migrate to Gen 2 cloud function, we use execution_id to correlate logs both in HTTP and pub sub type cloud function,