Better Stack

Better Stack

The AI SRE observability stack

Pricing: Freemium - $29/month Company: Better Stack Founded: 2021
Visit Website

TL;DR

Better Stack is an AI-native observability platform combining logs, metrics, traces, uptime monitoring, error tracking, and incident management with MCP server integration for AI agents. It's for engineering teams and SREs seeking affordable alternatives to Datadog. Key differentiator: 30x cheaper, predictable pricing, and seamless MCP for LLM workflows.

What Users Actually Pay

No user-reported pricing yet.

Our Take

Better Stack positions itself as a modern, cost-effective alternative in the crowded observability market, directly challenging incumbents like Datadog with claims of 30x lower costs and predictable pricing. Its primary value proposition is a unified stack for logs, metrics, traces, uptime, incidents, and AI-powered SRE tools, now enhanced with MCP server for AI agent integration, appealing to teams adopting LLM-driven ops. High G2 (4.8/5 from 308 reviews) and Capterra ratings underscore its market traction among startups and mid-sized teams. Strengths include exceptional ease of setup, intuitive UI, generous free tier, reliable alerting (screenshots, traceroute), and AI features like root cause analysis that speed MTTR. Reviewers praise support and value, especially vs. pricier rivals. The MCP server stands out for AI/ML workflows, aligning with emerging agentic ops trends. Limitations surface at scale: some users note missing enterprise features, full-stack depth vs. Datadog/New Relic, and potential alert fatigue without heavy customization. It's not yet as mature for massive, complex environments. Best suited for startups, indie hackers, and growing teams (SMBs) prioritizing simplicity, affordability, and AI integration over exhaustive enterprise controls.

Pros

  • + Intuitive, modern UI with quick setup (minutes), praised across G2/Capterra.
  • + Generous free tier and predictable, low-cost pricing vs. competitors like Datadog.
  • + Reliable uptime monitoring with screenshots, traceroute, no false positives.
  • + Integrated observability (logs/metrics/traces/incidents) + AI SRE tools reduce tool sprawl.
  • + Excellent support and migration assistance highlighted in reviews.

Cons

  • - May lack depth for very large-scale, complex infrastructures vs. Datadog/New Relic.
  • - Feature completeness gaps noted for advanced/enterprise use cases in comparisons.
  • - Learning curve for full feature mastery despite easy start.
  • - Limited presence on some review sites like TrustRadius (no reviews found).
  • - Potential scaling limits for high-volume logs/traces per some user feedback.

Sentiment Analysis

+0.88Very PositiveUpdated Mar 25, 2026

Better Stack receives highly positive feedback on professional review sites G2 and Capterra, with ratings around 4.8/5, emphasizing ease of use, intuitive setup, strong customer support, and reliable performance. Reddit discussions are generally positive, highlighting affordability, simplicity, and long-term usage. X mentions are mostly neutral to promotional with minor issues. Key themes: exceptional user experience, quick implementation, good value, powerful free tier.

Sentiment Over Time

By Source

G2+0.96

310 mentions

Sample quotes (3)
  • "Users consistently praise the ease of use and intuitive interface of Better Stack, highlighting how quickly they can set up monitoring and receive alerts."
  • "I love using Better Stack, it's easy to implement, has very good customer support, I use it often, there are quite a few features, and their API is super simple."
  • "Better Stack has been rated 4.8 stars by 310 verified reviews on G2."
Capterra+0.96

37 mentions

Sample quotes (3)
  • "“Better Uptime is a system that complies with what it offers, even the free version, it is very powerful for basic systems"."
  • "Better Stack 4.8 (37) ... Ease of use 4.9 Customer Service 4.8."
  • "Value For Money 4.7(37)."
Reddit+0.70

20 mentions

Sample quotes (3)
  • "I use Better Stack ( Better Uptime ) for a couple of years."
  • "We use Betterstack logs (formerly Logtail). Amazing product, super simple to use with high performance!"
  • "BetterStack is 30x cheaper than DataDog."
X (Twitter)+0.50

10 mentions

Sample quotes (3)
  • "Simple to query, powerful to analyze. Better Stack leads G2 in performance and ease of use."
  • "Join 300,000+ developers relying on Better Stack."
  • "Better Stack reports it as up, but ... (one issue noted)."

