Platform
System monitoring: the workspace's health and issues on one screen
System monitoring in ArkanERP is the «System health» screen where a workspace's administrator sees its state now: whether it answers and how fast, how many errors were logged, whether scheduled jobs run, when the last backup was taken, and whether ZATCA rejected invoices. Each issue shows with its cause, its level and a button to the list it is fixed from, and events such as sign-ins, submissions and errors appear as they happen, with who did them. The platform's team watches every server at the same time.
- The workspace read every five minutes
- Each issue with its cause and a button to it
- Live events with who did them
- The platform takes counts and states, not your data
What System monitoring does
One picture of the workspace
The workspace's state, healthy, warning or stopped, from a score its open issues make, with its users, who is online now and its uptime over thirty days. Its server shows as a state only, with no figures and no other business named.
Speed and errors
The time within which 95% of requests are served, requests per minute, server errors in the last quarter hour, what the error log took in the last hour and day, and the workspace not answering.
Background jobs and the scheduler
A scheduler that is off or stalled, the one that runs notifications, backups and depreciation, and jobs that failed in the last day; the system manager has a button that starts the scheduler again.
Backups
No backup, or an old last one, a copy that failed to reach cloud storage, and a failed monthly test restore of the latest copy.
ZATCA and email
Invoices ZATCA rejected in the last day, invoices waiting to be sent, and emails that failed to go out.
Sign-ins and permissions
Failed sign-ins, the System Manager role given to a user, and a new API key, each an event with a warning. Each IP address has a card with its successful and failed sign-ins over seven days and its open sessions.
Events as they happen
A live log of every sign-in, failed sign-in, submission, cancellation, error and ZATCA acceptance or rejection, with the user and the document, beside the requests as they are served.
Incidents with an action
Each issue is an incident with its level, cause, first and last seen, marked as seen when read, and its button opens the error log, job log, rejected invoices, email queue, backups, sign-in log or users.
Seven views and a wall screen
The live map, the operations board, the central station, the operations log, the geography of visitors' addresses and of devices whose browsers allowed it, the radar and the grid; each opens as a window of its own on a large screen.
How the work flows
- 1
Adding it
The monitoring app is added to the workspace from the platform's console, and the System Health Monitor role given to whoever follows it.
- 2
Reading
The platform reads the workspace every five minutes and hands back its picture and history; when it can't be reached, the workspace is read on its own.
- 3
Alert
An issue appears as an incident with its cause and level, and events in the live log as they happen.
- 4
Fix
The incident's button opens where it is fixed, and once its cause is gone it leaves the picture on the next reading.
Questions about System monitoring
Who sees the system health screen?
The workspace's system manager and whoever is given the System Health Monitor role, once the app is added to the workspace from the platform's console on request.
Does the platform see my business's data?
No. The platform takes counts and states only, with no amounts, parties, document names or users; who did what, on which document, shows only on the workspace's own screen.
Is anyone told when the workspace stops?
Yes. The platform's team is told at once when a workspace or server stops or a threat is seen, and the issue shows on the workspace's screen for its administrator.
What if the platform can't be reached?
The workspace's state is read in the workspace itself, without the history and past incidents the platform keeps.
Does monitoring catch break-in attempts?
Failed sign-ins and each address's card show on the screen, and the platform blocks addresses that guess passwords or probe the server automatically, on all its servers.
Systems that work with it
- Cloud and data securityArkanERP in the cloud: a separate database per business, encrypted nightly backups off the server, admin sign-in codes, automatic attack blocking, restore.
- Permissions and controlArabic permissions: per-user rights per screen, limits by company, branch and warehouse, users enter and managers approve, and an audit trail of every change.
- ZATCA e-invoicingPhase 2 link with ZATCA's Fatoora: signed invoices with QR codes, clearance of tax invoices, reporting of simplified ones, branches, and every invoice tracked.
- Integrations and APIConnect ArkanERP to your systems: a REST API with per-user keys, webhooks on events, WhatsApp Business, payment gateways, email, ZATCA and Excel imports.
- Electronic archiveDocument archiving: numbered documents with QR labels, SHA-256-fingerprinted versions, three confidentiality levels, voucher attachments archived on approval.