Reports, analytics, notifications, and automation rules

Running in production today: reports, asset reports, automation rules, notifications, activity logs, and the calendar.

The module ships two ways to get a report. Standard reports are fixed, per-module generators — executive summary, tickets, assets, security, firewall, servers, websites, audit logs, user activity and enterprise risk — that answer the common questions with no configuration beyond filters and a date range. They are the fastest route to a board pack or a monthly operations summary, because the layout and the queries are already decided.

The Report Builder covers everything the fixed set does not. You choose a data source from the builder registry (assets, tickets, patches, MDM devices, VAPT findings), a dimension to group by, a metric to aggregate, plus filters, a date range and a time grain. The result renders as a bar, line or pie chart, a table or a scorecard, and saves as a named custom report your team can re-run. The practical split: reach for a standard report when the question is routine, and the builder when someone asks something like "open tickets by category over the last quarter, weekly" — a query no fixed template happens to match.

Both kinds of report respect the same tenant boundary. A template or custom report belongs to your organization and aggregates only your organization's rows, so a report built by one tenant can never surface another tenant's data.

Delivery scheduling uses a cron expression on the template, evaluated by a beat task that runs hourly. That design has an honest consequence we state plainly: the minute field of the cron is ignored. Hour, day-of-month, month and day-of-week are honoured, so you choose the hour a report lands — "9am every Monday", "6pm on the 1st" — not the exact minute. For management reporting that trade is invisible; for anything needing minute precision, run the report on demand instead.

When a schedule matches, the task renders every due template in its configured format — PDF, CSV or Excel — and emails it to the recipient list. A recurring report you set up once keeps arriving without anyone remembering to run it, and changing the template changes every future delivery, because the schedule renders from the saved configuration each time rather than from a frozen copy.

The three formats map to three audiences. PDF is the executive artifact: something a director opens on a phone and reads as-is. CSV feeds whatever comes next — a pivot table, a BI import, a reconciliation script. Excel suits the manager who wants to sort and annotate before forwarding. Because the format lives on the template, the same saved configuration can exist in two variants — a PDF for leadership and a CSV for the analyst — without either owner maintaining the other's copy.

Automated reporting fails quietly in most tools: the job errors, nobody notices, and weeks later someone asks why the numbers stopped arriving. Infronest writes every outbound email — scheduled reports, notifications, SLA messages and alerts — to an email-audit log with the recipient, subject, category and a sent, failed or queued status.

That log turns "did the compliance report actually go to the auditor?" from a guess into a lookup. A failed row shows you the delivery that bounced the day it bounced, and a clean run of sent rows is evidence you can point at when someone claims a report never came. Because the log is tenant-scoped like everything else, each organization audits only its own deliveries.

The coverage is wider than reports alone: the same log captures notification, SLA and alert emails, each tagged with its category. So when an SLA-breach warning or a monitoring alert is disputed — "we were never told" — the delivery record for that exact message, with its status and timestamp, settles the question.