Skip to main content

Console overview

The console at app.wakora.io is where everything the agents collect becomes visible and actionable: hosts, websites, APM, RUM, logs, security, incidents, alerting, status pages, team and billing.

Signing in​

Sign in with email and password, or with Google, Microsoft, or Slack. Two-factor authentication, once enabled in My account, asks for a code delivered to your Telegram, browser push, or email. Forgot password sends a reset link that is valid for one hour. Workspaces on Business and above can additionally claim their company sign-in domain so colleagues join automatically, see Team and access.

New here? Create workspace on the sign-in page registers you and creates your own workspace in one step, with email and password or straight through Google. The console speaks 28 languages; pick yours in My account.

Workspaces​

A workspace (your team) owns hosts, sites, incidents, members and billing. You can be a member of several workspaces: the switcher in the top bar changes the active one, and the console remembers your last choice per device. Everything you see is scoped to the active workspace, always.

The left sidebar lists the modules: Dashboard, Hosts, Devices, APM, RUM, Uptime, Logs, Security, Incidents, Events, Alerting, Reports, Status pages, Marketplace, Billing, Settings. What you see depends on three things: your plan (modules outside the plan do not appear), your role in this workspace (the permissions matrix controls both menu items and actions), and what has shipped: a dimmed item with a version badge is a module that is coming, and clicking it says so instead of pretending.

The search palette (the search box in the top bar) finds hosts, sites, incidents by number or text, status pages, and offers "search this in logs" as a jump.

The console is live​

Pages breathe on their own: grids, charts, feeds and incident lists refresh every 30 to 120 seconds without a reload, and role or permission changes reach open sessions immediately. Most time charts support time travel: click a point (or a day in a year strip) to pin the whole page to that moment, and "back to live" resumes.

The pill in the top bar tells you whether the monitoring behind the console is healthy. Live is the normal state. Alerts paused means telemetry is still arriving but no incidents are being raised at the moment (a planned maintenance of the platform, or a fault on our side); it clears by itself. Offline means the console cannot reach the monitoring data at all: pages that are built from telemetry (hosts, APM, logs, devices) open as grey skeletons instead of errors, and the parts that live in the console itself (incidents, rules, team, billing) keep working. Nothing is sent or published while the console is offline, so a report cannot go out empty and a status page cannot flip to "resolved" on missing data.

Phones and tablets​

The console adapts: on a phone the sidebar becomes a bottom tab bar plus a sheet with every module, and detail pages get a back arrow in the top bar. Everything works, ack and resolve included.

Where things live, in one breath​