Agent Readiness

60/100

Better Stack offers a solid foundation for AI agent integration through its public REST APIs following JSON:API spec for Uptime and Telemetry, with Bearer auth and free tier access. Strong Zapier support and webhooks enable no-code automations, complemented by native integrations like OpenTelemetry and Terraform. Developer docs are good with examples but lack interactive sandbox or explicit rate limits; versioning and status page enhance reliability, making it agent-ready for monitoring and observability tasks.

API Surface85
Public APIRESTFree Tierunknown
Protocol Support40
MCP (75 tools)
SDK Availability35
npm: axios-better-stacktrace
Integration Ecosystem50
ZapierWebhooksSlackTerraformPagerDutyLinearOpenTelemetryPrometheus
Developer Experience80
Docs: goodVersioningChangelogStatus Page

Last checked Mar 28, 2026

MCP Integrations

1 server75 tools93 total uses
Better Stack
Better Stackbetterstack
smitheryVerifiedRemoteHigh match

Monitor system availability, manage incident response workflows, and query telemetry data via SQL. Visualize logs, traces, and metrics with custom dashboards and interactive charts. Automate on-call scheduling and status page updates to keep teams informed during outages.

93 uses
75 tools
  • telemetry_queryExecute a ClickHouse SQL query to retrieve logs, traces/spans, errors, and metrics from telemetry data. - **IMPORANT**: Use `telemetry_get_query_instructions_tool` to get instructions on how to create the correct query for logs and spans - **IMPORANT**: Use `telemetry_get_errors_query_instructions_tool` to get instructions on how to create the correct query for errors - **IMPORANT**: Use `telemetry_get_metrics_query_instructions_tool` to get instructions on how to create the correct query for metrics
  • telemetry_chartExecute a ClickHouse SQL query and display the result as a line chart. Query instructions (column aliases, time granularity, data access patterns) are in: - `telemetry_get_query_instructions_tool` — logs and spans - `telemetry_get_errors_query_instructions_tool` — errors - `telemetry_get_metrics_query_instructions_tool` — metrics
  • uptime_acknowledge_incident_toolAcknowledge an ongoing incident
  • uptime_create_incident_comment_toolCreate a comment on an incident
  • uptime_create_incident_toolCreate a new incident providing a summary of the issue, requester email, and other optional details
  • uptime_escalate_incident_toolEscalate an ongoing incident to a user, team, schedule, or policy
  • uptime_get_incident_comments_toolGet comments for an incident
  • uptime_get_incident_toolGet detailed information about a specific incident
  • uptime_get_incident_escalation_options_toolGet available escalation options for an incident
  • uptime_get_incident_timeline_toolGet the timeline of events for an incident
  • uptime_list_incidents_toolList incidents with filtering and pagination options
  • uptime_resolve_incident_toolResolve an ongoing incident
  • uptime_get_escalation_policy_toolGet detailed information about a specific escalation policy
  • uptime_get_severity_toolGet detailed information about a specific severity (urgency level)
  • uptime_list_escalation_policies_toolList all escalation policies with their steps and configuration
  • uptime_list_severities_toolList all severities (urgency levels) with their notification settings
  • uptime_get_monitor_availability_toolGet availability (SLA) summary for a specific monitor
  • uptime_get_monitor_toolGet details of a specific monitor
  • uptime_get_monitor_response_times_toolGet response time metrics for a specific monitor
  • uptime_list_monitors_toolList monitors with optional filtering and pagination
  • uptime_get_heartbeat_availability_toolGet availability summary for a specific heartbeat
  • uptime_get_heartbeat_toolGet details of a specific heartbeat
  • uptime_list_heartbeats_toolList all heartbeats with filtering and pagination options
  • uptime_get_on_call_toolGet detailed information about a specific on-call calendar or the default calendar
  • uptime_get_on_call_event_toolGet detailed information about a specific on-call event
  • uptime_get_on_call_rotation_toolGet on-call rotation configuration for a specific calendar
  • uptime_list_on_call_events_toolList all on-call schedule events for a specific calendar
  • uptime_list_on_calls_toolList all on-call calendars for the team
  • uptime_create_status_page_report_toolCreate a new status page report
  • uptime_create_status_page_report_update_toolCreate a new status update for an existing status page report
  • uptime_get_status_page_toolGet details of a specific status page
  • uptime_get_status_page_resources_toolGet resources (monitors/heartbeats) for a specific status page
  • uptime_get_status_page_report_update_toolGet details of a specific status page report update
  • uptime_list_status_page_reports_toolList status reports (incidents/maintenance) for a specific status page
  • uptime_list_status_pages_toolList all status pages with filtering and pagination options
  • uptime_list_status_page_report_updates_toolList status updates for a specific status report
  • telemetry_add_chart_to_dashboard_toolAdd a new chart to a dashboard. Use the `section` parameter to organize charts into named sections — sections are auto-created if they don't exist, and charts are auto-positioned within them. **IMPORTANT: Follow this workflow:** 1) Call get_chart_building_instructions first for chart type, unit, and settings reference. 2) If you haven't already verified the query by previewing with `telemetry_chart` (which runs the query and reports errors automatically), test it with `telemetry_query` first. The SQL query should use variables like {{source}}, {{start_time}}, {{end_time}}, and {{time}} for proper integration with dashboard filters
  • telemetry_add_dashboard_section_toolAdd a section divider to a dashboard. Sections span the full width and help organize charts into groups. Charts and sections at or below the insertion point are shifted down to make room
  • telemetry_build_explore_query_toolGenerates a ClickHouse SQL query from natural language for exploring logs and spans data in Better Stack. The query is specifically formatted for use in the Better Stack Explore page UI. **Note**: The generated query uses Better Stack's query syntax and will not work directly in raw ClickHouse.
  • telemetry_build_metric_query_toolGenerates a ClickHouse SQL query from natural language for creating metrics visualizations in Better Stack Dashboards. Returns a query optimized for charts and dashboards that can be directly used in the Dashboard builder UI. **Note**: The generated query uses Better Stack's query syntax and will not work directly in raw ClickHouse.
  • telemetry_create_application_toolCreate a new application in Better Stack. Returns the created application details including ID, ingestion token, ingesting host URL, retention settings, and platform-specific integration documentation links with next steps for configuration
  • telemetry_create_cloud_connection_toolCreate a secure cloud connection for direct ClickHouse query access to logs, spans, and metrics data. Returns connection credentials (host, port, username, password), sample queries for each data type, and cURL command examples. Connections expire after 1 hour by default
  • telemetry_create_dashboard_toolCreate a new dashboard. Optionally use a template to start with pre-configured charts. Call get_chart_building_instructions for guidance on dashboard structure and layout. Optionally specify a source_id to preconfigure the dashboard with that source. Returns the new dashboard ID which can be used with add_chart_to_dashboard to add charts
  • telemetry_create_source_toolCreate a new log source in Better Stack. Returns the created source details including ID, ingestion token, ingesting host URL, retention settings, and platform-specific integration documentation links with next steps for configuration
  • telemetry_edit_chart_toolEdit an existing chart name, query, type, or settings. Only provide the fields you want to change. **IMPORTANT: If changing the query:** If you haven't already verified the new query by previewing with `telemetry_chart` (which runs the query and reports errors automatically), test it with `telemetry_query` first before updating the chart. Call get_chart_building_instructions for chart type and settings reference. Use get_dashboard_details first to find the chart ID
  • telemetry_export_dashboard_toolExport a dashboard configuration as JSON. Returns the complete dashboard data structure including charts, sections, presets, and settings
  • telemetry_get_application_details_toolGet comprehensive details of a specific application including its configuration, retention settings, ingestion details, custom bucket settings (if configured)
  • telemetry_get_chart_building_instructions_toolGet comprehensive instructions for building charts and dashboards, including chart types, units, axis settings, column mapping, legend placement, layout tips, and common mistakes. Call this before creating or editing charts
  • telemetry_get_chart_details_toolGet detailed information about a specific chart including its SQL queries, configuration, and settings. Use get_dashboard_details first to find the chart ID
  • telemetry_get_dashboard_details_toolGet detailed information about a specific dashboard including its charts, sections, layout, and configuration. Use this to understand a dashboard structure before modifying it
  • telemetry_get_error_details_toolGet comprehensive details of a specific error including its type, message, call site information, first occurrence, and current state (unhandled, unresolved, ignored, resolved, or reoccurred)
  • telemetry_get_errors_query_instructions_toolGet comprehensive instructions for building SQL ClickHouse queries for error tracking, including both error patterns (metrics) and individual exceptions. Explains when to use each source and provides examples for common use cases
  • telemetry_get_metric_details_toolGet comprehensive details about a specific metric. Returns metric overview (data points, active series, available aggregations), definition (SQL expression or JSON path), example queries for different aggregation functions, and Prometheus tags (for pure metrics). Essential for understanding how to query and use a metric
  • telemetry_get_metric_query_instructions_toolGet instructions for building SQL ClickHouse queries for metrics, including available metrics, aggregations, and examples
  • telemetry_get_metrics_and_cardinality_toolGet complete metrics and cardinality for a source. Returns a table of all available metrics (pure and computed) with their names, types, data points count, and active series count
  • telemetry_get_query_instructions_toolGet instruction for building SQL ClickHouse queries, including fields, aggregations, and examples, that can be used for running queries using direct connections to the ClickHouse proxy
  • telemetry_get_replays_query_instructions_toolGet comprehensive instructions for building SQL ClickHouse queries for session replays. Explains data structure, provides examples for listing replays, finding replays linked to errors, and filtering by user/environment
  • telemetry_get_source_details_toolGet comprehensive details of a specific source including its configuration, retention settings, ingestion details, custom bucket settings (if configured)
  • telemetry_get_source_fields_toolGet complete field catalog for a logs or spans source. Returns a table of all queryable fields with their paths and data types. Essential for understanding what fields can be queried for building custom queries
  • telemetry_import_dashboard_toolImport a dashboard from JSON configuration. Creates a new dashboard with the provided data structure
  • telemetry_list_applications_toolList all available applications in a paginated table format. Returns application ID, name, platform type, team, status (active/paused), data region, and creation date
  • telemetry_list_clusters_toolList all available storage clusters for a specific team. Returns a table with cluster IDs, names, and regions. Used primarily for creating cloud connections to query logs and metrics data directly via ClickHouse
  • telemetry_list_dashboard_templates_toolList all available dashboard templates in a paginated table format. Returns template ID, name, description, and other metadata
  • telemetry_list_dashboards_toolList all available dashboards in a paginated table format. Returns dashboard ID, name, creation date, and last updated date
  • telemetry_list_data_regions_toolList all available data regions and clusters for application and source creation. Returns a table with region IDs (to use when creating applications or sources), display names, types (Region or Cluster), and geographical locations. Includes usage instructions for both standard regions and custom clusters
  • telemetry_list_releases_toolList all releases for a specific application in a paginated table format. Returns release reference, environments, first seen, and last seen timestamps
  • telemetry_list_sources_toolList all available sources in a paginated table format. Returns source ID, name, platform type, team, status (active/paused), data region, and creation date
  • telemetry_list_teams_toolList all available teams in Better Stack Logs. Returns a table with team IDs and names, grouped by organization
  • telemetry_move_charts_toolMove one or more charts to new positions on a dashboard. Validates the final layout for overlaps, allowing swaps and complex rearrangements. All moves are applied atomically - if any move is invalid, none are applied. Grid is 12 columns wide
  • telemetry_remove_chart_toolRemove a chart from its dashboard permanently. This action cannot be undone and will also remove any alerts associated with the chart. Use get_dashboard_details first to find the chart ID
  • telemetry_remove_dashboard_section_toolRemove a section divider from a dashboard permanently. This action cannot be undone. Charts are not affected - only the section header is removed. Use get_dashboard_details first to find the section ID
  • telemetry_remove_dashboard_toolRemove a dashboard permanently. This action cannot be undone
  • telemetry_rename_dashboard_toolRename an existing dashboard
  • telemetry_update_error_state_toolUpdate the state of a specific error (mark as resolved, ignored, or unresolved)
  • better_stack_search_documentation_toolSearch for relevant documentation articles and return their contents

Last checked Mar 20, 2026

Reviews

0 reviews
Write a Review

No reviews yet. Be the first to review Better Stack!