monitoring

A set of rules for monitoring Forklift, a tool that moves virtual machines between systems. It exposes Prometheus metrics—measurements that monitoring systems can collect—over a secured HTTPS endpoint.

In plain words
What is it for?
Use it to track migration outcomes, plan states, alerts, controller loops, and inventory activity in Prometheus.
Why use it?
It makes migration activity and controller health visible without adding metrics by hand. This helps operators spot failures, alerts, and changing workloads.

Cursor rule for Cursor

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add rules/kubev2v/forklift-console-plugin/monitoring
Clone the repo
git clone --depth 1 https://github.com/kubev2v/forklift-console-plugin

Made for: Cursor.

Per session 13 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,026 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00013 $0.01026
Opus 5 $0.00006 $0.00513
Sonnet 5 $0.00003 $0.00205
Haiku 4.5 $0.00001 $0.00103

Measured 2d ago against content hash c822113d65a1, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

monitoring scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.cursor/rules/backend/infrastructure/monitoring.mdc · 89 lines

How it starts

The opening of the file, as written. The whole thing — 89 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Monitoring & Metrics

Source: pkg/monitoring/, pkg/metrics/

Prometheus Endpoint

pkg/metrics/promethousutil.go (sic — typo in upstream Go source) → StartPrometheusEndpoint(certsDirectory)

  • Generates a self-signed TLS cert/key pair at startup.
  • Serves /metrics over HTTPS on port 8443 using promhttp.Handler().
  • All metrics auto-registered via promauto (no manual prometheus.Register calls).

Metrics Defined

All metrics live in pkg/monitoring/metrics/forklift-controller/metrics.go.

Counters

Metric Type Labels Purpose
mtv_migrations_status_total CounterVec status, provider, mode, target Total VM migrations by terminal status
mtv_workload_migrations_status_total CounterVec status, provider, mode, target, plan Same but correlated to a specific plan UID

Gauges

Metric Type Labels Purpose
mtv_plans_status GaugeVec status, provider, mode, target Current plan counts by status (reset each cycle)
mtv_plan_alert_status GaugeVec status, provider, mode, target, plan, plan_name, phase Per-plan alerting (1 = active, deleted when resolved)
mtv_migration_duration_seconds GaugeVec provider, mode, target, plan Duration of completed migrations
mtv_migration_data_transferred_bytes GaugeVec provider, mode, target, plan Total bytes transferred (updated during execution and on completion)

Histograms

Metric Type Labels Buckets
mtv_migrations_duration_seconds HistogramVec provider, mode, target 1h, 2h, 5h, 10h, 24h, 48h (in seconds)

Label Value Constants

status:   Succeeded, Failed, Executing, Running, Pending, Canceled, Completed, Blocked, Ready, Deleted
provider: oVirt, VSphere, Openstack, OVA, Openshift
mode:     Cold, Warm
target:   Local (dest URL empty), Remote (dest URL set)

Collection Loops

Both run as background goroutines, polling every 10 seconds.

Read the full file on GitHub · 89 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 2d ago First seen · 89 lines · 13 tokens per session scan A c822113d65a1

Subscribe to this mod's changes

monitoring is a cursor rule published in the GitHub repository kubev2v/forklift-console-plugin (11 stars, last pushed 2d ago), licensed Apache-2.0. It adds 13 tokens to every session and 1,026 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.