Who actually works in mail and cloud storage
Staff activity reports come from the corporate service audit logs, not from asking managers.
Task
“We need to see who works in corporate mail and storage, by department and by month. Asking managers gives impressions, not facts.”
Solution
Audit-log collection from Yandex 360 via API, event breakdown by person and department, monthly reports showing spikes and silence.
Result
234 peoplein one report, no manual exports
7 reportsmonthly, repeatable with one command
factsinstead of impressions
How it works
Logs from two different sources
Audit events live in two places: the organisation-wide journal and the separate mail and storage journals, with different endpoints and permissions. Collection covers both, otherwise half of the activity is invisible.
Events become metrics
Raw events — sign-ins, sent mail, file operations — are reduced to readable rows: who, how much, when. Monthly breakdowns by person and department follow, with spikes and quiet periods highlighted.
A report you can repeat
Each month the summary is rebuilt with one command, without manual exports or stitched spreadsheets. API access is granted with read-only audit scopes and nothing more.
integrations
scope
Access and scopes, audit-log collection from two sources, metric model, monthly reports, rerun instructions.