Skip to main content

Abyss Monitor

Abyss Monitor is Abyss' observability service for your Applications: logs, events, server performance, Cron Tasks, Sentinels and alert webhooks — all gathered in a unified dashboard.

What you can do​

  • Publish structured logs from your Application (info, warn, error, debug)
  • Track endpoints being hit (method, status, duration, body)
  • Publish business events and auto-aggregate them (a.b.c → a, a.b)
  • Publish server performance stats (CPU, memory, disk)
  • Configure distributed Cron Tasks (guaranteed trigger + logging)
  • Watch uptime with Sentinels (PING, HTTP, TCP)
  • Receive webhooks on events or Sentinel state changes
  • Get automatic Discord alerts on errors

Getting started​

Monitor has no dedicated app. You browse your dashboards from the main Abyss app and publish data from your code.

  1. Create a Project and an Application — see Projects & Applications
  2. Enable the Abyss Monitor service on your organization — see Enabling services
  3. Grab your Application API Key and your secretPublishToken
  4. Set up the Core package inside your project
  5. Follow the Logger, Performance stats and Middleware pages

Sharing and access​

A Monitor Application belongs to a Project and an organization. To open dashboard access:

  • share the Application with other members — see Share content
  • limit to a team or a project

Permissions​

Inside a Monitor Application, members need the following permissions:

PermissionAction
MONITOR_READOpen the dashboard
MONITOR_LOG_READView logs
MONITOR_STATS_READView server stats
MONITOR_EVENT_READ / CREATE / DELETEManage events
MONITOR_SENTINEL_READ / CREATE / UPDATE / DELETEManage Sentinels
MONITOR_CRON_TASK_READ / CREATE / UPDATE / DELETE / REGENERATE_SECRETManage Cron Tasks
MONITOR_RESET_SECRET_PUBLISH_TOKENReset the publish token
STORAGE_WEBHOOK_READ / CREATE / UPDATE / DELETE / RESET_SECRETManage webhooks
STORAGE_WEBHOOK_HISTORY_READView webhook history

API and SDK​