Expose queue stats #2

Closed
opened 2021-10-26 09:36:26 +02:00 by erth9960 · 2 comments
Owner

It should be possible to read information about the queue via an API endpoint.

The endpoint should be /status/queue. Output data format should be json.

When accessing /status/queue, the application should return a list of all queued jobs. The following parts of each queue item should be included:

  • type
  • id (the queue item filename)
  • title
  • description
  • courses
  • presenters
  • tags
  • creation time (from json data)
  • upload time (queue file creation time)

Basically everything that isn't a URL or path.

It should be possible to read information about the queue via an API endpoint. The endpoint should be /status/queue. Output data format should be json. When accessing /status/queue, the application should return a list of all queued jobs. The following parts of each queue item should be included: - type - id (the queue item filename) - title - description - courses - presenters - tags - creation time (from json data) - upload time (queue file creation time) Basically everything that isn't a URL or path.
Author
Owner

If an item has corresponding error data, that should be included in the job's json object as well under the key error.
The key should be omitted if there is no error.

If an item has corresponding error data, that should be included in the job's json object as well under the key `error`. The key should be omitted if there is no error.
dafo5502 self-assigned this 2021-10-26 09:52:44 +02:00
dafo5502 added a new dependency 2021-10-26 09:54:50 +02:00
Author
Owner
See also https://gitea.dsv.su.se/DMC/play-daemon/issues/5
Sign in to join this conversation.
No Label
No Milestone
1 Participants
Notifications
Due Date
No due date set.
Reference: DMC/play-api#2
No description provided.