|
Mantis - Resin
|
|||||
| Viewing Issue Advanced Details | |||||
|
|
|||||
| ID: | Category: | Severity: | Reproducibility: | Date Submitted: | Last Update: |
| 6300 | minor | always | 12-08-19 22:24 | 02-19-20 13:58 | |
|
|
|||||
| Reporter: | nam | Platform: | |||
| Assigned To: | OS: | ||||
| Priority: | normal | OS Version: | |||
| Status: | closed | Product Version: | 4.0.64 | ||
| Product Build: | Resolution: | fixed | |||
| Projection: | none | ||||
| ETA: | none | Fixed in Version: | 4.0.65 | ||
|
|
|||||
| Summary: | 0006300: improve pdf-report downtime reporting at the beginning of the query range | ||||
| Description: |
(rep by M. Shimomura) The pdf-report queries the internal log/stat database for downtimes. If the date for the query range cuts off some Resin lifecycle events, then Resin would report the beginning of the range as a downtime. It is misleading for downtime reporting to depend on the query range. The attached screenshot shows a 5-day downtime, which is not correct. We should: 1. improve docs and wording in pdf-report, and/or 2. do a backward scan of the database looking for the start event |
||||
| Steps To Reproduce: | |||||
| Additional Information: | |||||
| Relationships | |||||
| Attached Files: |
|
||||
| There are no notes attached to this issue. |