Activity, notifications and support

The console keeps you informed in four places, all under your organization: Activity, Notifications (the bell), Alerts and Monitoring. When something is wrong and the docs don’t help, open a support ticket.

Activity

Activity is your organization’s audit log: every change and every denied attempt, from the console, the CLI and the API, newest first. Each entry says who did it, what they did, to which resource, from which address, and which policy statement allowed it. The list updates every few seconds, so a change you just made shows up almost at once.

Filter by service (compute, network, IAM, billing…), time, outcome (succeeded, denied, failed) or actor (a principal TRN). A resource’s own page shows just its history.

Reading activity needs the audit:ListEvents action; the ReadOnly, ProjectMember and ProjectAdmin policies include it. Members whose policies are limited to one project see that project’s activity. Actions taken by TebibHost staff or the platform appear as TebibHost, without staff names or addresses.

Notifications

The bell in the top bar counts unread notifications. They tell you when something happened that you may need to act on:

Notification	When
Balance running low, new resources blocked, VMs stopped, resources deleted	The low-balance state changes
Top-up received	A payment is credited
VM stopped for balance, held for abuse, stopped unexpectedly	TebibHost stops or restarts a VM
Organization suspended or reinstated	An abuse decision
New reply, ticket resolved or closed	Support answers your ticket
New sign-in, access key created	Security events on your own account

You only see notifications about things you may read: billing notices need billing access, a VM’s notices need access to that VM, and security notices go only to the person they are about. Marking one read only marks it for you. Most of them are also sent by email.

Alerts

Alerts are what needs attention now: a low balance, VMs stopped by TebibHost, a quota at 90 % or more of its limit, a ticket waiting for your answer. An alert clears by itself once its cause is fixed: top up, start the VM, free some quota or reply.

Monitoring

Monitoring lists every project with its VMs: power state, why a VM is stopped, its size and what it cost this month. Open a VM for its CPU, memory and network charts.

Support tickets

For SSH trouble, a slow or stopped VM, or a question about spend, Ogbai can often answer right away, and opens a ticket with the conversation attached when it can’t.

Open a ticket from Support in the console or from the Help panel:

1. Give a short subject, pick a category (technical, billing, account, abuse, other) and a severity (low to urgent), and the project if it is about one.
2. Describe what happened: the resource names or IDs, what you expected and what you saw, and when it started.
3. Attach screenshots, logs or configs if they help: PNG, JPEG, PDF, text, JSON, zip or gzip, up to 5 files and 4 MB per message. Never attach passwords or private keys.

You get an email when support replies, and the ticket shows Waiting for you until you answer. A resolved ticket opens again when you reply; a closed one stays closed (open a new one). The OrgOwner, ProjectAdmin, ProjectMember and Billing policies can open and answer tickets; ReadOnly can read them. A suspended organization can still use support.