Operations
Operations
Eden Operations keeps health, usage, cost, incidents, recommendations, fleet state, and deployment activity in the same operating model as the work itself. It connects request-level evidence to the services, endpoints, models, agents, migrations, and runtimes responsible for an outcome.
Operate your deployment
Start with installation and the production profile, then use:
- Configuration reference and its generated field catalog.
- Backup, restore and disaster recovery.
- Upgrade and rollback.
- Recovery runbooks and diagnostic bundles.
- Telemetry integrations and monitoring/alerts.
- Release and endpoint compatibility.
Capabilities
| Capability | What it covers | Start here |
|---|---|---|
| Live operations | Current health, activity, and service state across connected systems. | Operations And Observability |
| Workload intelligence | Request patterns, latency, errors, resource use, and dependency behavior. | Analytics APIs |
| Recommendations & optimization | Prioritized actions derived from workload and infrastructure evidence. | AI Orchestration Analytics |
| Incidents & investigations | Correlated signals, timelines, affected resources, and investigation context. | Operational APIs |
| Fleet & runtime health | Node enrollment, availability, compatibility, utilization, and runtime state. | Runtime and Fleet |
| Costs & usage | Model, token, request, endpoint, tenant, and capacity attribution. | Analytics APIs |
| Logs, metrics & traces | Safe telemetry from fleet-level health to individual requests. | Operations And Observability |
| Deployments | Release state, rollout activity, health, and operational evidence. | Operational APIs |
Operating model
Operational records use safe identifiers, hashes, counts, statuses, route and provider identifiers, policy decisions, audit references, and correlation IDs. Credentials, raw prompts, query bodies, document contents, and unredacted sensitive values must not appear in telemetry or exports.