grafloki

$npx mdskill add kurtosis-tech/kurtosis/grafloki

Centralize and visualize logs from multiple services by deploying Grafana and Loki.

  • Debug complex, multi-service issues requiring correlated log viewing.
  • Integrates with Kurtosis enclaves to collect and store service output.
  • Executes setup and teardown commands to manage the logging stack.
  • Provides a web UI via Grafana for advanced log querying and filtering.

SKILL.md

.github/skills/graflokiView on GitHub ↗
---
name: grafloki
description: Start Grafana and Loki for centralized log collection from Kurtosis enclaves. View aggregated service logs in a Grafana dashboard. Use when you need a UI for browsing logs across multiple services or want persistent log storage.
compatibility: Requires kurtosis CLI with a running engine.
metadata:
  author: ethpandaops
  version: "1.0"
---

# Grafloki

Start a Grafana + Loki stack for centralized log collection from Kurtosis enclaves.

## Start

```bash
kurtosis grafloki start
```

This creates a Grafana instance with Loki as a data source, collecting logs from all services in all enclaves.

## Stop

```bash
kurtosis grafloki stop
```

## Usage

After starting, open the Grafana URL shown in the output. Use the Explore view with the Loki data source to query logs:

- Filter by service name
- Search for specific log patterns
- View logs across multiple services side by side

## When to use

- Debugging multi-service issues where you need correlated logs
- Monitoring long-running enclaves
- When `kurtosis service logs` isn't enough (need search, filtering, time ranges)

More from kurtosis-tech/kurtosis

SkillDescription
cli-local-buildBuild and test the Kurtosis CLI from source. Compile the CLI binary locally, run it against Docker or Kubernetes engines, and iterate on CLI changes without creating a release. Use when developing or debugging CLI commands.
cluster-manageManage Kurtosis cluster settings. Switch between Docker and Kubernetes backends, list available clusters, and configure which cluster Kurtosis uses. Use when you need to change where Kurtosis runs enclaves.
context-manageManage Kurtosis contexts for connecting to different Kurtosis instances. Add, list, switch, and remove contexts. Use when working with multiple Kurtosis environments (local, remote, team shared).
docker-debugDebug Kurtosis running on local Docker. Inspect engine, API container, and service logs. Diagnose container crashes, port conflicts, and networking issues. Use when kurtosis commands fail or services aren't reachable on Docker.
docker-local-buildBuild and test Kurtosis from source on local Docker. Compiles all components (engine, core, files-artifacts-expander), builds Docker images, installs the CLI, and restarts the engine. Use when developing Kurtosis and testing changes locally with Docker.
dumpDump Kurtosis state for debugging and sharing. Export enclave state including service logs, configurations, and file artifacts to a local directory. Use when you need to capture state for offline analysis or to share with others for debugging.
enclave-inspectInspect and manage Kurtosis enclaves. List enclaves, view services and ports, examine file artifacts, dump enclave state for debugging, and clean up. Use when you need to understand what's running inside an enclave or export its state.
engine-manageManage the Kurtosis engine server. Start, stop, restart the engine, check status, and view engine logs. Covers both Docker and Kubernetes engine backends. Use when the engine won't start, needs restarting, or you need to check engine health.
files-inspectInspect, download, upload, and debug Kurtosis file artifacts. View artifacts in an enclave, download them locally for inspection, upload local files, and troubleshoot file mounting issues. Use when services can't find expected files or configs are wrong.
gatewayStart and manage the Kurtosis gateway for Kubernetes. The gateway forwards local ports to the Kurtosis engine and services running in a k8s cluster. Required when using Kurtosis with Kubernetes. Use when kurtosis engine status shows nothing on k8s or services aren't reachable.