observability Static interface comparison
Grafana MCP
2.2.0 2.3.0
8 schema changes require review.No new authority detected.
View the upgrade review as Markdown
A shareable summary of this comparison for an issue, pull request or ticket. Select the text and copy it.
INTERFACE DIFF
What changed, tool by tool
- 0Added tools
- 0Removed tools
- 14Modified tools
- 8Input-schema changes
- 0Output-schema changes
- 0Declared authority changes
14 tools with recorded changes
alerting_rules_writeModifiedWhat changed
- alerting_rules_write — Schema change: input property removed: label_selectors.
- alerting_rules_write — Schema change: input property removed: limit_alerts.
- alerting_rules_write — Schema change: input property removed: matchers.
- alerting_rules_write — Schema change: input property removed: rule_limit.
- alerting_rules_write — Schema change: input property removed: rule_type.
- alerting_rules_write — Schema change: input property removed: search_folder.
- alerting_rules_write — Schema change: input property removed: search_rule_name.
- alerting_rules_write — Schema change: input property removed: states.
- alerting_rules_write — Schema change: input property datasource_uid changed: description "Datasource UID for… → "Datasource UID for….
- alerting_rules_write — Schema change: input property folder_uid changed: description "The folder UID. Fo… → "The folder UID. Re….
- alerting_rules_write — Schema change: input property notification_settings changed: description "Notification setti… → "Notification setti….
- alerting_rules_write — Schema change: input property operation changed: description "The operation to p… → "The operation to p…, enum ["list","get","vers… → ["create","update",….
- alerting_rules_write — Schema change: input property rule_uid changed: description "The UID of the ale… → "The UID of the ale….
Why it could matter
- Calls or consumers built for the earlier schema may need to change.
What to verify
- Validate representative existing tool calls against the new argument schema.
- Declared effect
- write → write
Input schema
Property Previous (2.2.0) Current (2.3.0) Change datasource_uidstringoptional stringoptional - Description changed
folder_uidstringoptional stringoptional - Description changed
label_selectorsarrayoptional not present - Removed
label_selectors › [items]string not present - Removed
limit_alertsintegeroptional not present - Removed
matchersarrayoptional not present - Removed
matchers › [items]string not present - Removed
notification_settingsobjectoptional objectoptional - Description changed
operationstring, enum (6)required string, enum (3)required - Description changed
- Constraint: enum
enum: ["list","get","versions","create","update","delete"] → ["create","update","delete"]rule_limitinteger, default=200optional not present - Removed
rule_typestring, enum (2)optional not present - Removed
rule_uidstringoptional stringoptional - Description changed
search_folderstringoptional not present - Removed
search_rule_namestringoptional not present - Removed
statesarrayoptional not present - Removed
states › [items]string not present - Removed
21 unchanged entries
(schema root)annotationsconditiondatadata › [items]disable_provenanceevaluation_intervalexec_err_stateexpressionforis_pausedkeep_firing_forlabelsmanaged_bymissing_series_evals_to_resolvenamespaceno_data_stateorg_idrecordrule_grouptitle
No output schema is recorded for this tool in either release.
Link to this toolExact JSON from the published snapshots
Loads the exact recorded definitions of this tool from both releases. The full snapshots are linked under Evidence and provenance.
alerting_silences_writeModifiedWhat changed
- alerting_silences_write — Schema change: input property removed: rule_uid.
- alerting_silences_write — Schema change: input property matchers changed: description "Label matchers. Re… → "Label matchers. Re….
- alerting_silences_write — Schema change: input property operation changed: description "The operation to p… → "The operation to p…, enum ["list","get","crea… → ["create","update",….
- alerting_silences_write — Schema change: input property silence_id changed: description "The silence id (re… → "The silence id (re….
- alerting_silences_write — Schema change: input property starts_at changed: description "Silence start time… → "Silence start time….
Why it could matter
- Calls or consumers built for the earlier schema may need to change.
What to verify
- Validate representative existing tool calls against the new argument schema.
- Declared effect
- write → write
Input schema
Property Previous (2.2.0) Current (2.3.0) Change matchersarrayoptional arrayoptional - Description changed
operationstring, enum (5)required string, enum (3)required - Description changed
- Constraint: enum
enum: ["list","get","create","update","delete"] → ["create","update","delete"]rule_uidstringoptional not present - Removed
silence_idstringoptional stringoptional - Description changed
starts_atstringoptional stringoptional - Description changed
9 unchanged entries
(schema root)commentcreated_byends_atmatchers › [items]matchers › [items] › isEqualmatchers › [items] › isRegexmatchers › [items] › namematchers › [items] › value
No output schema is recorded for this tool in either release.
Link to this toolExact JSON from the published snapshots
Loads the exact recorded definitions of this tool from both releases. The full snapshots are linked under Evidence and provenance.
create_datasourceModifiedWhat changed
- create_datasource — Schema change: input property name changed: description "Datasource display… → "Datasource display….
- create_datasource — No longer required: name.
- create_datasource: description changed.
- create_datasource: declared metadata changed (declared open_world: false → true).
Why it could matter
- Calls or consumers built for the earlier schema may need to change.
- Existing calls stay valid in shape, but behavior when the argument is omitted may differ.
- Models choose and call tools partly from their descriptions.
- Annotations such as idempotent or open-world hints can inform how clients treat a tool.
What to verify
- Validate representative existing tool calls against the new argument schema.
- Confirm the server’s behavior when the argument is omitted.
- Spot-check that agents still select this tool as intended.
- Confirm any client logic that relies on these annotations.
- Declared effect
- write → write
- Description
- PreviousCreate a datasource in two steps. Called with only the type, it returns the plugin's field schema and creates nothing. Called with the type, the display name in the top-level name argument, schemaReviewed=true, and field values in the fields map, it creates the datasource. The plugin for the type must already be installed. Secrets (passwords, tokens) are not accepted. Returns UID, health check, and a config page link.
- CurrentCreate a datasource in two steps. Called with only the type, it returns the fields to fill in and creates nothing. Called again with the type, a display name in name, and the field values, it creates the datasource; for a type with a field schema, put the values in the fields map and set schemaReviewed=true. The plugin for the type must already be installed. Secrets (passwords, tokens) can't be set. Returns the UID, the result of a health check against the new datasource, and a config page link.
Input schema
Property Previous (2.2.0) Current (2.3.0) Change namestringrequired stringoptional - No longer required
- Description changed
10 unchanged entries
(schema root)accessbasicAuthdatabasefieldsisDefaultschemaReviewedtypeurlwithCredentials
No output schema is recorded for this tool in either release.
Link to this toolExact JSON from the published snapshots
Loads the exact recorded definitions of this tool from both releases. The full snapshots are linked under Evidence and provenance.
create_snapshotModifiedWhat changed
- create_snapshot: declared metadata changed (declared open_world: false → true).
Why it could matter
- Annotations such as idempotent or open-world hints can inform how clients treat a tool.
What to verify
- Confirm any client logic that relies on these annotations.
- Declared effect
- write → write
Input schema
Input schema unchanged.
7 unchanged entries
(schema root)dashboarddeleteKeyexpiresexternalkeyname
No output schema is recorded for this tool in either release.
Link to this toolExact JSON from the published snapshots
Loads the exact recorded definitions of this tool from both releases. The full snapshots are linked under Evidence and provenance.
get_dashboard_panel_queriesModifiedWhat changed
- get_dashboard_panel_queries: description changed.
Why it could matter
- Models choose and call tools partly from their descriptions.
What to verify
- Spot-check that agents still select this tool as intended.
- Declared effect
- read → read
- Description
- PreviousRetrieve panel queries from a Grafana dashboard. Supports all datasource types (Prometheus, Loki, CloudWatch, SQL, etc.) and row-nested panels. Optionally filter to a specific panel by ID with `panelId`. Provide `variables` (an empty object uses saved selections) or `start`/`end` to populate `processedQuery` and `requiredVariables`. Referenced All selections return `warnings` requesting explicit values. Returns an array of objects with fields: title, query (raw expression), datasource (object with uid and type), and optionally processedQuery, refId, requiredVariables, and target. Targets built in a visual editor (CloudWatch metric search, InfluxDB query builder) have no string expression: those return an empty query plus `target`, the panel's raw query JSON. They can be executed as panel queries but not as standalone expressions.
- CurrentRetrieve panel queries from a Grafana dashboard. Supports all datasource types (Prometheus, Loki, CloudWatch, SQL, etc.) and row-nested panels. Optionally filter to a specific panel by ID with `panelId`. Provide `variables` (an empty object uses saved selections) or `start`/`end` to populate `processedQuery` and `requiredVariables`. Referenced All selections, and variables saved without a value, return `warnings` requesting explicit values. Returns an array of objects with fields: title, query (raw expression), datasource (object with uid and type), and optionally processedQuery, refId, requiredVariables, and target. Targets built in a visual editor (CloudWatch metric search, InfluxDB query builder) have no string expression: those return an empty query plus `target`, the panel's raw query JSON. They can be executed as panel queries but not as standalone expressions.
Input schema
Input schema unchanged.
6 unchanged entries
(schema root)endpanelIdstartuidvariables
No output schema is recorded for this tool in either release.
Link to this toolExact JSON from the published snapshots
Loads the exact recorded definitions of this tool from both releases. The full snapshots are linked under Evidence and provenance.
grafana_api_requestModifiedWhat changed
- grafana_api_request: description changed.
Why it could matter
- Models choose and call tools partly from their descriptions.
What to verify
- Spot-check that agents still select this tool as intended.
- Declared effect
- write → write
- Description
- PreviousMake an authenticated HTTP request to the Grafana API. Similar to 'gh api' for GitHub. Supports any Grafana API endpoint with optional jq-style response filtering. Use this for API endpoints that don't have a dedicated tool.
- CurrentMake an authenticated HTTP request to the Grafana API. Supports any Grafana API endpoint with optional jq-style response filtering. Use this for API endpoints that don't have a dedicated tool.
Input schema
Input schema unchanged.
6 unchanged entries
(schema root)bodyendpointheadersjqmethod
No output schema is recorded for this tool in either release.
Link to this toolExact JSON from the published snapshots
Loads the exact recorded definitions of this tool from both releases. The full snapshots are linked under Evidence and provenance.
list_dashboard_versionsModifiedWhat changed
- list_dashboard_versions — Schema change: input property start changed: description "Version to start f… → "Number of newest v….
Why it could matter
- Calls or consumers built for the earlier schema may need to change.
What to verify
- Validate representative existing tool calls against the new argument schema.
- Declared effect
- read → read
Input schema
Property Previous (2.2.0) Current (2.3.0) Change startinteger, minimum=1optional integer, minimum=1optional - Description changed
3 unchanged entries
(schema root)limituid
No output schema is recorded for this tool in either release.
Link to this toolExact JSON from the published snapshots
Loads the exact recorded definitions of this tool from both releases. The full snapshots are linked under Evidence and provenance.
list_pyroscope_label_namesModifiedWhat changed
- list_pyroscope_label_names — Schema change: input property matchers changed: +description="Optionally, Promet….
Why it could matter
- Calls or consumers built for the earlier schema may need to change.
What to verify
- Validate representative existing tool calls against the new argument schema.
- Declared effect
- read → read
Input schema
Property Previous (2.2.0) Current (2.3.0) Change matchersstringoptional stringoptional - Description changed
4 unchanged entries
(schema root)data_source_uidend_rfc_3339start_rfc_3339
No output schema is recorded for this tool in either release.
Link to this toolExact JSON from the published snapshots
Loads the exact recorded definitions of this tool from both releases. The full snapshots are linked under Evidence and provenance.
list_tempo_attribute_namesModifiedWhat changed
- list_tempo_attribute_names — Schema change: input property added: end.
- list_tempo_attribute_names — Schema change: input property added: start.
Why it could matter
- Calls or consumers built for the earlier schema may need to change.
What to verify
- Validate representative existing tool calls against the new argument schema.
- Declared effect
- read → read
Input schema
Property Previous (2.2.0) Current (2.3.0) Change endnot present stringoptional - Added
startnot present stringoptional - Added
3 unchanged entries
(schema root)datasourceUidscope
No output schema is recorded for this tool in either release.
Link to this toolExact JSON from the published snapshots
Loads the exact recorded definitions of this tool from both releases. The full snapshots are linked under Evidence and provenance.
list_tempo_attribute_valuesModifiedWhat changed
- list_tempo_attribute_values — Schema change: input property added: end.
- list_tempo_attribute_values — Schema change: input property added: start.
Why it could matter
- Calls or consumers built for the earlier schema may need to change.
What to verify
- Validate representative existing tool calls against the new argument schema.
- Declared effect
- read → read
Input schema
Property Previous (2.2.0) Current (2.3.0) Change endnot present stringoptional - Added
startnot present stringoptional - Added
4 unchanged entries
(schema root)datasourceUidfilter-queryname
No output schema is recorded for this tool in either release.
Link to this toolExact JSON from the published snapshots
Loads the exact recorded definitions of this tool from both releases. The full snapshots are linked under Evidence and provenance.
query_loki_logsModifiedWhat changed
- query_loki_logs — Schema change: input property queryType changed: description "Query type: 'range… → "Query type: 'range….
Why it could matter
- Calls or consumers built for the earlier schema may need to change.
What to verify
- Validate representative existing tool calls against the new argument schema.
- Declared effect
- read → read
Input schema
Property Previous (2.2.0) Current (2.3.0) Change queryTypestringoptional stringoptional - Description changed
9 unchanged entries
(schema root)datasourceUiddirectionendRfc3339formatlimitlogqlstartRfc3339stepSeconds
No output schema is recorded for this tool in either release.
Link to this toolExact JSON from the published snapshots
Loads the exact recorded definitions of this tool from both releases. The full snapshots are linked under Evidence and provenance.
search_plugin_informationModifiedWhat changed
- search_plugin_information: description changed.
Why it could matter
- Models choose and call tools partly from their descriptions.
What to verify
- Spot-check that agents still select this tool as intended.
- Declared effect
- read → read
- Description
- PreviousSearch the Grafana plugin catalog by keyword, purpose, or partial name (e.g. 'azure monitoring', 'loki', 'database'). Returns results sorted by trust: official Grafana Labs plugins first, then commercial partner plugins, then community plugins, each with its exact pluginId. Results include warnings for enterprise-only or Angular-based plugins.
- CurrentSearch the Grafana plugin catalog by keyword, purpose, or partial name (e.g. 'azure monitoring', 'loki', 'database'). Returns results ordered by signature type (Grafana Labs, commercial, community), each with its exact pluginId. Results include warnings for enterprise-only or Angular-based plugins.
Input schema
Input schema unchanged.
2 unchanged entries
(schema root)query
No output schema is recorded for this tool in either release.
Link to this toolExact JSON from the published snapshots
Loads the exact recorded definitions of this tool from both releases. The full snapshots are linked under Evidence and provenance.
update_dashboardModifiedWhat changed
- update_dashboard: description changed.
Why it could matter
- Models choose and call tools partly from their descriptions.
What to verify
- Spot-check that agents still select this tool as intended.
- Declared effect
- write → write
- Description
- PreviousCreate or update a dashboard. Returns the saved dashboard UID and dashboard link in the 'url' field, using the instance public URL when available. Two modes: (1) Full JSON — provide 'dashboard' for new dashboards or complete replacements. (2) Patch — provide 'uid' + 'operations' to make targeted changes to an existing dashboard. One of these two modes is required; 'folderUid', 'message', and 'overwrite' are supplementary and do nothing on their own. Dashboard authoring guidance: if a saved query must support one, many, or All values from a multi-select variable inside a regex expression or matcher, save '${var:regex}' rather than plain '$var'. Saved dashboard annotation queries/definitions live in dashboard JSON under 'annotations.list'; annotation events are stored separately and are not part of the dashboard JSON. For stat panels over the current dashboard range, make the query return the range-level result the stat should display; panel-side reduction only reduces returned series and does not compute peak-over-range or ratio-of-peaks semantics for you. Patch operations support JSONPaths like '$.panels[0].targets[0].expr', '$.panels[1].title', '$.panels[2].targets[0].datasource', '$.templating.list/-', and '$.annotations.list/-'. Append to arrays with '/- ' syntax: '$.panels/- '. Remove by index: {"op": "remove", "path": "$.panels[2]"}. Multiple removes on the same array are automatically reordered to avoid index-shifting issues. Note: only numeric array indices are supported in patch paths; filter expressions like [?(@.id==2)] and wildcards like [*] are not supported. Schema: prefer v2 for new dashboards; if this Grafana lacks v2 the save fails saying so, then send v1. Keep an existing dashboard in its stored schema (indicated by 'isV2'/'apiVersion' on the fetched dashboard). A body with top-level 'elements'/'layout' is saved as v2. Minimal v2 body: {"title":"T","timeSettings":{"from":"now-6h","to":"now"},"variables":[],"elements":{"p1":{"kind":"Panel","spec":{"id":1,"title":"Up","vizConfig":{"kind":"VizConfig","group":"timeseries","spec":{}},"data":{"kind":"QueryGroup","spec":{"queries":[{"kind":"PanelQuery","spec":{"refId":"A","query":{"kind":"DataQuery","group":"prometheus","datasource":{"name":"<ds uid>"},"spec":{"expr":"up"}}}}]}}}}},"layout":{"kind":"GridLayout","spec":{"items":[{"kind":"GridLayoutItem","spec":{"x":0,"y":0,"width":24,"height":8,"element":{"kind":"ElementReference","name":"p1"}}}]}}}. For tabs, layout is {"kind":"TabsLayout","spec":{"tabs":[{"kind":"TabsLayoutTab","spec":{"title":"A","layout":<GridLayout>}}]}}.
- CurrentCreate or update a dashboard. Returns the saved dashboard UID and dashboard link in the 'url' field, using the instance public URL when available. Two modes: (1) Full JSON — provide 'dashboard' for new dashboards or complete replacements. (2) Patch — provide 'uid' + 'operations' to make targeted changes to an existing dashboard. One of these two modes is required; 'folderUid', 'message', and 'overwrite' are supplementary and do nothing on their own. Dashboard authoring guidance: if a saved query must support one, many, or All values from a multi-select variable inside a regex expression or matcher, save '${var:regex}' rather than plain '$var'. Saved dashboard annotation queries/definitions live in dashboard JSON under 'annotations.list'; annotation events are stored separately and are not part of the dashboard JSON. For stat panels over the current dashboard range, make the query return the range-level result the stat should display; panel-side reduction only reduces returned series and does not compute peak-over-range or ratio-of-peaks semantics for you. Patch operations support JSONPaths like '$.panels[0].targets[0].expr', '$.panels[1].title', '$.panels[2].targets[0].datasource', '$.templating.list/-', and '$.annotations.list/-'. Append to arrays with '/- ' syntax: '$.panels/- '. Remove by index: {"op": "remove", "path": "$.panels[2]"}. Multiple removes on the same array are automatically reordered to avoid index-shifting issues. Note: only numeric array indices are supported in patch paths; filter expressions like [?(@.id==2)] and wildcards like [*] are not supported. Schema: prefer v2 for new dashboards; if this Grafana lacks v2 the save fails saying so, then send v1. Keep an existing dashboard in its stored schema (indicated by 'isV2'/'apiVersion' on the fetched dashboard). A body with top-level 'elements'/'layout' is saved as v2. Send list fields as [] when empty; the server fills links, tags, variables and each panel's links and transformations if omitted. Minimal v2 body: {"title":"T","timeSettings":{"from":"now-6h","to":"now"},"variables":[],"links":[],"elements":{"p1":{"kind":"Panel","spec":{"id":1,"title":"Up","vizConfig":{"kind":"VizConfig","group":"timeseries","spec":{}},"data":{"kind":"QueryGroup","spec":{"queries":[{"kind":"PanelQuery","spec":{"refId":"A","query":{"kind":"DataQuery","group":"prometheus","datasource":{"name":"<ds uid>"},"spec":{"expr":"up"}}}}],"transformations":[]}}}}},"layout":{"kind":"GridLayout","spec":{"items":[{"kind":"GridLayoutItem","spec":{"x":0,"y":0,"width":24,"height":8,"element":{"kind":"ElementReference","name":"p1"}}}]}}}. For tabs, layout is {"kind":"TabsLayout","spec":{"tabs":[{"kind":"TabsLayoutTab","spec":{"title":"A","layout":<GridLayout>}}]}}.
Input schema
Input schema unchanged.
12 unchanged entries
(schema root)dashboardfolderUidmessageoperationsoperations › [items]operations › [items] › opoperations › [items] › pathoperations › [items] › valueoverwriteuiduserId
No output schema is recorded for this tool in either release.
Link to this toolExact JSON from the published snapshots
Loads the exact recorded definitions of this tool from both releases. The full snapshots are linked under Evidence and provenance.
update_datasourceModifiedWhat changed
- update_datasource: declared metadata changed (declared open_world: false → true).
Why it could matter
- Annotations such as idempotent or open-world hints can inform how clients treat a tool.
What to verify
- Confirm any client logic that relies on these annotations.
- Declared effect
- write → write
Input schema
Input schema unchanged.
11 unchanged entries
(schema root)accessbasicAuthdatabasefieldsisDefaultjsonDatanameschemaRevieweduidurl
No output schema is recorded for this tool in either release.
Link to this toolExact JSON from the published snapshots
Loads the exact recorded definitions of this tool from both releases. The full snapshots are linked under Evidence and provenance.
No tools match these filters.
66 tools with no recorded change
add_activity_to_incidentalerting_manage_routingalerting_routing_writealerting_rules_readalerting_silences_readanalyze_loki_labelscheck_datasources_healthcreate_annotationcreate_foldercreate_incidentdelete_annotationdelete_snapshotdiff_tempo_tracesgenerate_deeplinkget_alert_groupget_annotation_tagsget_annotationsget_assertionsget_current_oncall_usersget_dashboard_by_uidget_dashboard_propertyget_dashboard_summaryget_datasourceget_docget_incidentget_oncall_shiftget_panel_imageget_pluginget_snapshotget_tempo_traceget_tempo_traceql_docsinstall_pluginlist_alert_groupslist_datasourceslist_incident_custom_fieldslist_incidentslist_loki_label_nameslist_loki_label_valueslist_oncall_scheduleslist_oncall_teamslist_oncall_userslist_prometheus_label_nameslist_prometheus_label_valueslist_prometheus_metric_metadatalist_prometheus_metric_nameslist_provisioning_repositorieslist_pyroscope_label_valueslist_pyroscope_profile_typeslist_snapshotsquery_loki_patternsquery_loki_statsquery_prometheusquery_prometheus_histogramquery_pyroscopequery_tempo_metricsrender_grafana_appsearch_dashboardssearch_docssearch_folderssearch_tempo_tracessuggest_loki_alloy_label_configupdate_alert_groupupdate_annotationupdate_incidentuser_infovalidate_provisioning_file
Evidence and provenance
- Static findings
- REVIEW from Modelara’s automated analysis of the two declared interfaces. A policy outcome, not a security rating or a runtime test.
- Human review
- Pending human review. No reviewer decision is recorded for this comparison.
- Published evidence
- Part of Valyd’s published data generation listed in valyd-data-source.json. Published records are not rewritten.
Show provenance and exact files
- Comparison
grafana/2.2.0~2.3.0The published comparison identifier.- Analyzer
modelara v0.1.8Policy version not recorded.Analyzed Nov 11, 2026, 1:20 AM UTC.- Distribution
go- Previous release
github.com/grafana/mcp-grafana@2.2.080 tools · published by the registry Nov 2, 2026, 1:00 PM UTC · upstream v2.2.0Artifact integritysha256-UQEVfp6lLBCqd/PFWetqv1qD0eY96hr1V1S6ikI1fsE=Artifactmcp-grafana_2.2.0_checksums.txtInterface fingerprintsha256:6c90f99fefa676ac6de70103153f4d2b1cbacfdce750d6c0fd27c54f9296f211Exact interface snapshot (JSON)- Current release
github.com/grafana/mcp-grafana@2.3.080 tools · published by the registry Nov 10, 2026, 5:45 PM UTC · upstream v2.3.0Artifact integritysha256-KzMqlyk2+lJPgQUdRn6uJNmCAvzs/17KAR2tEFAh4l4=Artifactmcp-grafana_2.3.0_checksums.txtInterface fingerprintsha256:c08fb18259d52f1a5941303ad6185d1c75bf357525fbf6e6052b68597b350e94Exact interface snapshot (JSON)- Comparison record
- Exact comparison record (JSON)
The integrity value or digest identifies the exact artifact that was inspected; it does not show that the package is safe. The interface fingerprint identifies the declared tools and schemas Modelara recorded for that release.
MODELARA ANALYSIS OUTPUT
Interface findings
Requires review
8 findingsalerting_rules_writeREVIEWChangedShow details
input property removed: label_selectorsinput property removed: limit_alertsinput property removed: matchersinput property removed: rule_limitinput property removed: rule_typeinput property removed: search_folderinput property removed: search_rule_nameinput property removed: statesinput property datasource_uid changed: description "Datasource UID for… → "Datasource UID for…input property folder_uid changed: description "The folder UID. Fo… → "The folder UID. Re…input property notification_settings changed: description "Notification setti… → "Notification setti…input property operation changed: description "The operation to p… → "The operation to p…, enum ["list","get","vers… → ["create","update",…input property rule_uid changed: description "The UID of the ale… → "The UID of the ale…
alerting_silences_writeREVIEWChangedShow details
input property removed: rule_uidinput property matchers changed: description "Label matchers. Re… → "Label matchers. Re…input property operation changed: description "The operation to p… → "The operation to p…, enum ["list","get","crea… → ["create","update",…input property silence_id changed: description "The silence id (re… → "The silence id (re…input property starts_at changed: description "Silence start time… → "Silence start time…
create_datasourceREVIEWChangedShow details
input property name changed: description "Datasource display… → "Datasource display…input required: [name, type] → [type]
list_dashboard_versionsREVIEWChangedShow details
input property start changed: description "Version to start f… → "Number of newest v…
list_pyroscope_label_namesREVIEWChangedShow details
input property matchers changed: +description="Optionally, Promet…
list_tempo_attribute_namesREVIEWChangedShow details
input property added: endinput property added: start
list_tempo_attribute_valuesREVIEWChangedShow details
input property added: endinput property added: start
query_loki_logsREVIEWChangedShow details
input property queryType changed: description "Query type: 'range… → "Query type: 'range…
Informational
8 findingscreate_datasourceINFOChangedget_dashboard_panel_queriesINFOChangedgrafana_api_requestINFOChangedsearch_plugin_informationINFOChangedupdate_dashboardINFOChangedcreate_datasourceINFOChangedShow details
declared open_world: false → true
create_snapshotINFOChangedShow details
declared open_world: false → true
update_datasourceINFOChangedShow details
declared open_world: false → true
What do these results mean?
- PASS
- No policy-significant interface change detected.
- REVIEW
- Interface changes require inspection.
- FAIL
- A policy-significant change was detected.
- INVALID
- The comparison could not be evaluated reliably.