Change Details

As a Wikisource user, I want baseline data related to ebook exports to be established by the Community Tech team, so they can set goals for potential improvements and track progress. **Background:** As part of our Wikisource work, we hope to improve the overall reliability of ebook exports. In order to effectively do this, we need to have a current understanding of overall reliability. The purpose of this ticket is to identify how we can determine this data and to then go ahead and retrieve the data. There are 3 main types of issues we encounter with ebook exports: 1) the tool doesn't work at all (which we can track with uptimerobot), 2) the tool technically works but there are errors (which we can track with other error logs, potentially logstash, as an example), 3) formatting & styles issues (which we need to get from direct examples & feedback from users -- this isn't easy to track). **Acceptance Criteria:** * Collect information on the following: ** Total number of ebook exports in the last 30 days, 60 days, and 90 days (logs are at https://wsexport.wmflabs.org/logs/ --> how can I easily access/analyze them?) ** Total number of WSExport connection timeouts in the past month, date of timeout, and duration of timeout (you can use T226136 as a model) ** Current uptime stats for the last 24 hours, 30 days, 60 days, and 90 days * Determine how we can collect logged data on ebook export errors (for example, can this be done in logstash), which may include: *** Linting errors *** Export tool errors out * Determine the number of the errors for the last 24 hours, 30 days, 60 days, and 90 days, if possible? * Can we generate data on any changes that may have occurred in uptime and reliability from before and after the [[ https://phabricator.wikimedia.org/T242760 | move to VPS ]]? * General question: Is UptimeRobot giving us a complete picture of uptime, or is anything missing? Just want to check in about this.

As a Wikisource user, I want baseline data related to ebook exports to be established by the Community Tech team, so they can set goals for potential improvements and track progress. **Background:** As part of our Wikisource work, we hope to improve the overall reliability of ebook exports. In order to effectively do this, we need to have a current understanding of overall reliability. The purpose of this ticket is to identify how we can determine this data and to then go ahead and retrieve the data. There are 3 main types of issues we encounter with ebook exports: 1) the tool doesn't work at all (which we can track with uptimerobot), 2) the tool technically works but there are errors (which we can track with other error logs, potentially logstash, as an example), 3) formatting & styles issues (which we need to get from direct examples & feedback from users -- this isn't easy to track). **Acceptance Criteria:** * Collect information on the following: ** Total number of ebook exports in the last 30 days, 60 days, and 90 days (logs are at https://wsexport.wmflabs.org/logs/ --> how can I easily access/analyze them?) ** Total number of WSExport connection timeouts in the past month, date of timeout, and duration of timeout (you can use T226136 as a model). ** Current uptime stats for the last 24 hours, 30 days, 60 days, and 90 days ** Do we know which file formats are downloaded most often right now from the export tool? ** Do we know what % of traffic to WS is from mobile? * Determine how we can collect logged data on ebook export errors (for example, can this be done in logstash), which may include: *** Linting errors *** Export tool errors out * Determine the number of the errors for the last 24 hours, 30 days, 60 days, and 90 days, if possible? * Can we generate data on any changes that may have occurred in uptime and reliability from before and after the [[ https://phabricator.wikimedia.org/T242760 | move to VPS ]]? * General question: Is UptimeRobot giving us a complete picture of uptime, or is anything missing? Just want to check in about this.

As a Wikisource user, I want baseline data related to ebook exports to be established by the Community Tech team, so they can set goals for potential improvements and track progress. **Background:** As part of our Wikisource work, we hope to improve the overall reliability of ebook exports. In order to effectively do this, we need to have a current understanding of overall reliability. The purpose of this ticket is to identify how we can determine this data and to then go ahead and retrieve the data. There are 3 main types of issues we encounter with ebook exports: 1) the tool doesn't work at all (which we can track with uptimerobot), 2) the tool technically works but there are errors (which we can track with other error logs, potentially logstash, as an example), 3) formatting & styles issues (which we need to get from direct examples & feedback from users -- this isn't easy to track). **Acceptance Criteria:** * Collect information on the following: ** Total number of ebook exports in the last 30 days, 60 days, and 90 days (logs are at https://wsexport.wmflabs.org/logs/ --> how can I easily access/analyze them?) ** Total number of WSExport connection timeouts in the past month, date of timeout, and duration of timeout (you can use T226136 as a model). ** Current uptime stats for the last 24 hours, 30 days, 60 days, and 90 days ** Do we know which file formats are downloaded most often right now from the export tool? ** Do we know what % of traffic to WS is from mobile? * Determine how we can collect logged data on ebook export errors (for example, can this be done in logstash), which may include: *** Linting errors *** Export tool errors out * Determine the number of the errors for the last 24 hours, 30 days, 60 days, and 90 days, if possible? * Can we generate data on any changes that may have occurred in uptime and reliability from before and after the [[ https://phabricator.wikimedia.org/T242760 | move to VPS ]]? * General question: Is UptimeRobot giving us a complete picture of uptime, or is anything missing? Just want to check in about this.