tilebox · lukasbindreiter · May 8, 2026 · May 8, 2026 · May 8, 2026
diff --git a/api-reference/python/tilebox.workflows/Client.configure_logging.mdx b/api-reference/python/tilebox.workflows/Client.configure_logging.mdx
@@ -0,0 +1,38 @@
+---
+title: Client.configure_logging
+icon: laptop-code
+---
+
+```python
+def Client.configure_logging(
+    level: int,
+    runner_level: int | None = None,
+) -> None
+```
+
+Configure the log level for logs exported by this workflow client.
+
+## Parameters
+
+<ParamField path="level" type="int" required>
+  Logging level for task logs emitted with `context.logger`, for example `logging.INFO` or `logging.DEBUG`.
+</ParamField>
+
+<ParamField path="runner_level" type="int | None">
+  Logging level for internal task runner logs. If omitted, the value of `level` is used.
+</ParamField>
+
+## Returns
+
+`None`
+
+<RequestExample>
+```python Python
+import logging
+
+from tilebox.workflows import Client
+
+client = Client(name="sentinel-2-runner")
+client.configure_logging(level=logging.DEBUG, runner_level=logging.INFO)
+```
+</RequestExample>
diff --git a/api-reference/python/tilebox.workflows/Client.mdx b/api-reference/python/tilebox.workflows/Client.mdx
@@ -4,7 +4,12 @@ icon: code
 ---
 
 ```python
-class Client(url: str, token: str)
+class Client(
+    *,
+    url: str = "https://api.tilebox.com",
+    token: str | None = None,
+    name: str | None = None,
+)
 ```
 
 Create a Tilebox workflows client.
@@ -19,6 +24,10 @@ Create a Tilebox workflows client.
   The API Key to authenticate with. If not set the `TILEBOX_API_KEY` environment variable will be used.
 </ParamField>
 
+<ParamField path="name" type="string | None">
+  Optional service name for workflow telemetry. If not set, the default service name is used.
+</ParamField>
+
 ## Sub clients
 
 The workflows client exposes sub clients for interacting with different parts of the Tilebox workflows API.
@@ -41,6 +50,14 @@ def Client.automations() -> AutomationClient
 
 A client for scheduling automations.
 
