Skip to main content
Video tutorial · 2:31

PDF reports

The Reports page (left menu, Overview) builds a PDF of the selected project. You can download one at any time, or create a scheduled report that CertAutoPilot e-mails with the PDF attached — every day, on chosen weekdays, or once a month, at the time you pick.

Reports are available to users with the operator role or higher in the project.

What a report contains​

You choose the sections; all four are selected by default.

SectionContents
CertificatesTotals (all, active, expiring in 30 days, failed jobs); the certificates in service by time left — past expiry, 0–3, 3–7, 7–30 and over 30 days, and no date; counts by status and by issuer; the certificates expiring within the window you set (1–365 days, default 30); and the certificates whose renewal failed or that expired, with their last error (failed renewals soonest expiry first, expired ones most recent first). In service means active, or with a renewal or re-issue pending, running or failed — the current certificate still serves; the "expiring in 30 days" figure is the 0–3, 3–7 and 7–30 day columns together. Like the dashboard, each window is capped at a third of the certificate's lifetime, so a freshly issued short-lived certificate is counted in "over 30 days" until its last third.
DistributionDistributions by last result, and the ones whose last run failed, was partial or is unverified, with the error.
47-day readinessThe readiness score, automation and distribution coverage, recommended actions, the breakdown by issuer and the certificates at risk under shorter lifetimes.
DiscoverySources, certificates and endpoints found, managed and not managed, expiring and expired, risk counts, open findings by severity with the most severe ones, and post-quantum readiness (certificate keys and servers by key exchange).

Every table lists at most 500 rows; a longer list says how many more there are. The data is a snapshot taken when the report is built. Times are shown in the scheduled report's timezone, or in your browser's timezone for a download.

Emoji and other pictographs in names are left out of the PDF. Characters the embedded font cannot draw — for example Chinese, Japanese or Arabic script — are printed as ?. A very long value is shortened in its table cell and in the page header.

Whose view a report shows​

A report is always built with one user's access:

  • a download — the user who downloads it;
  • a scheduled report — the user who owns the subscription (its creator).

A user limited to granted resources gets only what they were granted: a certificate they cannot see never appears in their report, not even in the totals. The PDF says so on its first page.

If the visible discovery data of a limited user is too large to compute, the Discovery section (or only its key-exchange table) says it could not be computed and the rest of the report is still sent.

Scheduled reports​

Click New scheduled report and set:

  • Sections and the expiring-certificates window.
  • How often — Daily, Weekly (one or more weekdays) or Monthly (day 1–28, so every month has it), at a time in a timezone.
  • Send through — an SMTP notification channel of the project. A user limited to granted resources needs at least viewer on that channel.
  • Send to me — the e-mail address on your profile. Add one on the Profile page first; an LDAP or SSO account cannot edit it there — it comes from the directory or the identity provider when the user signs in. CertAutoPilot does not verify this address; the report sent there holds only what you may see, the same as a download.
  • Other recipients — at most 50 addresses. Only a project admin with access to the whole project can add them, and only on a scheduled report whose owner is such an admin too (their own, or another whole-project admin's): the report is built with its owner's access, so the recipients receive everything that admin sees. Anyone who may edit the report can remove addresses.

Every recipient gets a message of their own, so nobody sees the other addresses, and an address the mail server refuses does not stop the others (the last result names it). Each recipient is recorded as soon as the mail server accepts its message, so a send that is retried or picked up again never mails the same person twice.

Send now mails the report at once without changing the schedule. The table shows the next send time and the last result; hover a failed result to read the reason.

An operator sees and manages only their own scheduled reports; a project admin sees and manages every one in the project. A project admin limited to granted resources is treated like an operator here: own reports only, and no other recipients. One user can have at most 50 scheduled reports in a project.

Turning a scheduled report off always works, even when its owner has lost the e-mail address or the channel; those are checked when it is turned on or saved active. The report of a deactivated owner cannot be turned on. Editing a report without changing its schedule keeps the pending send time, so a change made just after the send time does not skip that send — and does not repeat a send already under way. Changing the schedule (or turning the report off) drops a send time that was not delivered yet. The timezone must be a named zone (for example Europe/Istanbul or UTC). The table shows the next send time in the report's own timezone.

At most 10 scheduled reports are started per minute: when many are due at the same time, the rest go out over the following minutes (100 reports due at once are all sent within about 10 minutes).

While the cluster still runs a node of an earlier version (during an upgrade), creating a scheduled report and Send now are refused with CLUSTER_UPGRADE_REQUIRED — an older node does not run report sends. Finish the upgrade first.

When a report is not sent​

SituationWhat happens
The SMTP server refuses every recipient, the credentials are wrong, or the channel is turned off or no longer visible to the ownerThe run is recorded as Failed with the reason; the subscription stays on and tries again at its next time. A temporary SMTP or network error gets up to three tries in total; only the outcome of the last one is recorded.
The mail server refuses some of the recipientsThe others get the report; the result is Sent and names the addresses that were refused. A temporary refusal is tried again (for that address only) before it is named.
Send to me is off and there are no other recipients that can be sent toThe run fails at every send time (no recipient) until the report is edited.
The owner's account is deleted or deactivated, or the owner no longer has the operator role in the projectThe subscription is turned off and says why. Deleting a user also deletes their subscriptions.
The owner is no longer a project admin with access to the whole projectThe other recipients are skipped and the report goes to the owner only (when Send to me is on — otherwise the run fails: no recipient); the last result says so.
A worker stops in the middle of a sendThe same job is picked up again and sends that time's report to the recipients that did not get it yet.
The report cannot be drawn (a fault in the PDF library)The run is recorded as Failed with the reason; it is not retried.
CertAutoPilot was down at the send timeOne report is sent when it is back; missed times are not sent one by one.

A notification channel that a scheduled report uses cannot be deleted, and neither can a project that still has scheduled reports — delete or edit them first.

Audit​

Creating, changing, deleting, Send now and downloads are recorded in the audit log (REPORT_SUBSCRIPTION_CREATED, …_UPDATED, …_DELETED, REPORT_SEND_REQUESTED, REPORT_DOWNLOADED), and every scheduled or manual send writes REPORT_SENT, REPORT_SEND_FAILED or REPORT_SEND_SKIPPED with the number of recipients. The job log and the project audit log are readable by everyone in the project (a user limited to granted resources sees only its own report entries in the audit log), so they never list the other recipients: the audit record counts them, and addresses in a failure message are shortened to their first letter and domain (b***@example.com). The full list is on the scheduled report itself, for the people who may manage it.

Rate limits: downloads 10 per minute per user and 30 per project; Send now 5 per minute per user and 15 per project; creating, saving and deleting scheduled reports 30 per minute per project.

Video tutorial

Short, hands-on videos showing this feature working for real. English audio, English and Turkish subtitles. All video tutorials →

Email Notifications, Scheduled Reports and Syslog to Your SIEMYouTube ↗