robocorp-log

What it is and what it does

robocorp-log is a structured logging library designed for Python automation where understanding failure causes is critical. It replaces verbose text-based logging with a compact format that generates an interactive HTML viewer (log.html), reducing disk space while improving readability. The library uses an AST-based pre-import hook to automatically capture execution traces without requiring explicit logging calls throughout your code, though it also provides manual logging APIs (critical, warn, info, debug, exception, html) when needed.

The package is primarily intended to be used through robocorp-tasks, which handles configuration via pyproject.toml. However, it exposes core APIs for suppressing sensitive data, hiding specific variables or methods, and sanitizing HTML content. It supports Python 3.10 through 3.14 and has no known security vulnerabilities. Note that the auto-import mechanism does not support coroutines (async/await, greenlet) and requires logging setup before importing modules you want to trace.

Use it for:

• Automated RPA workflows where detailed execution logs help diagnose failures in unattended runs
• Python test suites generating compact, browsable logs instead of large text files for CI/CD pipelines
• Sensitive data handling in automation scripts by automatically redacting variable names or patterns you register
• Interactive debugging of complex automation by viewing structured execution traces in a web browser
• Compliance and audit logging for automation tasks where you need to prove what executed and why it failed

Worth the install?

AI-flagged interpretation of the facts on this page — verify before relying

Provides structured, automatic logging for Python automation with a focus on capturing detailed failure context and generating an interactive HTML log viewer.

Yes, if you are building Python automation or RPA workflows where failure diagnostics and log readability matter. The low install friction, active maintenance, permissive license, and zero known vulnerabilities make it safe to adopt. The main caveat is that it requires setup before importing modules you want to trace and does not support async/await or greenlet; verify those constraints fit your codebase before committing.

Install

robocorp-log on PyPI

pip install robocorp-log

uv add robocorp-log

poetry add robocorp-log

Installing robocorp-log

Before you install

Low friction installation with only two runtime dependencies (psutil and tomli). Actively maintained with recent releases; last commit 2026-07-24. Classified as Beta but in active development.

License in practice

Apache-2.0 permissive license allows free use, modification, and distribution in both open-source and commercial projects with minimal restrictions.

Quickstart

pip install robocorp-log

import robocorp.log as log

log.info('Task started')
log.critical('Critical issue found')
log.exception(exception_instance)

Requires Python 3.10 or later. Auto-import logging must be configured before importing modules you want to trace; does not support async/await or greenlet.

Verify before relying

• Whether the HTML log viewer output is suitable for large-scale automation runs or has performance/size limitations
• Specific performance overhead of the AST-based auto-import hook during module initialization
• Compatibility with popular debugging tools and whether debugger skip configuration is straightforward

Package facts

Evidence: robocorp_log-3.1.2-py3-none-any.whl

Tags

More Python Modules packages