Settings and activity
14 results found
-
3 votesMorten Bek Ditlevsen shared this idea ·
-
3 votesMorten Bek Ditlevsen shared this idea ·
-
101 votesMorten Bek Ditlevsen supported this idea ·
-
4 votes
An error occurred while saving the comment Morten Bek Ditlevsen supported this idea · -
5 votesMorten Bek Ditlevsen shared this idea ·
-
29 votesMorten Bek Ditlevsen supported this idea ·
-
31 votesMorten Bek Ditlevsen supported this idea ·
-
2 votesMorten Bek Ditlevsen supported this idea ·Morten Bek Ditlevsen shared this idea ·
-
11 votesMorten Bek Ditlevsen shared this idea ·
-
8 votesMorten Bek Ditlevsen supported this idea ·
-
6 votesMorten Bek Ditlevsen shared this idea ·
-
313 votesMorten Bek Ditlevsen shared this idea ·
-
290 votes
No public ETA to announce yet.
Morten Bek Ditlevsen supported this idea · -
243 votes
Hi folks, this is being actively worked on, and is expected to preview sometime in H1 2024. Thank you for using UserVoice to help us prioritize!
Morten Bek Ditlevsen supported this idea ·
Hi Thomas Bouldin,
Thanks a lot - I am using the firebase-functions/logger, but I had failed to discover that the trace ID was what I was looking for.
Since we are using structured logging, I did add my own ditto, but I can remove that again now then. Thanks so much.
I am curious that you write 'and more'. What might you be hinting at there? :-)
Perhaps my 'idea' could be rephrased to:
Let the logs explorer recognize trace ids and add a context menu showing 'See all from this execution' (similar to the previous functionality). I know it can be done 'manually', but it would be good for discoverability.