Repository navigation
Deprecate AsyncLoggingHandler? #1532
Copy link
Copy link
Closed
Labels
api: loggingIssues related to the Cloud Logging API.Issues related to the Cloud Logging API.
Description
Activity
garrettjonesgoogle commented
on Jan 13, 2017 ContributorMore actionsHmm I think I should actually switch the main one back to synchronous. I overlooked the separate asynchronous class which people can use. What I do think should be done though is to switch the example to suggest the asynchronous one because it will be more performant.
- addedapi: loggingIssues related to the Cloud Logging API.Issues related to the Cloud Logging API.
on Jan 13, 2017 garrettjonesgoogle commented
on Jan 26, 2017 ContributorMore actionsI think this needs to be cleaned up before GA.
- added and removed
on Feb 20, 2017 We should delete this altogether, and support a setting for sync v async in the logging config.
Closed in #1716
Could the AsyncLoggingHandler be left as a deprecated extension of LoggingHandler, as that will make transitioning usage easier?
- added a commit that references this issue
on Oct 8, 2022 - added a commit that references this issue
on Dec 22, 2025 - added a commit that references this issue
on Jan 6, 2026 - added a commit that references this issue
on Feb 24, 2026 - added a commit that references this issue
on Mar 11, 2026 - added a commit that references this issue
on Mar 12, 2026 - added a commit that references this issue
on Mar 20, 2026 - added a commit that references this issue
on Mar 30, 2026 - added a commit that references this issue
on Apr 1, 2026
Metadata
Metadata
Assignees
Labels
api: loggingIssues related to the Cloud Logging API.Issues related to the Cloud Logging API.
The fix for #1386 has made the normal LoggingHandler asynchronous! Was this deliberate? If so, should the AsyncLoggingHandler be deprecated as it now no longer changes behaviour.