+## Logging
+
+```python
+def Client.configure_logging(level: int, runner_level: int | None = None) -> None
+```
+
+Configure which task and runner logs this client exports. See [`Client.configure_logging`](/api-reference/python/tilebox.workflows/Client.configure_logging).
+
 ## Task runners
 
 ```python
@@ -59,7 +76,8 @@ client = Client()
 # or provide connection details directly
 client = Client(
     url="https://api.tilebox.com",
-    token="YOUR_TILEBOX_API_KEY"
+    token="YOUR_TILEBOX_API_KEY",
+    name="sentinel-2-runner",
 )
 
 # access sub clients

diff --git a/api-reference/python/tilebox.workflows/ExecutionContext.logger.mdx b/api-reference/python/tilebox.workflows/ExecutionContext.logger.mdx
@@ -0,0 +1,39 @@
+---
+title: Context.logger
+icon: folder-gear
+---
+
+```python
+ExecutionContext.logger: StructuredLogger
+```
+
+Structured logger for logs emitted by the currently executing task.
+
+## Methods
+
+```python
+context.logger.debug(message, /, *args, **attributes) -> None
+context.logger.info(message, /, *args, **attributes) -> None
+context.logger.warning(message, /, *args, **attributes) -> None
+context.logger.error(message, /, *args, **attributes) -> None
+context.logger.exception(message, /, *args, **attributes) -> None
+context.logger.critical(message, /, *args, **attributes) -> None
+context.logger.bind(**attributes) -> StructuredLogger
+```
+
+Structured attributes are attached to the log record and become searchable telemetry attributes.
+
+<RequestExample>
+```python Python
+from tilebox.workflows import ExecutionContext, Task
+
+class ProcessScene(Task):
+    scene_id: str
+
+    def execute(self, context: ExecutionContext) -> None:
+        context.logger.info("Started", scene_id=self.scene_id)
+
+        log = context.logger.bind(component="download")
+        log.debug("Fetching input")
+```
+</RequestExample>
diff --git a/api-reference/python/tilebox.workflows/ExecutionContext.tracer.mdx b/api-reference/python/tilebox.workflows/ExecutionContext.tracer.mdx
@@ -0,0 +1,32 @@
+---
+title: Context.tracer
+icon: folder-gear
+---
+
+```python
+ExecutionContext.tracer: WorkflowTracer
+```
+
+Tracer for creating custom spans inside the currently executing task.
+
+## Methods
+
+```python
+context.tracer.span(name: str, *args, **kwargs) -> ContextManager[Span]
+context.tracer.current_span() -> Span
+```
+
+Custom spans are nested under the current task span and are exported to Tilebox with the job trace.
+
+<RequestExample>
+```python Python
+from tilebox.workflows import ExecutionContext, Task
+
+class ProcessScene(Task):
+    scene_id: str
+
+    def execute(self, context: ExecutionContext) -> None:
+        with context.tracer.span("download-scene") as span:
+            span.set_attribute("scene_id", self.scene_id)
+```
+</RequestExample>
diff --git a/api-reference/python/tilebox.workflows/JobClient.query_logs.mdx b/api-reference/python/tilebox.workflows/JobClient.query_logs.mdx
@@ -0,0 +1,33 @@
+---
+title: JobClient.query_logs
+icon: rectangle-terminal
+---
+
+```python
+def JobClient.query_logs(job_id: Job | UUID | str) -> LogRecords
+```
+
+Query logs emitted while running a job. Pagination is handled automatically.
+
+## Parameters
+
+<ParamField path="job_id" type="Job | UUID | str" required>
+  The job, job ID, or job ID string to query logs for.
+</ParamField>
+
+## Returns
+
+A `LogRecords` list. Each `LogRecord` contains `time`, `severity_number`, `severity_text`, `body`, `trace_id`, `span_id`, `attributes`, and `runner_attributes`.
+
+`LogRecords.to_pandas()` converts the records to a pandas DataFrame.
+
+<RequestExample>
+```python Python
+logs = client.jobs().query_logs(job)
+
+for record in logs:
+    print(record.time, record.severity_text, record.body)
+
+df = logs.to_pandas()
+```
+</RequestExample>
diff --git a/api-reference/python/tilebox.workflows/JobClient.query_spans.mdx b/api-reference/python/tilebox.workflows/JobClient.query_spans.mdx
@@ -0,0 +1,33 @@
+---
+title: JobClient.query_spans
+icon: chart-gantt
+---
+
+```python
+def JobClient.query_spans(job_id: Job | UUID | str) -> Spans
+```
+
+Query spans emitted while running a job. Pagination is handled automatically.
+
+## Parameters
+
+<ParamField path="job_id" type="Job | UUID | str" required>
+  The job, job ID, or job ID string to query spans for.
+</ParamField>
+
+## Returns
+
+A `Spans` list. Each `Span` contains `start_time`, `end_time`, `duration`, `trace_id`, `span_id`, `parent_span_id`, `name`, `status_code`, `status_message`, `attributes`, `runner_attributes`, and `events`.
+
+`Spans.to_pandas()` converts the spans to a pandas DataFrame and includes a computed `duration` column.
+
+<RequestExample>
+```python Python
+spans = client.jobs().query_spans(job.id)
+
+for span in spans:
+    print(span.name, span.status_code, span.duration)
+
+df = spans.to_pandas()
+```
+</RequestExample>
diff --git a/assets/changelog/2026-05-observability-dark.png b/assets/changelog/2026-05-observability-dark.png
diff --git a/assets/changelog/2026-05-observability-light.png b/assets/changelog/2026-05-observability-light.png
diff --git a/assets/console/api-keys-dark.png b/assets/console/api-keys-dark.png
diff --git a/assets/console/api-keys-light.png b/assets/console/api-keys-light.png
diff --git a/assets/console/automation-dark.png b/assets/console/automation-dark.png
diff --git a/assets/console/automation-edit-dark.png b/assets/console/automation-edit-dark.png
diff --git a/assets/console/automation-edit-light.png b/assets/console/automation-edit-light.png
diff --git a/assets/console/automation-light.png b/assets/console/automation-light.png
diff --git a/assets/console/automations-dark.png b/assets/console/automations-dark.png
diff --git a/assets/console/automations-light.png b/assets/console/automations-light.png
diff --git a/assets/console/cluster-dark.png b/assets/console/cluster-dark.png
diff --git a/assets/console/cluster-light.png b/assets/console/cluster-light.png
diff --git a/assets/console/datapoint-dark.png b/assets/console/datapoint-dark.png
diff --git a/assets/console/datapoint-light.png b/assets/console/datapoint-light.png
diff --git a/assets/console/datasets-create-dark.png b/assets/console/datasets-create-dark.png
diff --git a/assets/console/datasets-create-light.png b/assets/console/datasets-create-light.png
diff --git a/assets/console/datasets-create-temporal-dark.png b/assets/console/datasets-create-temporal-dark.png
diff --git a/assets/console/datasets-create-temporal-light.png b/assets/console/datasets-create-temporal-light.png
diff --git a/assets/console/datasets-documentation-dark.png b/assets/console/datasets-documentation-dark.png
diff --git a/assets/console/datasets-documentation-light.png b/assets/console/datasets-documentation-light.png
diff --git a/assets/console/datasets-explorer-dark.png b/assets/console/datasets-explorer-dark.png
diff --git a/assets/console/datasets-explorer-light.png b/assets/console/datasets-explorer-light.png
diff --git a/assets/console/datasets-overview-dark.png b/assets/console/datasets-overview-dark.png
diff --git a/assets/console/datasets-overview-light.png b/assets/console/datasets-overview-light.png
diff --git a/assets/console/job-execution-dark.png b/assets/console/job-execution-dark.png
diff --git a/assets/console/job-execution-light.png b/assets/console/job-execution-light.png
diff --git a/assets/console/job-logs-dark.png b/assets/console/job-logs-dark.png
diff --git a/assets/console/job-logs-light.png b/assets/console/job-logs-light.png
diff --git a/assets/console/storage-event-dark.png b/assets/console/storage-event-dark.png
diff --git a/assets/console/storage-event-light.png b/assets/console/storage-event-light.png
diff --git a/assets/console/usage-dark.png b/assets/console/usage-dark.png
diff --git a/assets/console/usage-light.png b/assets/console/usage-light.png
diff --git a/assets/workflows/observability/job-logs-pandas-dark.png b/assets/workflows/observability/job-logs-pandas-dark.png
diff --git a/assets/workflows/observability/job-logs-pandas-light.png b/assets/workflows/observability/job-logs-pandas-light.png
diff --git a/assets/workflows/observability/job-traces-pandas-dark.png b/assets/workflows/observability/job-traces-pandas-dark.png
diff --git a/assets/workflows/observability/job-traces-pandas-light.png b/assets/workflows/observability/job-traces-pandas-light.png
diff --git a/authentication.mdx b/authentication.mdx
@@ -6,7 +6,7 @@ icon: key
 
 ## Creating an API key
 
-To create an API key, log into the [Tilebox Console](https://console.tilebox.com). Navigate to [Account -> API Keys](https://console.tilebox.com/account/api-keys) and click the "Create API Key" button.
+To create an API key, log into the [Tilebox Console](https://console.tilebox.com). Navigate to [Settings -> API Keys](https://console.tilebox.com/settings/api-keys) and click the "Create API Key" button.
 
 <Info>
 Keep your API keys secure. Deactivate any keys if you suspect they have been compromised.

diff --git a/changelog.mdx b/changelog.mdx
@@ -4,6 +4,21 @@ description: A chronological record of new features, improvements, and other not
 icon: rss
 ---
 
+<Update label="May 2026">
+    <Frame>
+    <img src="/assets/changelog/2026-05-observability-light.png" alt="Job Execution Trace View" className="dark:hidden" />
+    <img src="/assets/changelog/2026-05-observability-dark.png" alt="Job Execution Trace View" className="hidden dark:block" />
+    </Frame>
+
+    ## Workflow Observability
+
+    Tilebox Workflows now includes built-in observability for jobs and task runners. Tilebox captures workflow logs, traces, task status, and runner context, then correlates them with jobs and tasks.
+
+    The Console includes a built-in explorer for workflow observability, so you can inspect task logs, trace timing, failures, and runner behavior from the job view.
+
+    See the [Workflow observability documentation](/workflows/observability/introduction) for examples and integration options.
+</Update>
+
 <Update label="February 2026">
     <Frame>
     ![Optional Tasks](/assets/changelog/2026-02-optional-tasks.png)

diff --git a/docs.json b/docs.json
@@ -88,9 +88,18 @@
                 "group": "Observability",
                 "icon": "eye",
                 "pages": [
-                  "workflows/observability/open-telemetry",
+                  "workflows/observability/introduction",
                   "workflows/observability/tracing",
-                  "workflows/observability/logging"
+                  "workflows/observability/logging",
+                  "workflows/observability/query",
+                  {
+                    "group": "Integrations",
+                    "icon": "plug",
+                    "pages": [
+                      "workflows/observability/integrations/open-telemetry",
+                      "workflows/observability/integrations/axiom"
+                    ]
+                  }
                 ]
               },
               {
@@ -187,8 +196,11 @@
                   "api-reference/python/tilebox.workflows/Client",
                   "api-reference/python/tilebox.workflows/Task",
                   "api-reference/python/tilebox.workflows/Client.runner",
+                  "api-reference/python/tilebox.workflows/Client.configure_logging",
                   "api-reference/python/tilebox.workflows/TaskRunner.run_all",
                   "api-reference/python/tilebox.workflows/TaskRunner.run_forever",
+                  "api-reference/python/tilebox.workflows/ExecutionContext.logger",
+                  "api-reference/python/tilebox.workflows/ExecutionContext.tracer",
                   "api-reference/python/tilebox.workflows/ExecutionContext.submit_subtask",
                   "api-reference/python/tilebox.workflows/ExecutionContext.submit_subtasks",
                   "api-reference/python/tilebox.workflows/ExecutionContext.job_cache",
@@ -203,6 +215,8 @@
                   "api-reference/python/tilebox.workflows/JobClient.retry",
                   "api-reference/python/tilebox.workflows/JobClient.cancel",
                   "api-reference/python/tilebox.workflows/JobClient.visualize",
+                  "api-reference/python/tilebox.workflows/JobClient.query_logs",
+                  "api-reference/python/tilebox.workflows/JobClient.query_spans",
                   "api-reference/python/tilebox.workflows/JobClient.query"
                 ]
               }

diff --git a/guides/datasets/access-sentinel2-data.mdx b/guides/datasets/access-sentinel2-data.mdx
@@ -4,7 +4,7 @@ description: Query Sentinel-2 satellite imagery metadata from a Tilebox dataset,
 icon: database
 ---
 
-This guide assume you already [signed up](https://console.tilebox.com/sign-up) for a Tilebox account (free) and [created an API key](https://console.tilebox.com/account/api-keys).
+This guide assume you already [signed up](https://console.tilebox.com/sign-up) for a Tilebox account (free) and [created an API key](https://console.tilebox.com/settings/api-keys).
 
 ## Install Tilebox package
 

diff --git a/quickstart.mdx b/quickstart.mdx
@@ -40,7 +40,7 @@ If you prefer to work locally, follow these steps to get started.
       </Tip>
     </Step>
     <Step title="Create an API Key">
-      Create an API key by logging into the [Tilebox Console](https://console.tilebox.com), navigating to [Account -> API Keys](https://console.tilebox.com/account/api-keys), and clicking the "Create API Key" button.
+      Create an API key by logging into the [Tilebox Console](https://console.tilebox.com), navigating to [Settings -> API Keys](https://console.tilebox.com/settings/api-keys), and clicking the "Create API Key" button.
 
       <Frame>
         <img src="/assets/console/api-keys-light.png" alt="Tilebox Console" className="dark:hidden"  />
@@ -138,7 +138,7 @@ If you prefer to work locally, follow these steps to get started.
       ```
     </Step>
     <Step title="Create an API Key">
