- Category: server monitoring
- Auth: DCR_OAUTH
- Composio-managed OAuth available? No
- Tools: 116
- Triggers: 0
- Slug:
BETTER_STACK_MCP - Version: 20261018_00
Tools
Acknowledge incident
Acknowledge incident
Add chart to dashboard
Add chart to dashboard
BETTER_STACK_MCP_ADD_CHART_TO_DASHBOARDAdd 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.REQUIRED: the query’s FROM must reference a source, either {{source}} or a source-type variable defined via set_dashboard_variable (e.g. {{redis_source}}). A query with no source is rejected with guidance to define it first.Dashboard chart queries run against the metrics collection: use sum(logs_count) (or the matching sum(<row_type>_count) for the source), avgMerge(value_avg), label('tag'). Do NOT use JSONExtract(raw, …) — that is for live-tail charts and query only; dashboards have no raw column. Call metrics_query_help with the source ID and context: 'chart_query' for available metrics/labels and chart-query-style examples.Workflow:- Call
chart_building_helpfor chart types, units, and settings. - Call
metrics_query_helpwithcontext: 'chart_query'to see the source’s metrics schema and chart-query examples. - Verify the query with
render_chart(runs it and surfaces errors automatically) or withquery.
{{source}}, {{start_time}}, {{end_time}}, {{time}} variables for integration with dashboard filters. Queries can also reference custom dashboard variables — {{var}} (required) or [[ AND col = {{var}} ]] (optional clause, dropped while the variable is empty); define them with set_dashboard_variable.Input Parameters
chart_building_help for the per-type reference, possible values, and gotchas.Add dashboard section
Add dashboard section
BETTER_STACK_MCP_ADD_DASHBOARD_SECTIONAdd 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 roomInput Parameters
Application
Application
Applications
Applications
Available incident escalation policies
Available incident escalation policies
Change team member role
Change team member role
BETTER_STACK_MCP_CHANGE_TEAM_MEMBER_ROLEChange a team member’s role. Identify the member by email or user_id (from team_members) and pass the target role_id (from team_roles). The admin role cannot be assigned, and an existing admin’s role cannot be changed, via the API. Pending invitations can’t have their role changed — cancel and re-invite instead. If the token can reach more than one team, pass team_id (or team_name).Input Parameters
Chart
Chart
Chart alert
Chart alert
Chart alert help
Chart alert help
BETTER_STACK_MCP_CHART_ALERT_HELPGet instructions for creating and configuring chart alerts, including alert types, operators, configuration fields, supported chart types, and common mistakes. Call this before creating or editing chart alertsChart alerts
Chart alerts
Chart building help
Chart building help
BETTER_STACK_MCP_CHART_BUILDING_HELPGet 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 chartsClusters
Clusters
Create application
Create application
BETTER_STACK_MCP_CREATE_APPLICATIONCreate 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 configurationInput Parameters
Create chart alert
Create chart alert
BETTER_STACK_MCP_CREATE_CHART_ALERTCreate a new chart alert on an existing chart. The chart must support alerts (line_chart, bar_chart, number_chart, or tail_chart with time variables). Call chart_alert_help for configuration reference. Use chart or dashboard first to find the chart IDInput Parameters
Create cloud connection
Create cloud connection
BETTER_STACK_MCP_CREATE_CLOUD_CONNECTIONCreate 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 defaultInput Parameters
Create dashboard
Create dashboard
BETTER_STACK_MCP_CREATE_DASHBOARDCreate a new dashboard. Optionally use a template to start with pre-configured charts. Call chart_building_help 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 chartsInput Parameters
Create error issue
Create error issue
BETTER_STACK_MCP_CREATE_ERROR_ISSUECreate an issue for an error in Linear, or a work item in Jira, through the team’s integration and link the two. The issue gets Better Stack’s standard body (error type, message, call site, stack trace, occurrence counts and a link back) and the integration’s configured defaults for team or space, work type, assignee, labels and priority. Better Stack then posts every change to the error state as a comment on the issue. An error that already has an issue through the integration is reported, not duplicated; use link_error_issue to attach an issue that already exists.Input Parameters
Create heartbeat
Create heartbeat
BETTER_STACK_MCP_CREATE_HEARTBEATCreate a new heartbeat that expects a periodic request from a cron job, worker, or other background task, and alerts when that request stops arriving.Provide a name for the heartbeat. The heartbeat reports down once no request is received within period seconds plus the grace window. Use the returned heartbeat URL as the endpoint your job pings on every successful run.Input Parameters
Create incident
Create incident
Create incident comment
Create incident comment
Create metric expression
Create metric expression
BETTER_STACK_MCP_CREATE_METRIC_EXPRESSIONCreate a new metric expression (extract-metrics-from-logs rule) on a source.sql_expression runs against each log row; log fields live inside the raw JSON column — use JSONExtract(raw, 'path', 'Nullable(Type)'). The Nullable(...) wrapper is required. Nested paths use positional args: JSONExtract(raw, 'request', 'headers', 'user-agent', 'Nullable(String)'). Call source_fields to see what fields exist.Pass aggregations (e.g. ["avg", "count"]) for an aggregated metric, or omit / pass [] for a label (group-by column).Prefer build_type: new_data (default). historical_logs re-runs the rule over every stored log — expensive; only when the user explicitly asks.Input Parameters
Create monitor
Create monitor
BETTER_STACK_MCP_CREATE_MONITORCreate a new monitor that tracks the availability of a website, host, or service.Provide the url to monitor. For ping, TCP, UDP, SMTP, POP, IMAP, and DNS monitors this is the host (e.g. example.com) rather than a full URL. The monitor starts checking immediately unless paused is set to true.Input Parameters
Create release
Create release
Create source
Create source
BETTER_STACK_MCP_CREATE_SOURCECreate 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 configurationInput Parameters
Create status page report
Create status page report
BETTER_STACK_MCP_CREATE_STATUS_PAGE_REPORTCreate a new status page reportInput Parameters
Create status page report update
Create status page report update
Create status page resource
Create status page resource
BETTER_STACK_MCP_CREATE_STATUS_PAGE_RESOURCEAdd a resource (monitor, heartbeat, or group) to a status page.Provide the resource_type and resource_id of the thing to display, plus a public_name shown to visitors (usually the resource’s own name). Use status_page_sections to find the section to place it in; when omitted the resource is added to the status page’s first section.Input Parameters
Create status page section
Create status page section
Dashboard
Dashboard
Dashboard query help
Dashboard query help
BETTER_STACK_MCP_DASHBOARD_QUERY_HELPGet instructions for writing a ClickHouse query to use inside a Better Stack Dashboard chart (or chart alert).The query uses template variables ({{source}}, {{time}}, {{start_time}}, {{end_time}}) and runs against the source’s metrics collection — it is meant to be saved as a dashboard chart via add_chart_to_dashboard / edit_chart, NOT run directly.To instead write an ad-hoc query you will run directly via query or render_chart, use metrics_query_help.Input Parameters
Dashboards
Dashboards
Dashboard templates
Dashboard templates
Data regions
Data regions
BETTER_STACK_MCP_DATA_REGIONSList 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 clustersDelete chart alert
Delete chart alert
Delete metric expression
Delete metric expression
BETTER_STACK_MCP_DELETE_METRIC_EXPRESSIONDelete a metric expression from a source. This action cannot be undone. Call metric_expressions first to get the ID.build_type: new_data (default) stops the rule from applying to future logs but leaves already-extracted data. build_type: historical_logs also rebuilds the source’s metrics without this rule — expensive.Input Parameters
Documentation
Documentation
Edit application
Edit application
BETTER_STACK_MCP_EDIT_APPLICATIONEdit an existing application in Better Stack - rename it, pause or resume ingesting, or set its VRL transformations, including the exception grouping program. Only provide the fields you want to change. Use applications or application first to find the application ID.Input Parameters
._pattern grouping key. Set to an empty string to remove a custom program, omit to leave unchanged.Edit chart
Edit chart
BETTER_STACK_MCP_EDIT_CHARTEdit an existing chart name, query, type, or settings. Only provide the fields you want to change.If changing the query: the new query’s FROM must reference a source, either {{source}} or a source-type variable defined via set_dashboard_variable (queries with no source are rejected).Dashboard chart queries run against the metrics collection: use sum(logs_count) (or the matching sum(<row_type>_count) for the source), avgMerge(value_avg), label('tag'). JSONExtract(raw, …) only works in live-tail charts — dashboards have no raw column.Verify the new query with render_chart (runs it and surfaces errors automatically) or with query before saving.Queries can also reference custom dashboard variables — {{var}} (required) or [[ AND col = {{var}} ]] (optional clause, dropped while the variable is empty); define them with set_dashboard_variable.Call chart_building_help for chart/settings reference and metrics_query_help with context: 'chart_query' for the source’s metrics schema and chart-query-style examples. Use dashboard first to find the chart ID.Input Parameters
chart_building_help for the per-type reference, possible values, and gotchas.Edit chart alert
Edit chart alert
BETTER_STACK_MCP_EDIT_CHART_ALERTEdit an existing chart alert configuration. Only provide the fields you want to change. Call chart_alert_help for configuration reference. Use chart_alerts or chart_alert first to find the alert IDInput Parameters
Edit dashboard
Edit dashboard
BETTER_STACK_MCP_EDIT_DASHBOARDEdit an existing dashboard’s name or source eligibility. Only provide the fields you want to change. Use dashboard first to find the dashboard ID.Input Parameters
SELECT count() > 0 FROM {{source}}); the dashboard is offered for a source only when the query returns truthy. The selected source and time range are injected automatically (as the {{source}}, {{start_time}}, and {{end_time}} variables), so the query should not reference any other dashboard variables. Call metrics_query_help with context: 'chart_query' for the source’s metrics schema and query syntax. Set to an empty string to clear eligibility and make the dashboard visible for all sources; omit to leave it unchanged.Edit dashboard section
Edit dashboard section
Error
Error
Errors
Errors
BETTER_STACK_MCP_ERRORSList error patterns for an application with occurrence counts, affected users, current state, and links. Defaults to unresolved errors and supports filtering by state. For specialized error analytics or custom SQL, use errors_query_help instead.Input Parameters
Errors query help
Errors query help
Escalate incident
Escalate incident
BETTER_STACK_MCP_ESCALATE_INCIDENTEscalate an ongoing incident to a user, team, schedule, or policyInput Parameters
Escalation policies
Escalation policies
Escalation policy
Escalation policy
Exploration
Exploration
Explorations
Explorations
Explore logs query help
Explore logs query help
BETTER_STACK_MCP_EXPLORE_LOGS_QUERY_HELPGet instructions for writing a ClickHouse query to use inside the Better Stack Explore logs page (and live-tail charts) for log and span data.The query uses template variables ({{source}}, {{time}}, {{start_time}}, {{end_time}}) and reads fields from the raw JSON column — it is meant to be used in the Explore UI, NOT run directly.To instead write an ad-hoc logs/spans query you will run directly via query, use query_help.Input Parameters
Export dashboard
Export dashboard
Heartbeat
Heartbeat
Heartbeat availability
Heartbeat availability
Heartbeats
Heartbeats
Import dashboard
Import dashboard
Incident
Incident
Incident comments
Incident comments
Incidents
Incidents
BETTER_STACK_MCP_INCIDENTSList incidents with filtering and pagination optionsInput Parameters
status for mutually-exclusive lifecycle filtering.status for mutually-exclusive lifecycle filtering.incident_group_id off an existing incident.Incident timeline
Incident timeline
Invite team member
Invite team member
BETTER_STACK_MCP_INVITE_TEAM_MEMBERInvite someone to a Better Stack team by e-mail address. Optionally set their role by system-role name (role: responder, member, team_lead, billing_admin) or by role_id (use team_roles to look up ids). Defaults to responder. The admin role cannot be assigned via the API. Someone who already belongs to the organization is added to the team directly, with no invitation to accept; the Admin role applies to every team, so an existing Admin keeps it. If the token can reach more than one team, pass team_id (or team_name).Input Parameters
Link error issue
Link error issue
BETTER_STACK_MCP_LINK_ERROR_ISSUELink an error to an issue or work item that already exists in Linear or Jira. Better Stack then posts every change to the error state as a comment on the issue. For Linear, resolving the issue also resolves the error when auto-resolve is turned on for that integration; Jira has no status sync back. Create the issue in Linear or Jira first, then pass its identifier, key, or URL here.Input Parameters
Metric
Metric
BETTER_STACK_MCP_METRICGet 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 metricInput Parameters
Metric expressions
Metric expressions
BETTER_STACK_MCP_METRIC_EXPRESSIONSList the metric expressions (extract-metrics-from-logs rules) on a source. Returns the rule ID, name, kind (metric vs label), ClickHouse type, SQL expression, and aggregations. IDs use a short prefixed form that feeds straight into update_metric_expression / delete_metric_expressionInput Parameters
Metrics query help
Metrics query help
BETTER_STACK_MCP_METRICS_QUERY_HELPGet instructions for building SQL ClickHouse queries for metrics (available metrics, aggregations, examples) to run directly via the query tools (query / render_chart), using concrete remote(...) / s3Cluster(...) collection names and explicit time filters.To instead write a query for use inside a Dashboard chart, use dashboard_query_help.Pass context: 'chart_query' when the query will be saved as a dashboard chart or chart alert — the prompt will emphasize {{source}} / {{time}} / {{start_time}} / {{end_time}} template variables and chart column aliases. (context: 'direct_query' is the default, for ad-hoc queries.)Input Parameters
Metrics schema
Metrics schema
BETTER_STACK_MCP_METRICS_SCHEMAGet metrics and cardinality for a source. Returns a paginated table of available metrics (user-defined and ingested) ordered by active series (highest cardinality first), with their names, types, storage layout, data points count, and active series count. Use name_filter to search by name: rabbitmq*, *queue*, *_total, or an exact name. When more than 250 metrics match and grouping them by name prefix would shrink the list at least 3x, a prefix summary is returned instead of the list; drill in with the name_filter it suggests. page applies to whichever table is shownInput Parameters
Monitor
Monitor
Monitor availability
Monitor availability
Monitor response times
Monitor response times
Monitors
Monitors
Move charts
Move charts
On call
On call
On call event
On call event
On call events
On call events
On call rotation
On call rotation
On calls
On calls
Query
Query
BETTER_STACK_MCP_QUERYExecute a ClickHouse SQL query to retrieve logs, traces/spans, errors, and metrics from telemetry data.- IMPORANT: Use
query_helpto get instructions on how to create the correct query for logs and spans - IMPORANT: Use
errors_query_helpto get instructions on how to create the correct query for errors - IMPORANT: Use
metrics_query_helpto get instructions on how to create the correct query for metrics
Input Parameters
Query help
Query help
BETTER_STACK_MCP_QUERY_HELPGet instructions for building SQL ClickHouse queries for logs and spans (fields, aggregations, examples) to run directly via the query tools (query / render_chart) against the ClickHouse proxy. To instead write a query for use inside the Explore logs UI, use explore_logs_query_help.Input Parameters
Releases
Releases
Remove chart
Remove chart
Remove dashboard
Remove dashboard
Remove dashboard section
Remove dashboard section
Remove dashboard variable
Remove dashboard variable
BETTER_STACK_MCP_REMOVE_DASHBOARD_VARIABLERemove a dashboard template variable by name. Cannot remove the automatic variables source, start_time, end_time, or time. A chart still referencing a removed variable as a required {{name}} errors until it is redefined (the next chart save auto-creates it again, empty). Use dashboard first to see the defined variables.Input Parameters
Remove exploration variable
Remove exploration variable
BETTER_STACK_MCP_REMOVE_EXPLORATION_VARIABLERemove a variable from an exploration (saved Explore query) by name. Cannot remove the automatic variables source, start_time, end_time, or time. A query still referencing a removed variable as a required {{name}} errors until it is redefined. Use exploration first to see the defined variables.Input Parameters
Remove release
Remove release
Remove status page resource
Remove status page resource
Remove status page section
Remove status page section
Remove team member
Remove team member
BETTER_STACK_MCP_REMOVE_TEAM_MEMBERRemove a member from a Better Stack team, or cancel a pending invitation. Identify them by email or user_id (from team_members). Admins cannot be removed via the API, and the organization’s last member cannot be removed. If the token can reach more than one team, pass team_id (or team_name). This permanently removes the person’s access to the team.Input Parameters
Render chart
Render chart
BETTER_STACK_MCP_RENDER_CHARTExecute a ClickHouse SQL query and visualize the result as a chart.Use chart_type to choose the visualization:line(default) — trends over time. Alias columns astime,value, and optionalseries.bar— magnitude over time or across buckets. Uses the same columns asline; setstacked: trueto stack the series.pie— share of a total across categories. Alias a categorical columnAS series(the slice label) and a numeric columnAS value(the slice size), e.g.SELECT service AS series, count() AS value FROM ... GROUP BY service.
... AS time— the time bucket (e.g.,toStartOfHour(dt) AS time)... AS value— the numeric metric (e.g.,count() AS value)... AS series— optional: a grouping column for multiple series (e.g.,service AS series)
- Up to 1 hour →
toStartOfMinute(dt) AS time→ ~60 points - 1–24 hours →
toStartOfInterval(dt, INTERVAL 5 MINUTE) AS time→ up to 288 points - 1–7 days →
toStartOfHour(dt) AS time→ up to 168 points - 7–30 days →
toStartOfInterval(dt, INTERVAL 4 HOUR) AS time→ up to 180 points - 30–90 days →
toStartOfInterval(dt, INTERVAL 12 HOUR) AS time→ up to 180 points - 90+ days →
toStartOfDay(dt) AS time
query_help— logs and spanserrors_query_help— errorsmetrics_query_help— metrics
Input Parameters
Reopen incident
Reopen incident
Replays query help
Replays query help
Set dashboard variable
Set dashboard variable
BETTER_STACK_MCP_SET_DASHBOARD_VARIABLECreate or update a dashboard template variable — a user-facing filter in the dashboard toolbar, referenced in chart SQL as {{name}} (required — the chart errors until it resolves to a value) or [[ AND col = {{name}} ]] (optional — the whole [[ ... ]] clause is dropped while the variable is empty).Saving a chart auto-creates a plain text variable (or a source variable when the name contains ‘source’) for any undefined required {{name}}, but it starts empty — use this tool to give it a typed definition or a default value so the chart resolves without manual input.Fields per type:select_value(shown as “Static list”) → the options indefault_values(first = default selection)select_with_sql(shown as “Dynamic list”) → an option-yielding expression (NOT a full query) insql_definition, e.g.label('_host'); see thesql_definitionparameter for how it is interpolated- Both list types accept
allow_multiple_values: trueto let users pick several options at once (interpolates as a regex used withmatch()).multi_select_with_sqlis the legacy always-multiple Dynamic list; preferselect_with_sqlwithallow_multiple_values: true. select_predefined_sql(shown as “Query per value”) → named SQL filters infilters(each a full query), default picked viaselected_labelstring/number/boolean→[default]indefault_valuessql_expression→[raw SQL]indefault_values, spliced into chart SQL unescapedsource→ the source IDs insource_ids. Name itsourceto set the dashboard’s own source (which sources every chart queries by default), or use a custom name for an extra source variable that a chart references in its FROM (e.g.FROM {{name}}) to query a different set of sources than the dashboard default.date/datetime→ an ISO date indefault_values, e.g.['2026-07-23']or['2026-07-23T14:30:00Z']
start_time, end_time, and time are reserved (they come from the time picker). source is the exception: set it as a source-type variable to change the dashboard’s source. Use dashboard to list a dashboard’s variables and dashboard_query_help for how each type is referenced in chart SQL.Input Parameters
dt BETWEEN {{start_time}} AND {{end_time}}, never {{time}} (that macro only buckets inside charts). Example: SELECT label(‘cmd’) FROM {{source}} WHERE dt BETWEEN {{start_time}} AND {{end_time}} GROUP BY 1 ORDER BY count() DESC LIMIT 5.SELECT DISTINCT <sql_definition> AS option FROM {{source}} WHERE dt BETWEEN {{start_time}} AND {{end_time}} LIMIT 50 to populate the dropdown. Example: label(‘_host’).match(), or as a parenthesised list when written straight after IN / NOT IN. Never IN ({{var}}), which keeps the regex and matches nothing. Ignored for other types.Set exploration variable
Set exploration variable
BETTER_STACK_MCP_SET_EXPLORATION_VARIABLECreate or update a variable on an exploration (saved Explore query), referenced in its query as {{name}}.The most common use is setting the exploration’s source: name it source, type source, and pass the source IDs in source_ids — the query then runs against those sources.Fields per type:source→ the source IDs insource_ids. Name itsourceto set the exploration’s own source, or use a custom name for an extra source variable the query references in its FROM (e.g.FROM {{name}}).select_value→ the options indefault_values(first = default selection)select_with_sql/multi_select_with_sql→ an option-yielding expression (NOT a full query) insql_definition, e.g.label('_host')select_predefined_sql→ named SQL filters infilters(each a full query), default picked viaselected_labelstring/number/boolean→[default]indefault_valuessql_expression→[raw SQL]indefault_values, spliced into the query unescapeddate/datetime→ an ISO date indefault_values, e.g.['2026-07-23']or['2026-07-23T14:30:00Z']
start_time, end_time, and time are reserved (they come from the time picker). source is the exception: set it as a source-type variable to change the exploration’s source. Use exploration to list an exploration’s variables.Input Parameters
dt BETWEEN {{start_time}} AND {{end_time}}.Severities
Severities
Severity
Severity
Source
Source
Source fields
Source fields
Sources
Sources
Status page
Status page
Status page reports
Status page reports
Status page report update
Status page report update
Status page report updates
Status page report updates
Status page resources
Status page resources
Status pages
Status pages
Status page sections
Status page sections
Team members
Team members
BETTER_STACK_MCP_TEAM_MEMBERSList the members of a Better Stack team, including pending invitations. Returns each member’s email, name, role and the mobile app platforms they have signed in on. Supports the same email filter and pagination as the REST team-members API. If the token can reach more than one team, pass team_id (or team_name) to pick one; call it without a team first to see the list of accessible teams. Useful for auditing who has access — e.g. offboarding.Input Parameters
Team roles
Team roles
BETTER_STACK_MCP_TEAM_ROLESList the roles defined in a Better Stack organization, including their role_id and system-role identifier (admin, billing_admin, team_lead, responder, member, or “custom”). Use this to discover valid role_id values for interpreting team member roles. If the token can reach more than one team/organization, pass team_id (or team_name) to choose one.Input Parameters
Teams
Teams
Toggle chart alert pause
Toggle chart alert pause
Unlink error issue
Unlink error issue
BETTER_STACK_MCP_UNLINK_ERROR_ISSUERemove the link between an error and an issue in Linear, Jira, or GitLab. Better Stack stops syncing the two; the issue itself is left untouched.Input Parameters
Update error state
Update error state
BETTER_STACK_MCP_UPDATE_ERROR_STATEUpdate the state of a specific error (mark as resolved, ignored, or unresolved)Input Parameters
Update metric expression
Update metric expression
BETTER_STACK_MCP_UPDATE_METRIC_EXPRESSIONUpdate an existing metric expression. Call metric_expressions first to get the ID.At least one of name, sql_expression, type, aggregations must be provided — build_type alone is not a change and will be rejected. See create_metric_expression for sql_expression / type / aggregations guidance.Prefer build_type: new_data (default). historical_logs re-runs the rule over every stored log — expensive; only when the user explicitly asks.Input Parameters
Update status page
Update status page
Update status page resource
Update status page resource
BETTER_STACK_MCP_UPDATE_STATUS_PAGE_RESOURCEUpdate a resource on a status page.Change its public name, description, widget type (e.g. show or hide the uptime history), or move it by setting position (zero-based) and/or status_page_section_id. Use status_page_resources to find resource IDs.