Statistics

Detailed metrics and analytics for deployment activity and resource usage.

Statistics API

Endpoints

Endpoint	Scope	Access
GET /api/v1/statistics	The caller’s own scope	Users with statistics:read

A tenant-scoped user always receives their own tenant’s statistics. A platform administrator receives the whole platform, and may narrow to one tenant with tenant_id; that parameter is ignored for tenant-scoped users, who cannot widen their scope.

Platform-only fields (tenant_count, top_tenants) are null for a tenant-scoped caller; tenant identifies the tenant when the result is confined to one.

Query Parameters

period is the window discriminant; days, since and until are subordinate to it, and supplying one against the wrong period is a 400.

Parameter	Values	Default	Description
period	day, week, month, quarter, year, relative, custom	week	Time window for statistics
days	Positive integer	none	Rolling window length, with period=relative
since	RFC 3339 instant	none	Lower bound, with period=custom
until	RFC 3339 instant	none	Upper bound, with period=custom
tenant_id	Tenant UUID	none	Platform admins only: narrow scope

# Statistics for your own scope over the last calendar month
curl -H "Authorization: Bearer $TOKEN" \
  "https://mantis.example.com/api/v1/statistics?period=month"

# A rolling window of the last 45 days
curl -H "Authorization: Bearer $TOKEN" \
  "https://mantis.example.com/api/v1/statistics?period=relative&days=45"

# An explicit range
curl -H "Authorization: Bearer $TOKEN" \
  "https://mantis.example.com/api/v1/statistics?period=custom&since=2026-07-01T00:00:00Z&until=2026-07-19T00:00:00Z"

# Platform admins: narrow to one tenant
curl -H "Authorization: Bearer $TOKEN" \
  "https://mantis.example.com/api/v1/statistics?tenant_id=019b937d-a39a-8bd5-ad63-b6c422fb96dc&period=week"

Deployment Statistics

State Breakdown

Deployments are categorized by their final state:

Every state below is counted in total. Queued has no field of its own: it is reported together with Pending under by_state.pending.

State	Description	Reported as	Counted As
Pending	Awaiting dispatch	pending	In-progress
Queued	Dispatched, not yet started	pending	In-progress
Running	Currently executing	running	In-progress
Succeeded	Completed successfully	succeeded	Success
Failed	Completed with errors	failed	Failure
Cancelled	Manually stopped	cancelled	Neither
RolledBack	Superseded by a rollback	rolled_back	Neither

{
  "by_state": {
    "pending": 5,
    "running": 10,
    "succeeded": 142,
    "failed": 8,
    "cancelled": 3,
    "rolled_back": 2
  }
}

Success Rate

Calculated as the percentage of successful deployments out of all deployments in the period:

success_rate = (succeeded / total) × 100

total is the sum of every state in the breakdown — pending (including queued), running, succeeded, failed, cancelled and rolled back. All deployments in the period contribute to the denominator. A row whose status the platform does not define is left out of both.

Example:

• 5 pending + 10 running + 142 succeeded + 8 failed + 3 cancelled + 2 rolled back = 170 total
• Success rate = 142 / 170 × 100 = 83.5%

Average Duration

Mean execution time for completed deployments:

{
  "avg_duration_ms": 45200
}

Display formats:

Duration	Format
< 1 second	850ms
< 1 minute	45.2s
≥ 1 minute	2.5m

Tip

Average duration helps identify performance trends. A sudden increase may indicate infrastructure issues.

Deployment Trends

Daily Counts

Statistics include daily deployment counts for trend visualization:

{
  "deployment_trend": [
    { "date": "2024-01-15", "count": 28, "succeeded": 26, "failed": 2 },
    { "date": "2024-01-16", "count": 32, "succeeded": 30, "failed": 2 },
    { "date": "2024-01-17", "count": 25, "succeeded": 24, "failed": 1 },
    { "date": "2024-01-18", "count": 35, "succeeded": 33, "failed": 2 },
    { "date": "2024-01-19", "count": 20, "succeeded": 19, "failed": 1 },
    { "date": "2024-01-20", "count": 8, "succeeded": 8, "failed": 0 },
    { "date": "2024-01-21", "count": 8, "succeeded": 7, "failed": 1 }
  ]
}

Trend Analysis

The trend data enables:

Analysis	Insight
Daily volume	Identify peak deployment days
Failure spikes	Detect problematic releases
Weekend patterns	See reduced activity periods
Growth trends	Track deployment frequency over time

        Mon   Tue   Wed   Thu   Fri   Sat   Sun
Count    28    32    25    35    20     8     8
Success  26    30    24    33    19     8     7
Failed    2     2     1     2     1     0     1
Rate    92%   94%   96%   94%   95%  100%   88%

Resource Counts

