Acumen Logs Knowledge Hub

Who it's for: Teams getting started with Acumen Logs or onboarding new collaborators.
You’ll learn: Platform pillars, key concepts, and where to dive deeper next.

Welcome to the Acumen Logs Knowledge Hub. This living library captures everything you need to plan, configure, and maintain reliable monitoring for your applications, APIs, and infrastructure.


Platform Highlights

  • Unified Monitoring: Track synthetic journeys, uptime checks, heartbeats, SSL, WHOIS, and API monitors from one dashboard.
  • Actionable Observability: Dive into rich request traces, console logs, Lighthouse insights, and video recordings to pinpoint issues quickly.
  • Smart Alerting: Route incidents to email, Slack, Microsoft Teams, desktop notifications, or webhooks with configurable thresholds and quiet hours.
  • Workflow Friendly: Use integrations (GitHub Actions, Zapier, WHMCS, webhooks) to fold monitoring into your CI/CD and support processes.
  • Team Ready: Organize by projects, manage access with roles, and keep stakeholders informed with sharing links and exports.

Core Monitoring Types

Monitoring Type When to Use It Key Outcomes
Synthetic Monitoring Validate critical user flows such as checkout, onboarding, and search. Video replays, console logs, per-request timings, Lighthouse scores.
Uptime Monitoring Ensure URLs, APIs, and services stay reachable worldwide. Global response-time trends, regional health, incident history.
Heartbeat Monitoring Confirm scheduled jobs, daemons, and background workers run on time. Missed heartbeat detection, SLA tracking, programmatic alerting.
SSL & WHOIS Track certificate and domain expirations. Automated renewal reminders, compliance visibility.
Real User Monitoring (RUM) Measure real-world performance in production. User-centric performance analytics, Core Web Vitals perspective.

Key Concepts

  • Projects: Buckets that group monitors, alerts, and reports. Organize by product line, client, environment, or campaign.
  • Journeys: Reusable collections of scripted steps that mirror real customer flows (login, add-to-cart, checkout, etc.).
  • Locations: Global points-of-presence that execute tests; mix regions to detect localized incidents.
  • Fail Conditions: Business rules that decide when an execution is considered unhealthy (status codes, response duration, JavaScript errors, asset failures).
  • Notifications: Channel-specific policies that balance fast reaction with low noise (fail counts, escalation paths, maintenance windows).

Getting Started

  1. Create a Project: Head to the Projects page and add your first container.
  2. Add Monitors: Start with uptime for your public endpoints, then layer synthetic checks for mission-critical journeys.
  3. Define Alerts: Configure alert channels and thresholds before you go live. Use the built-in test buttons to validate routing.
  4. Share Context: Invite teammates, export dashboards, or wire up upstream tools (Slack, Teams, PagerDuty via webhooks, Zapier).
  5. Review Regularly: Schedule retrospectives that inspect failure trends, slow regions, and expiring certificates.

Where to Go Next

  • Projects: Learn strategies for structuring workspaces at scale.
  • Monitoring Guides: Step-by-step walkthroughs for creating Synthetic, Uptime, and Heartbeat monitors.
  • Dashboards: Deep dives into result interpretation, diagnosis workflows, and response optimization.
  • Integrations: Automate handoffs with GitHub Actions, Zapier, WHMCS, and custom webhooks.
  • Advanced Playbooks: Explore API monitoring, automation pipelines, and maintenance retrospectives for mature operations.

📌 Tip: Each article in this hub is tagged with quick navigation anchors so you can jump straight to the section you need. Use the table of contents at the top of every page inside the LaRecipe sidebar.