OpenParable
Skip to content
← Back to skills

Golem Logging Scala

Development
golem-logging-scala

Golem Logging Scala is an Agent Skill for development published in the golemcloud/golem repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

Adding logging to a Scala Golem agent. Use when the user asks about logging, log messages, log levels, wasi:logging, golem.wasi.Logging, or printing debug/info/error output from a Scala agent.

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/golemcloud/golem/blob/HEAD/golem-skills/skills/scala/golem-logging-scala/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/golem-logging-scala, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

Logging from a Scala Agent

The Scala SDK provides golem.wasi.Logging — a typed facade over wasi:logging/logging with convenience methods for each log level and an optional context parameter.

Quick Start

Import and use the Logging object directly — no initialization needed:

import golem.wasi.Logging

Logging.info("order created: " + orderId)
Logging.debug("processing item: " + itemId)
Logging.warn("retry attempt " + attempt + " for request " + reqId)
Logging.error("failed to connect: " + err.getMessage)

Log Levels

MethodWASI LevelUse for
Logging.trace(msg)traceFine-grained control flow
Logging.debug(msg)debugDebugging information
Logging.info(msg)infoMonitoring, normal operations
Logging.warn(msg)warnHazardous situations
Logging.error(msg)errorSerious errors
Logging.critical(msg)criticalFatal errors

Context Strings

Every method accepts an optional context parameter (defaults to ""). Use it to scope log entries to a subsystem or request:

Logging.info("connected to database", context = "db")
Logging.debug(s"query took ${ms}ms", context = "db/query")
Logging.error(s"timeout after ${retries} retries", context = "http-client")

For the lowest-level API, call Logging.log directly:

Logging.log(Logging.Level.Critical, "shutdown", "system is shutting down")

Using println / System.err.println

Standard output and error also work and are captured by Golem:

println("stdout message")
System.err.println("stderr message")

These appear in golem agent stream output but lack log levels and context. Prefer Logging.* methods for structured, filterable logging.

Viewing Logs

Stream live agent output:

golem agent stream '<agent-id>'

Or during an invocation:

golem agent invoke '<agent-id>' '<method>' [args]

Key Points

  • No setup needed — golem.wasi.Logging is available from golem-scala-core which is already in the project dependencies
  • All methods map directly to the wasi:logging/logging WASI interface
  • Context strings help group and filter log entries by subsystem
  • Logs are recorded in the oplog and visible via golem agent stream and golem agent invoke
  • Logging is a side effect — during replay (crash recovery), log calls from replayed operations are skipped