What is the Status Page?
Our Platform Status Page provides real-time information about the health and performance of all Elementum services. This page is your go-to resource for:- Current System Status: See which services are operational, experiencing issues, or under maintenance
- Historical Uptime: View performance metrics over the past 90 days
- Incident Updates: Get detailed information about any ongoing issues or maintenance
- Service Components: Monitor individual service areas like Core, API, Automations, and Agents
Why Monitor Platform Status?
Proactive Issue Awareness
Instead of wondering if a problem is on your end or ours, check the status page first. This helps you:- Verify Service Health: Confirm if Elementum services are running normally
- Plan Around Maintenance: Be aware of scheduled maintenance windows
- Understand Impact: Know which specific services might be affected during incidents
- Reduce Support Tickets: Check status before contacting support for system-wide issues
Business Continuity
When you’re experiencing issues, the status page helps you:- Assess Scope: Determine if the problem is isolated to your instance or affecting all users
- Communicate with Stakeholders: Provide accurate information about service status
- Plan Workarounds: Understand which features might be temporarily unavailable
- Track Resolution: Monitor incident progress and estimated resolution times
Available Services
The status page monitors these key service areas:Core Platform
Main application functionality, user interface, and core features
API Services
REST API endpoints and integration services
Automations
Workflow automation engine and trigger systems
Agents
AI agent services and intelligence features
Status Indicators
The status page uses clear visual indicators to communicate service health:- 🟢 Operational: Service is running normally with no issues
- 🟡 Degraded Performance: Service is experiencing performance issues but remains functional
- 🟠 Partial Outage: Some features or regions are experiencing issues
- 🔴 Major Outage: Service is experiencing significant disruption
- 🔵 Maintenance: Planned maintenance is in progress
Subscribe to Notifications
Stay informed about platform status without constantly checking the status page. You can subscribe to receive email notifications for:- Incident Creation: When a new issue is identified
- Status Updates: Progress updates during incident resolution
- Resolution Notifications: When issues are resolved
- Maintenance Alerts: Scheduled maintenance notifications
How to Subscribe
- Visit status.elementum.io
- Click “Get email notifications” at the top of the page
- Enter your email address
- Verify your email with the OTP sent to your inbox
- You’ll receive notifications for all future incidents and updates
Programmatic Access via API
For developers and automated systems, you can programmatically access status information through our REST API endpoints. All endpoints return JSON data and don’t require authentication.Core Endpoints
Core Endpoints
Summary - Complete status overviewStatus - Overall indicator (Components - Individual service statuses (
none
, minor
, major
, critical
) and descriptionoperational
, degraded_performance
, partial_outage
, major_outage
)Incidents
Incidents
Status:
Impact:
Investigating
, Identified
, Monitoring
, Resolved
, Postmortem
Impact:
None
, Minor
, Major
, Critical
Scheduled Maintenances
Scheduled Maintenances
Status:
Impact:
Scheduled
, In Progress
, Verifying
, Completed
Impact:
None
, Minor
, Major
, Critical
Example Usage
Example Usage
Integration with Support
The status page works alongside our other support resources:- Check Status First: Always verify platform status before contacting support
- Reference in Tickets: Include status page information when reporting issues
- Follow Incident Updates: Use status updates to track resolution progress
- Escalate Appropriately: Contact support if status shows operational but you’re still experiencing issues
Need Help?
If you have questions about the status page or need assistance with platform issues:- Email Support: support@elementum.elementum.io
Appendix: Datadog Integration Setup
Monitor Elementum’s platform status programmatically using Datadog Synthetic tests. This setup automatically alerts your team when services experience issues, providing proactive incident awareness.Option A: Simple Status Monitoring
Option A: Simple Status Monitoring
Goal: Alert whenever the platform status indicator isn’t
none
(i.e., any degraded/partial/outage condition).Create the Test
- Navigate to Datadog → Synthetic Monitoring & Testing → New test → New API test → HTTP
- Configure the request:
- Method:
GET
- URL:
https://status.elementum.io/api/v2/status.json
- Method:
Add Assertions
After clicking Send, add these assertions:- Status code → is →
200
- Header
content-type
→ matches regex →application/json
- Body → JSONPath → Path:
$.status.indicator
→ Operator: is → Value:none
The key assertion is
$.status.indicator is none
. When the indicator becomes minor
, major
, or critical
, this assertion fails and triggers your alert.Configure Monitoring
- Locations: Select 1-3 managed locations near your users
- Frequency: Set to every 1-5 minutes based on your needs
- Alert conditions: Configure “Alert if failing for 2 minutes in at least 2 locations” to avoid false positives
Set Up Notifications
Configure alerts to your preferred channels. Use Datadog’s template variables to include failure details in your messages.Option B: Enhanced Monitoring with Component Details
Option B: Enhanced Monitoring with Component Details
Goal: Include which specific components are affected in your alerts for better incident response.
Step 1: Status Check
- Method:
GET
- URL:
https://status.elementum.io/api/v2/status.json
- Assertion:
$.status.indicator is none
(same as Option A)
Step 2: Component Analysis
- Method:
GET
- URL:
https://status.elementum.io/api/v2/summary.json
- Extract Variable:
- Type: JSONPath
- Path:
$.components[?(@.status!='operational')].name
- Variable Name:
AFFECTED_COMPONENTS
The
summary.json
endpoint provides comprehensive context including overall status, component statuses, and current incidents—perfect for detailed alert messages.Use in Notifications
Reference theAFFECTED_COMPONENTS
variable in your notification templates to automatically include which services are impacted.Option C: Severity-Based Alerting
Option C: Severity-Based Alerting
Goal: Different alert priorities for different severity levels (degradation vs. outages).
Approach 1: Single Test with Routing
- Use the simple Option A setup
- Route all alerts to a primary responder
- Failure details will show the actual indicator value (
minor
/major
/critical
) for manual triage
Approach 2: Multiple Tests for Precise Paging
Degradation/Partial Alert:- URL:
https://status.elementum.io/api/v2/status.json
- Assertion 1:
$.status.indicator is none
- Assertion 2:
$.status.indicator is not critical
- Result: Alerts on
minor
ormajor
but notcritical
- URL:
https://status.elementum.io/api/v2/status.json
- Assertion:
$.status.indicator is critical
- Result: Only alerts on critical outages for high-priority paging
Alternative: Agent-Based Checks
Alternative: Agent-Based Checks
If you prefer using Datadog Agent checks over Synthetics, you can use the HTTP Check integration:This approach flips to DOWN when it finds
"indicator":"(minor|major|critical)"
in the response.Benefits of Datadog Integration
- Rich Context: Include affected components and severity in alerts
- Integration Ready: Works with your existing Datadog alerting workflows
- Customizable: Adapt alert severity and routing to your operational needs