How long each job takes
const url = 'http://localhost:11044/api/v1/activity/stats';const options = {method: 'GET', headers: {'X-Embabel-Api-Key': '<X-Embabel-Api-Key>'}};
try { const response = await fetch(url, options); const data = await response.json(); console.log(data);} catch (error) { console.error(error);}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.
Authorizations
Section titled “Authorizations”Responses
Section titled “Responses”Per-job durations, slowest tail first
How long each job takes over its most recent runs since the app started, answered by GET /activity/stats
object
One entry per job, slowest 95th percentile first
One job’s run durations, in milliseconds
object
How many of the counted runs failed
What starts the job
The job’s label, the same sentence the activity list shows for its runs
When the job’s latest counted run ended, an ISO-8601 UTC instant
Longest counted run in milliseconds
True when the job runs for the caller; false for the appliance’s own, which carries no user
Median run duration in milliseconds
95th-percentile run duration in milliseconds
Runs counted, at most runsPerJob
How many of each job’s most recent runs the figures cover, at most
When the oldest run counted here began, an ISO-8601 UTC instant. Null when nothing has settled since the app started
Example
{ "jobs": [ { "kind": "BACKGROUND" } ]}
