Core Concepts

Understanding EdLog's core concepts will help you design an effective monitoring strategy for your infrastructure.

Organizations (Accounts)

Organizations are the top-level container in EdLog. Each organization is completely isolated and can have multiple users, project groups, and billing settings.

  • • Separate data isolation per organization
  • • Independent API keys and rate limits
  • • Team member management with roles
  • • Unified billing and usage tracking

Project Groups

Project groups organize related projects together. Use them to logically separate different environments, customers, or application clusters.

Examples

  • • Production Apps
  • • Staging Environment
  • • Customer Sites
  • • Internal Tools
  • • Infrastructure Services

Benefits

  • • Visual organization
  • • Bulk operations
  • • Permission management
  • • Separate dashboards
  • • Group-level settings

Projects

Projects represent individual applications, services, or systems you want to monitor. Each project has its own API key and event stream.

Project Properties

Name Human-readable identifier (e.g., "API Server")
Key Unique slug used in API calls (e.g., "api-server")
API Key Authentication token for sending events
Description Optional notes about the project

Events

Events are the fundamental data unit in EdLog. Every piece of information sent to EdLog is an event with a consistent structure.

Event Lifecycle

  1. Event received via webhook API
  2. Validated and stored in database
  3. Processed by matching tile rules
  4. Tile states updated based on rules
  5. Notifications triggered if configured
  6. Dashboard updates in real-time

Dashboard Tiles

Tiles are visual components that display the current state of your systems based on incoming events. They react to events through configurable rules.

Tile Types

  • Deploy: Deployment pipeline status
  • Uptime: Service availability
  • Error: Error tracking
  • Metric: Numeric values & gauges
  • Status: Generic status display

Tile States

  • ● OK: Normal operation
  • ● Info: Informational
  • ● Warning: Attention needed
  • ● Error: Problem detected
  • ● Unknown: No data

Rules Engine

Rules determine how tiles react to events. They evaluate incoming events and update tile states accordingly.

Rule Components

  • Conditions: What to match (event type, name, attributes)
  • Actions: What to do when matched
    • Set tile state (OK, Warning, Error)
    • Update tile content
    • Trigger notifications
    • Execute webhooks
  • Priority: Order of evaluation (higher priority first)

Data Flow

Your Apps Webhooks EdLog API Events Rules Engine Updates Dashboard

Input Sources

  • • CI/CD pipelines
  • • Monitoring tools
  • • Application logs
  • • Custom scripts

Output Actions

  • • Real-time dashboard updates
  • • Email/Slack notifications
  • • Webhook callbacks
  • • Historical tracking

Ready to Start?