Skip to content

How long each job takes

GET
/api/v1/activity/stats
curl --request GET \
--url http://localhost:11044/api/v1/activity/stats \
--header 'X-Embabel-Api-Key: <X-Embabel-Api-Key>'

Per job: runs counted, failures among them, median, 95th percentile and longest duration, slowest tail first. Over each job’s most recent runs since the app started; since is when the oldest run counted began, null when nothing has run.

Per-job durations, slowest tail first

Media typeapplication/json

How long each job takes over its most recent runs since the app started, answered by GET /activity/stats

object
jobs
required

One entry per job, slowest 95th percentile first

Array<object>

One job’s run durations, in milliseconds

object
failures
required

How many of the counted runs failed

integer format: int32
kind
required

What starts the job

string
Allowed values: BACKGROUND HANDLER SCHEDULED POLL
label
required

The job’s label, the same sentence the activity list shows for its runs

string
lastEndedAt
required

When the job’s latest counted run ended, an ISO-8601 UTC instant

string
maxMs
required

Longest counted run in milliseconds

integer format: int64
mine
required

True when the job runs for the caller; false for the appliance’s own, which carries no user

boolean
p50Ms
required

Median run duration in milliseconds

integer format: int64
p95Ms
required

95th-percentile run duration in milliseconds

integer format: int64
runs
required

Runs counted, at most runsPerJob

integer format: int32
runsPerJob
required

How many of each job’s most recent runs the figures cover, at most

integer format: int32
since

When the oldest run counted here began, an ISO-8601 UTC instant. Null when nothing has settled since the app started

string

Example

{
"jobs": [
{
"kind": "BACKGROUND"
}
]
}