Skip to content

Document Actor run log redirection on the Logging page #1174

Closed

Description

@vdusek

The Logging concept page (06_logging.mdx) covers only the apify_client debug logger and its extra fields. Nothing in the docs explains that ActorClient.call() redirects the run's log and status messages to a logger while it waits (actor.py#L385-L388, #L416-L429), or how to turn that off. RunClient.get_streamed_log() and RunClient.get_status_message_watcher() (run.py#L344-L350, #L433-L439) appear only in the API reference.

The JS docs have a "Redirecting Actor run logs" section that covers the log option of call() and getStreamedLog() for runs started with start() (05_logging.mdx).

Expected behavior

Add a "Redirecting Actor run logs" section to the Python Logging page, with sync and async snippets:

  • call(logger=...): 'default' uses the built-in redirect logger, a logging.Logger receives the lines, None turns redirection off. The same logger also gets the run's status and status message changes.
  • For a run started with start(), get_streamed_log() and get_status_message_watcher(), used as context managers or started and stopped by hand.

✍️ Drafted by Claude Code

Activity

  1. added
    t-toolingIssues with this label are in the ownership of the tooling team.
    on Oct 30, 2026
  2. added theissue type on Oct 30, 2026
  3. added a commit that references this issue on Nov 6, 2026
    1913925
  4. self-assigned this
    on Nov 6, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

t-toolingIssues with this label are in the ownership of the tooling team.

Type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions