Status

The Log10x Status Page at status.log10x.com provides real-time health monitoring for all Log10x services. Built on Upptime, it runs automated checks every 5 minutes and publishes uptime history.

How It Works

graph LR
    A["<div style='font-size: 16px;'>⏰ Scheduler</div><div style='font-size: 14px;'>GitHub Actions</div>"] --> B["<div style='font-size: 16px;'>🔍 Health Checks</div><div style='font-size: 14px;'>HTTP GET Requests</div>"]
    B --> C["<div style='font-size: 16px;'>📊 Status Update</div><div style='font-size: 14px;'>GitHub Pages</div>"]
    C --> D["<div style='font-size: 16px;'>🌐 Status Page</div><div style='font-size: 14px;'>status.log10x.com</div>"]

    classDef scheduler fill:#6366f1,stroke:#4f46e5,color:#ffffff,stroke-width:2px,rx:8,ry:8
    classDef checks fill:#059669,stroke:#047857,color:#ffffff,stroke-width:2px,rx:8,ry:8
    classDef update fill:#ea580c,stroke:#c2410c,color:#ffffff,stroke-width:2px,rx:8,ry:8
    classDef page fill:#0891b2,stroke:#0e7490,color:#ffffff,stroke-width:2px,rx:8,ry:8

    class A scheduler
    class B checks
    class C update
    class D page

Step	Description
⏰ Scheduler	GitHub Actions runs automated checks every 5 minutes
🔍 Health Checks	HTTP GET requests to each service endpoint
📊 Status Update	Results committed to GitHub repository
🌐 Status Page	Static site served via GitHub Pages

Monitored Services

The status page monitors five critical Log10x services:

Service	Endpoint	Expected Response	Check Interval
🖥️ Console	`https://console.log10x.com`	HTTP 200	5 minutes
⚡ API	`https://api.log10x.com/health`	HTTP 200	5 minutes
📊 Metrics	`https://prometheus.log10x.com/health`	HTTP 200	5 minutes
🔐 Identity	`https://auth.log10x.com/.well-known/openid-configuration`	HTTP 200	5 minutes
📈 Grafana	AWS Managed Grafana `/api/health`	HTTP 200	5 minutes

REST Endpoints for Integration

You can integrate Log10x status checks into your own monitoring system using these public endpoints:

Health Check Endpoints

🖥️ Console⚡ API🔐 Auth📊 Metrics

curl -s -o /dev/null -w "%{http_code}" https://console.log10x.com

Response	Meaning
`200`	Console is operational
`5xx`	Console is experiencing issues

curl -s https://api.log10x.com/health

Expected Response:

{"status": "healthy"}

Response	Meaning
`200` + JSON	API is operational
`5xx`	API is experiencing issues

curl -s https://auth.log10x.com/.well-known/openid-configuration

Expected Response: OIDC discovery document (JSON)

Response	Meaning
`200` + JSON	Auth is operational
`5xx`	Auth is experiencing issues

curl -s https://prometheus.log10x.com/health

Expected Response:

{"status": "healthy"}

Response	Meaning
`200` + JSON	Metrics API is operational
`5xx`	Metrics API is experiencing issues

Status API (Upptime)

The Upptime-powered status page exposes JSON data you can query programmatically:

Summary History RSS Feed

curl -s https://raw.githubusercontent.com/log-10x/status/master/history/summary.json

Returns current status of all monitored services with uptime percentages.

Individual service history files:

# Console history
curl -s https://raw.githubusercontent.com/log-10x/status/master/history/console.yml

# API history
curl -s https://raw.githubusercontent.com/log-10x/status/master/history/api.yml

# Auth history
curl -s https://raw.githubusercontent.com/log-10x/status/master/history/auth.yml

Subscribe to status updates via RSS:

https://raw.githubusercontent.com/log-10x/status/master/history/rss.xml

Integration Examples

Prometheus Shell Script Kubernetes Datadog

Monitor Log10x endpoints with Prometheus Blackbox Exporter:

# blackbox.yml
modules:
  http_2xx:
    prober: http
    timeout: 5s
    http:
      valid_status_codes: [200]
      fail_if_ssl: false
      preferred_ip_protocol: ip4

# prometheus.yml
scrape_configs:
  - job_name: 'log10x-status'
    metrics_path: /probe
    params:
      module: [http_2xx]
    static_configs:
      - targets:
          - https://console.log10x.com
          - https://api.log10x.com/health
          - https://prometheus.log10x.com/health
          - https://auth.log10x.com/.well-known/openid-configuration
          - https://g-3fb6644a79.grafana-workspace.us-east-1.amazonaws.com/api/health
    relabel_configs:
      - source_labels: [__address__]
        target_label: __param_target
      - source_labels: [__param_target]
        target_label: instance
      - target_label: __address__
        replacement: blackbox-exporter:9115

Simple health check script for cron or CI/CD:

#!/bin/bash
# log10x-health-check.sh

SERVICES=(
    "Console|https://console.log10x.com"
    "API|https://api.log10x.com/health"
    "Metrics|https://prometheus.log10x.com/health"
    "Identity|https://auth.log10x.com/.well-known/openid-configuration"
    "Grafana|https://g-3fb6644a79.grafana-workspace.us-east-1.amazonaws.com/api/health"
)

for service in "${SERVICES[@]}"; do
    name="${service%%|*}"
    url="${service##*|}"
    status=$(curl -s -o /dev/null -w "%{http_code}" --max-time 10 "$url")
    if [ "$status" = "200" ]; then
        echo "✅ $name: OK"
    else
        echo "❌ $name: FAILED (HTTP $status)"
    fi
done

Use as external dependency check in your deployments:

# Use Log10x API health endpoint as external dependency check
livenessProbe:
  httpGet:
    path: /health
    port: 8080
  initialDelaySeconds: 30
  periodSeconds: 10

Add Log10x endpoints to Datadog Synthetic Monitoring:

# datadog-synthetics.yaml
- name: Log10x Console
  type: api
  subtype: http
  request:
    method: GET
    url: https://console.log10x.com
  assertions:
    - type: statusCode
      operator: is
      target: 200
  locations:
    - aws:us-east-1
  options:
    tick_every: 300  # 5 minutes

Incident Notifications

When a service goes down:

📋 GitHub Issue created automatically with incident details
📊 Status page updates within 5 minutes
📝 History recorded for uptime calculations

View past incidents at status.log10x.com.

Response Time Thresholds

The status page monitors response times with these thresholds:

Service	Max Response Time
🖥️ Console	5,000 ms
⚡ API	3,000 ms
📊 Metrics	3,000 ms
🔐 Identity	5,000 ms
📈 Grafana	5,000 ms

Services exceeding these thresholds may be marked as degraded even if returning HTTP 200.

Resources

Resource	Link
Status Page	status.log10x.com
Status Repository	github.com/log-10x/status
Upptime Documentation	upptime.js.org