====== Reporting ======

The **Reporting** tile (**View > Reporting**, or the **Reports** quick action) shows how busy the board is.

{{ :v4:images:dispatch-reporting.png?900 |The Reporting tile}}
//Figure 1. Reporting for the last 7 days, by day.//

===== What it shows =====

  * **A toolbar** with the range: **Today**, **Yesterday**, **7 days**, **30 days** or **60 days**, **By hour** or **By day**, and **Export CSV**. By hour is offered up to 7 days.
  * **Five number boxes**: **Calls** (with the average per day), **Failed logins** (with the average per day), **Peak sessions** (the most callers open at the same time), **Average call** (about, per session) and **Busiest hour of day** (the hour, for example 09:00 - 10:00, and how many calls it had).
  * **Calls per hour or day**, as a stacked bar chart split by service, with a legend that shows the total for each (Telnet, RLogin, FTP, Web, NNTP and BinkP in the picture).
  * **Calls by service**: a bar for each service with its count and its share of all calls.
  * **Busiest hours**: the top five single hours, with their dates, and a small chart of **calls by hour of the day**, from 0 to 23. The busiest clock hour is shown in amber.
  * **Failed logins per hour or day**.

Days and hours are in your local time.

===== Good to know =====

  * History is kept for 60 days. The footer tells you if the range you picked is only partly covered.
  * Failed logins come from the Login Guard. At start PBDispatch reads them back from ''LOGINGUARD.LOG'', so counts survive a restart. Log rotation can limit how far back they go.
  * **Average call** is an estimate. Web and BinkP calls are not counted, because they have no session length.
  * **Export CSV** saves the numbers for a spreadsheet.