Tenant Resources

Resources scoped to the current tenant:

Resource	Description
solutions	Number of solution packages
targets	Registered deployment targets
environments	Deployment environments
variables	Configuration variables
tags	Organization tags

Global Resources

Resources shared across all tenants:

Resource	Description
sequences	Shared execution sequences
actions	Shared action definitions

{
  "resource_counts": {
    "solutions": 12,
    "targets": 24,
    "environments": 4,
    "variables": 156,
    "tags": 18,
    "sequences": 8,
    "actions": 24
  }
}

Activity Feed

Activity Entries

Recent system activity is tracked:

{
  "recent_activity": [
    {
      "timestamp": "2024-01-21T14:30:00Z",
      "event_type": "deployment_success",
      "description": "Deployment web-app completed successfully",
      "resource_type": "deployment",
      "resource_id": "019b937d-a39a-8bd5-ad63-b6c422fb96dc",
      "resource_name": "web-app",
      "user": "alice@example.com"
    },
    {
      "timestamp": "2024-01-21T14:15:00Z",
      "event_type": "deployment_failed",
      "description": "Deployment api-service failed",
      "resource_type": "deployment",
      "resource_id": "019b937d-78bc-8a32-a79f-fefe5386b887",
      "resource_name": "api-service",
      "user": "bob@example.com"
    }
  ]
}

Event Types

The activity feed surfaces deployment lifecycle events. The event_type field is derived from the deployment status:

Event Type	Description
deployment_pending	Deployment created, waiting to start
deployment_queued	Deployment queued for execution
deployment_running	Deployment is executing
deployment_success	Deployment completed successfully
deployment_failed	Deployment failed
deployment_cancelled	Deployment was cancelled
deployment_rolled_back	Deployment was rolled back

The rule is literal: event_type is deployment_ plus the deployment status, so any status the enum renders can appear here.

Activity Timeline

┌───────────────────────────────────────────────────────────┐
│ Recent Activity                                           │
├───────────────────────────────────────────────────────────┤
│                                                           │
│ ● 14:30  deployment_success                             │
│          web-app completed successfully                   │
│          by alice@example.com                             │
│                                                           │
│ ● 14:15  deployment_failed                                │
│          api-service failed                               │
│          by bob@example.com                               │
│                                                           │
│ ● 13:45  deployment_running                               │
│          backend-services started                         │
│          by carol@example.com                             │
│                                                           │
│ ● 13:00  deployment_cancelled                             │
│          web-app v1.2.2 was cancelled                     │
│          by dave@example.com                              │
│                                                           │
└───────────────────────────────────────────────────────────┘

Top Tenants

Global Dashboard Only

Administrators see top tenants ranked by activity:

{
  "top_tenants": [
    {
      "tenant_id": "019b937d-a39a-8bd5-ad63-b6c422fb96dc",
      "tenant_name": "Acme Corp",
      "deployment_count": 48,
      "success_rate": 97.9
    },
    {
      "tenant_id": "019b937d-78bc-8a32-a79f-fefe5386b887",
      "tenant_name": "Beta Inc",
      "deployment_count": 32,
      "success_rate": 93.8
    },
    {
      "tenant_id": "019b937d-4172-8af3-aea8-5c3919af26a9",
      "tenant_name": "Gamma LLC",
      "deployment_count": 28,
      "success_rate": 89.3
    }
  ]
}

Tenant Ranking

┌─────────────────────────────────────────────────────────────┐
│  Top Tenants by Deployment Activity                        │
├─────────────────────────────────────────────────────────────┤
│                                                             │
│  ┌────────────────┬──────────────┬────────────────────┐   │
│  │ Tenant         │ Deployments  │ Success Rate       │   │
│  ├────────────────┼──────────────┼────────────────────┤   │
│  │ 🥇 Acme Corp   │ 48           │ 97.9% ████████████│   │
│  │ 🥈 Beta Inc    │ 32           │ 93.8% ███████████ │   │
│  │ 🥉 Gamma LLC   │ 28           │ 89.3% ██████████  │   │
│  │    Delta Co    │ 15           │ 86.7% █████████   │   │
│  │    Epsilon Ltd │ 12           │ 91.7% ███████████ │   │
│  └────────────────┴──────────────┴────────────────────┘   │
│                                                             │
└─────────────────────────────────────────────────────────────┘

Target Health Statistics

Status Breakdown

Status	Description
Online	Target has an active session with its assigned Thorax instance
Stale	No heartbeat within the heartbeat timeout (default 90 s); the target then dwells Stale for the stale timeout (default 300 s) before going Offline
Offline	No heartbeat received within the liveness window (default 360 s); also the initial state for targets that have never connected

Health Metrics

