Skip to main content

PyPI Python License

evoid-dashboard

Monitoring dashboard — Intent Handler system

Quick Start • Intent Handler • API Endpoints


Quick Start

uv add evoid-dashboard
from evoid_dashboard import register_handlers

# Register dashboard as adapter handler
register_handlers(host="0.0.0.0", port=8001)

Method 2: Direct API

from evoid_dashboard import create_dashboard

app = create_dashboard(port=8001)

Intent Handler

evoid-dashboard registers monitoring endpoints as Intent handlers.


API Endpoints

Endpoint Method Description
/services GET List all registered services
/intents GET List all registered intents
/processors GET List all registered processors
/messages GET Message bus history
/health GET Dashboard health check

Configuration

TOML

[engines]
dashboard = "dashboard"

[engines.options.dashboard]
host = "0.0.0.0"
port = 8001

How It Works

The dashboard reads from EVOID's internal registries:

  • Intent registry — all registered Intents with levels and pipelines
  • Processor registry — all registered processors
  • Message bus history — recent Intent executions

No DI integration needed — it observes the runtime directly.

Dependencies

  • evoid>=0.4.0

License

MIT

Metadata

Release files for evoid-dashboard 0.2.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Built distribution (wheel)

Table of built distributions (wheels) for evoid-dashboard 0.2.0
File Interpreter ABI Platform Actions
evoid_dashboard-0.2.0-py3-none-any.whl Python 3 none any Details for evoid_dashboard-0.2.0-py3-none-any.whl

Release files / evoid_dashboard-0.2.0-py3-none-any.whl

Download URL evoid_dashboard-0.2.0-py3-none-any.whl
Size 8.8 kB
Tags Python 3
SHA-256 checksum
How to use checksums
52b4986943c220087a140c9da4f133c4a3b2e6f4bdd4d6093b078598c5c1b7b1
BLAKE2b-256 checksum
How to use checksums
6bcd5b473680581b19429b31884ea07185a341eaa2590078519725091daa06b3
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via uv/0.12.3 {"installer":{"name":"uv","version":"0.12.3","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}

Security for evoid-dashboard 0.2.0

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

No provenance found

None of the files in this release were uploaded with provenance metadata.

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page