-      Create an API key by logging into the [Tilebox Console](https://console.tilebox.com), navigating to [Account -> API Keys](https://console.tilebox.com/account/api-keys), and clicking the "Create API Key" button.
+      Create an API key by logging into the [Tilebox Console](https://console.tilebox.com), navigating to [Settings -> API Keys](https://console.tilebox.com/settings/api-keys), and clicking the "Create API Key" button.
 
       <Frame>
         <img src="/assets/console/api-keys-light.png" alt="Tilebox Console" className="dark:hidden"  />

diff --git a/workflows/concepts/task-runners.mdx b/workflows/concepts/task-runners.mdx
@@ -366,4 +366,4 @@ This mechanism ensures that scenarios such as power outages, hardware failures,
 
 ## Observability
 
-Task runners are continuously running processes, making it essential to monitor their health and performance. You can achieve observability by collecting and analyzing logs, metrics, and traces from task runners. Tilebox Workflows provides tools to enable this data collection and analysis. To learn how to configure task runners for observability, head over to the [Observability](/workflows/observability) section.
+Task runners are continuously running processes, making it essential to monitor their health and performance. Tilebox Workflows collects logs and traces from task runners automatically. To learn how to inspect and customize workflow observability, see [Observability](/workflows/observability/introduction).
Original file line number	Diff line number	Diff line change
Expand Up		@@ -366,4 +366,4 @@ This mechanism ensures that scenarios such as power outages, hardware failures,

		## Observability

		Task runners are continuously running processes, making it essential to monitor their health and performance. You can achieve observability by collecting and analyzing logs, metrics, and traces from task runners. Tilebox Workflows provides tools to enable this data collection and analysis. To learn how to configure task runners for observability, head over to the [Observability](/workflows/observability) section.
		Task runners are continuously running processes, making it essential to monitor their health and performance. Tilebox Workflows collects logs and traces from task runners automatically. To learn how to inspect and customize workflow observability, see [Observability](/workflows/observability/introduction).