Target health counts are not part of the statistics API response (which carries deployment_stats, resource_counts, and recent_activity). Query target health via the targets API (GET /api/v1/targets, filterable by status) or the real-time SSE target stream.

Health Percentage

┌─────────────────────────────────────────────────────────────┐
│  Target Health                                              │
├─────────────────────────────────────────────────────────────┤
│                                                             │
│  Online: 83% ██████████████████████████████████░░░░░░░░    │
│                                                             │
│  ┌──────────┬──────────┬──────────┬──────────┐            │
│  │  Total   │  Online  │  Stale   │ Offline  │            │
│  │    24    │    20    │    2     │    2     │            │
│  │          │ (83.3%)  │ (8.3%)   │ (8.3%)   │            │
│  └──────────┴──────────┴──────────┴──────────┘            │
│                                                             │
└─────────────────────────────────────────────────────────────┘

Time Periods

Period Mapping

Period	Days	Date Range Example
day	1	Jan 21 only
week	7	Jan 15 - Jan 21
month	30	Dec 22 - Jan 21
quarter	90	Oct 23 - Jan 21
year	365	Jan 22, 2023 - Jan 21, 2024

Selecting Periods

Via Lens UI:

Period: [Last 7 Days        ▼]
        ┌─────────────────────┐
        │ Last 24 Hours       │
        │ Last 7 Days       ● │
        │ Last 30 Days        │
        │ Last 90 Days        │
        │ Last Year           │
        └─────────────────────┘

Via the REST API, select the period with the ?period= query parameter — a calendar window (day, week, month, quarter, year), a rolling one (relative with days), or an explicit range (custom with since/until):

curl "$MANTIS_URL/api/v1/statistics?period=day"   -H "Authorization: Bearer $TOKEN"
curl "$MANTIS_URL/api/v1/statistics?period=week"  -H "Authorization: Bearer $TOKEN"
curl "$MANTIS_URL/api/v1/statistics?period=month" -H "Authorization: Bearer $TOKEN"
curl "$MANTIS_URL/api/v1/statistics?period=relative&days=90" -H "Authorization: Bearer $TOKEN"

API Usage

Statistics are exposed through the REST API (and the Lens dashboard); there is no mantisctl statistics subcommand.

Global Statistics

# Statistics for the caller's scope (requires statistics:read)
curl "$MANTIS_URL/api/v1/statistics?period=week" \
  -H "Authorization: Bearer $TOKEN"

Tenant Statistics

# Narrow to one tenant (platform administrators only)
curl "$MANTIS_URL/api/v1/statistics?tenant_id=<tenant-id>&period=week" \
  -H "Authorization: Bearer $TOKEN"

A tenant-scoped user does not need this: GET /api/v1/statistics already returns their own tenant, and tenant_id is ignored for them.

Exporting Statistics

The endpoint returns JSON. Pipe the response through jq (or redirect to a file) to capture or transform it:

# Save raw JSON
curl -s "$MANTIS_URL/api/v1/statistics?period=month" \
  -H "Authorization: Bearer $TOKEN" > stats.json

Best Practices

1. Monitor Success Rate Trends

Track success rate over time:

Trend	Interpretation	Action
Stable > 95%	Healthy	Continue monitoring
Declining	Problems emerging	Investigate recent changes
Volatile	Inconsistent	Review deployment practices
Below 90%	Critical	Immediate investigation

2. Set Alert Thresholds

Recommended alert thresholds:

Metric	Warning	Critical
Success Rate	< 95%	< 90%
Avg Duration	> 2× baseline	> 5× baseline
Failed Deployments	> 3 per day	> 10 per day
Offline Targets	> 5%	> 10%

3. Review Regularly

Frequency	Focus
Daily	Current activity, failures
Weekly	Trends, patterns
Monthly	Growth, capacity
Quarterly	Performance optimization

4. Use Appropriate Time Periods

Scenario	Recommended Period
Troubleshooting	Last 24 Hours
Weekly reports	Last 7 Days
Trend analysis	Last 30 Days
Capacity planning	Last 90 Days
Annual review	Last Year

Troubleshooting

Statistics Not Loading

Cause: Permission or connectivity issue

Solution:

1. Verify authentication token is valid
2. Confirm your role has the statistics:read permission (admin, operator, or viewer)
3. Confirm network connectivity to API

Stale Data

Cause: SSE disconnected or aggregator lag

Solution:

1. Click refresh button
2. Check SSE connection status
3. Verify aggregator service is running

Missing Trend Data

Cause: Period too short or no deployments

Solution:

1. Extend the window — a longer period, or period=relative&days=<n>
2. Verify deployments occurred in the window
3. Check deployment filters

Next Steps

• Real-time Updates - Live statistics updates
• Dashboard Overview - Dashboard features
• Audit Logs - Detailed event logging