Change Details

ElectronPDF came with a stats dashboard (available here: https://grafana.wikimedia.org/dashboard/db/mediawiki-electronpdfservice?orgId=1) The new Chromium-PDF service should provide at least the same set of stats: == Acceptance criteria We would be tracking the following: [X] rejected jobs [X] queued jobs by type (desktop|mobile] [X] size of the queue when new job comes in [X] number of rendered jobs (daily, monthly) NOTE: StatsD flushes metrics to Graphite every 10 s (the default value of `config.flushInterval`). Aggregation of time series is done in Graphite. Grafana is a frontend for Graphite. Just increment the `num_rendered_jobs` metric whenever a job is rendered and rely on the Grafana/Graphite/StatsD pipeline to do the rest 💪 [X] number of failed renderings [X] time each job spends in the queue [X] time each job spends in the rendering state [X] might be helpful: generated pdf size [Please do not add to this list, once this task is done additional analytics can be easier] == Sign off steps [] Set up dashboard.

ElectronPDF came with a stats dashboard (available here: https://grafana.wikimedia.org/dashboard/db/mediawiki-electronpdfservice?orgId=1) The new Chromium-PDF service should provide at least the same set of stats: == Acceptance criteria We would be tracking the following: [X] rejected jobs [X] queued jobs by type (desktop|mobile] [X] size of the queue when new job comes in [X] number of rendered jobs (daily, monthly) NOTE: StatsD flushes metrics to Graphite every 10 s (the default value of `config.flushInterval`). Aggregation of time series is done in Graphite. Grafana is a frontend for Graphite. Just increment the `num_rendered_jobs` metric whenever a job is rendered and rely on the Grafana/Graphite/StatsD pipeline to do the rest 💪 [X] number of failed renderings [X] time each job spends in the queue [X] time each job spends in the rendering state [X] might be helpful: generated pdf size [Please do not add to this list, once this task is done additional analytics can be easier] == Sign off steps [x] Set up dashboard.

ElectronPDF came with a stats dashboard (available here: https://grafana.wikimedia.org/dashboard/db/mediawiki-electronpdfservice?orgId=1) The new Chromium-PDF service should provide at least the same set of stats: == Acceptance criteria We would be tracking the following: [X] rejected jobs [X] queued jobs by type (desktop|mobile] [X] size of the queue when new job comes in [X] number of rendered jobs (daily, monthly) NOTE: StatsD flushes metrics to Graphite every 10 s (the default value of `config.flushInterval`). Aggregation of time series is done in Graphite. Grafana is a frontend for Graphite. Just increment the `num_rendered_jobs` metric whenever a job is rendered and rely on the Grafana/Graphite/StatsD pipeline to do the rest 💪 [X] number of failed renderings [X] time each job spends in the queue [X] time each job spends in the rendering state [X] might be helpful: generated pdf size [Please do not add to this list, once this task is done additional analytics can be easier] == Sign off steps [x] Set up dashboard.