observability Static interface comparison
Grafana MCP
2.1.1 2.2.0
1 new destructive capability requires explicit review.
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
- 1Added tools
- 0Removed tools
- 13Modified tools
- 6Input-schema changes
- 0Output-schema changes
- 1Declared authority changes
14 tools with recorded changes
get_dashboard_panel_queriesModifiedWhat changed
- get_dashboard_panel_queries — Schema change: input property added: end.
- get_dashboard_panel_queries — Schema change: input property added: start.
- get_dashboard_panel_queries: description changed.
Why it could matter
- Calls or consumers built for the earlier schema may need to change.
- Models choose and call tools partly from their descriptions.
What to verify
- Validate representative existing tool calls against the new argument schema.
- 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`. Optionally provide `variables` for template variable substitution, which populates `processedQuery` and `requiredVariables` fields. 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 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
Property Previous (2.1.1) Current (2.2.0) Change endnot present stringoptional - Added
startnot present stringoptional - Added
4 unchanged entries
(schema root)panelIduidvariables
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_tempo_traceModifiedWhat changed
- get_tempo_trace — Schema change: input property added: end.
- get_tempo_trace — Schema change: input property added: start.
- get_tempo_trace: description changed.
Why it could matter
- Calls or consumers built for the earlier schema may need to change.
- Models choose and call tools partly from their descriptions.
What to verify
- Validate representative existing tool calls against the new argument schema.
- Spot-check that agents still select this tool as intended.
- Declared effect
- read → read
- Description
- PreviousRetrieve a specific trace by ID
- CurrentRetrieve a specific trace by ID. Returns its spans grouped by service and resource, with span attributes, events and links.
Input schema
Property Previous (2.1.1) Current (2.2.0) Change endnot present stringoptional - Added
startnot present stringoptional - Added
4 unchanged entries
(schema root)datasourceUidfocus_span_idtrace_id
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_prometheus_label_namesModifiedWhat changed
- list_prometheus_label_names — Schema change: input property matches changed: items {"properties":{"fil… → {"oneOf":[{"descrip….
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.1.1) Current (2.2.0) Change matches › [items]object oneOf (2) - Changed: oneOf
- Type changed
oneOf: — → [{"description":"A Prometheus selector such as {job=\"api\"}","type":"string"},{"properties":{"filters":{"items":{"properties":{"name":{"description":"The name of the label to match against","type":"string"},"type":{"description":"One of th… (truncated: full value in the exact JSON)type: "object" → —matches › [items] › filtersarrayoptional not present - Removed
matches › [items] › filters › [items]object not present - Removed
matches › [items] › filters › [items] › namestringrequired not present - Removed
matches › [items] › filters › [items] › typestringrequired not present - Removed
matches › [items] › filters › [items] › valuestringrequired not present - Removed
7 unchanged entries
(schema root)datasourceUidendRfc3339limitmatchesprojectNamestartRfc3339
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_prometheus_label_valuesModifiedWhat changed
- list_prometheus_label_values — Schema change: input property matches changed: items {"properties":{"fil… → {"oneOf":[{"descrip….
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.1.1) Current (2.2.0) Change matches › [items]object oneOf (2) - Changed: oneOf
- Type changed
oneOf: — → [{"description":"A Prometheus selector such as {job=\"api\"}","type":"string"},{"properties":{"filters":{"items":{"properties":{"name":{"description":"The name of the label to match against","type":"string"},"type":{"description":"One of th… (truncated: full value in the exact JSON)type: "object" → —matches › [items] › filtersarrayoptional not present - Removed
matches › [items] › filters › [items]object not present - Removed
matches › [items] › filters › [items] › namestringrequired not present - Removed
matches › [items] › filters › [items] › typestringrequired not present - Removed
matches › [items] › filters › [items] › valuestringrequired not present - Removed
8 unchanged entries
(schema root)datasourceUidendRfc3339labelNamelimitmatchesprojectNamestartRfc3339
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: 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
- PreviousExecutes a log query against a Loki or VictoriaLogs datasource and returns matching log entries (or metric samples on Loki). Defaults to the last hour, a limit of 10 entries, and 'backward' direction (newest first). The `logql` parameter takes LogQL on Loki and LogsQL on VictoriaLogs (e.g., Loki: `{app="foo"} |= "error"`; VictoriaLogs: `{app="foo"} "error"`). To count matching log lines precisely, use a `count_over_time()` metric query with queryType='instant'. For broad queries that match many lines, set `format` to 'compact' to group results by stream and avoid repeating label metadata on every line. If this server enables the Loki cost guardrail, expensive queries are rejected before execution: query cost is bytes SCANNED, determined only by the stream selector and time range — line filters (|=) and parsers (| json) reduce what is returned, not what is scanned. Use a stream selector with at least one selective positive label matcher (never `{}`, `=~".*"`/`=~".+"`, or negative-only matchers), keep time ranges narrow; rejected queries return rewrite guidance.
- CurrentExecutes a log query against a Loki or VictoriaLogs datasource and returns matching log entries (or metric samples on Loki). Defaults to the last hour, a limit of 10 entries, and 'backward' direction (newest first). The `logql` parameter takes LogQL on Loki and LogsQL on VictoriaLogs (e.g., Loki: `{app="foo"} |= "error"`; VictoriaLogs: `{app="foo"} "error"`). To count matching log lines precisely, use a `count_over_time()` metric query with queryType='instant'. For broad queries that match many lines, set `format` to 'compact' to group results by stream and avoid repeating label metadata on every line. Query cost is the bytes scanned, which the index statistics for the stream selector over the same time range estimate before a broad selector or long time range is run. If this server enables the Loki cost guardrail, expensive queries are rejected before execution: query cost is bytes SCANNED, determined only by the stream selector and time range — line filters (|=) and parsers (| json) reduce what is returned, not what is scanned. Use a stream selector with at least one selective positive label matcher (never `{}`, `=~".*"`/`=~".+"`, or negative-only matchers), keep time ranges narrow; rejected queries return rewrite guidance.
Input schema
Input schema unchanged.
10 unchanged entries
(schema root)datasourceUiddirectionendRfc3339formatlimitlogqlqueryTypestartRfc3339stepSeconds
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_patternsModifiedWhat changed
- query_loki_patterns: 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
- PreviousRetrieves detected log patterns from a Loki datasource for a given stream selector and time range. Returns a list of patterns, each containing a pattern string and a total count of occurrences. Patterns help identify common log structures and anomalies. The `logql` parameter must be a stream selector (e.g., `{job="nginx"}`) and does not support line filters or aggregations. Defaults to the last hour if the time range is omitted. **Not supported on VictoriaLogs** datasources - use a `| stats` pipeline instead.
- CurrentRetrieves detected log patterns from a Loki datasource for a given stream selector and time range. Returns a list of patterns, each containing a pattern string, a total count of occurrences, and a detected `level` when available. Patterns help identify common log structures and anomalies. The `logql` parameter must be a stream selector (e.g., `{job="nginx"}`) and does not support line filters or aggregations. Defaults to the last hour if the time range is omitted. **Not supported on VictoriaLogs** datasources - use a `| stats` pipeline instead.
Input schema
Input schema unchanged.
6 unchanged entries
(schema root)datasourceUidendRfc3339logqlstartRfc3339step
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_statsModifiedWhat changed
- query_loki_stats: 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
- PreviousRetrieves index-level statistics about log streams matching a given selector within a Loki or VictoriaLogs datasource and time range. Returns an object containing the count of streams, chunks, entries, and total bytes (e.g., `{"streams": 5, "chunks": 50, "entries": 10000, "bytes": 512000}`). **Important**: the `entries` count reflects storage-level index entries (chunk metadata), NOT the number of individual log lines matching the selector. Counting actual matching log lines requires a `count_over_time()` LogQL metric query. On VictoriaLogs only `entries` is populated; the other fields remain zero. The `logql` parameter **must** be a simple label selector (e.g., `{app="nginx", env="prod"}`) and does not support line filters, parsers, or aggregations. Defaults to the last hour if the time range is omitted.
- CurrentRetrieves index-level statistics about log streams matching a given selector within a Loki or VictoriaLogs datasource and time range. Returns an object containing the count of streams, chunks, entries, and total bytes (e.g., `{"streams": 5, "chunks": 50, "entries": 10000, "bytes": 512000}`). **Important**: the `entries` count reflects storage-level index entries (chunk metadata), NOT the number of individual log lines matching the selector. Counting actual matching log lines requires a `count_over_time()` LogQL metric query. On VictoriaLogs only `entries` is populated; the other fields remain zero. The `logql` parameter **must** be a simple label selector (e.g., `{app="nginx", env="prod"}`) and does not support line filters, parsers, or aggregations. The `bytes` field estimates how much data a log query over the same selector and time range would scan, which is useful to know before running a broad selector or long time range. Defaults to the last hour if the time range is omitted.
Input schema
Input schema unchanged.
5 unchanged entries
(schema root)datasourceUidendRfc3339logqlstartRfc3339
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_prometheusModifiedWhat changed
- query_prometheus: 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
- PreviousQuery a PromQL-compatible datasource (Prometheus, Thanos, Mimir, Cloud Monitoring, etc.) using a PromQL expression. Supports instant queries (single point) and range queries (time range). Time: RFC3339 or relative expressions like 'now', 'now-1h'.
- CurrentQuery a PromQL-compatible datasource (Prometheus, Thanos, Mimir, Cloud Monitoring, etc.) using a PromQL expression. Returns data without opening a chart. Supports instant and range queries. Time: RFC3339 or relative expressions like 'now', 'now-1h'.
Input schema
Input schema unchanged.
8 unchanged entries
(schema root)datasourceUidendTimeexprprojectNamequeryTypestartTimestepSeconds
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_pyroscopeModifiedWhat changed
- query_pyroscope: 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
- Previous Unified Pyroscope query tool for fetching profiles or metrics from Pyroscope. Profile data shows WHICH functions consume resources; metrics data shows WHEN consumption spiked. Use query_type="both" for complete analysis in one call. query_type options (extends Grafana's PyroscopeQueryType): - "profile": returns profile data (shape controlled by format) - "metrics": returns time-series data points - "both" (default): returns both profile and metrics in one response format options (shape of the profile data): - "table" (default): per-function table with flat (self) and cumulative values, ranked by flat - "dot": call graph in Graphviz DOT format; nodes are per source line, so one function may span several nodes
- Current Unified Pyroscope query tool for fetching profiles or metrics from Pyroscope. Profile data shows WHICH functions consume resources; metrics data shows WHEN consumption spiked. Use query_type="both" for complete analysis in one call. query_type options (extends Grafana's PyroscopeQueryType): - "profile": returns profile data (shape controlled by format) - "metrics": returns time-series data points; for cumulative profile types (e.g. CPU time, allocations) each point is a per-second rate over its step, in the reported unit (e.g. "cores" for CPU time) - "both" (default): returns both profile and metrics in one response format options (shape of the profile data): - "table" (default): per-function table with flat (self) and cumulative values, ranked by flat - "dot": call graph in Graphviz DOT format; nodes are per source line, so one function may span several nodes
Input schema
Input schema unchanged.
12 unchanged entries
(schema root)data_source_uidend_rfc_3339formatgroup_bygroup_by › [items]matchersmax_node_depthprofile_typequery_typestart_rfc_3339step
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_tempo_metricsModifiedWhat changed
- query_tempo_metrics: 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
- PreviousCompute trace-derived metrics using a TraceQL metrics query. The syntax is unlike PromQL. Use type 'instant' for a single value or 'range' for a time series (default). Instant queries over large time ranges may timeout — keep the window under 15 minutes for instant, or use range instead.
- CurrentCompute trace-derived metrics using a TraceQL metrics query. The syntax is unlike PromQL. Use type 'instant' for a single value or 'range' for a time series (default). Instant queries over large time ranges may timeout — keep the window under 15 minutes for instant, or use range instead. Returns each series with its labels and either its samples and exemplars (range) or a single value (instant).
Input schema
Input schema unchanged.
6 unchanged entries
(schema root)datasourceUidendquerystarttype
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.
render_grafana_appAddedWhat changed
- New read-only tool render_grafana_app.
Why it could matter
- The release adds a capability without declared write authority.
What to verify
- Decide whether agents should be offered this tool.
- Declared effect
- — → read
Input schema
Property Previous (2.1.1) Current (2.2.0) Change (schema root)not present object, additionalProperties=false - Added
argumentsnot present object, anyOf (2)required - Added
toolNamenot present string, enum (2)required - Added
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_dashboardsModifiedWhat changed
- search_dashboards — Schema change: input property added: folderPath.
- search_dashboards — Schema change: input property query changed: description "Optional query. Om… → "Optional query. Om….
- search_dashboards: description changed.
Why it could matter
- Calls or consumers built for the earlier schema may need to change.
- Models choose and call tools partly from their descriptions.
What to verify
- Validate representative existing tool calls against the new argument schema.
- Spot-check that agents still select this tool as intended.
- Declared effect
- read → read
- Description
- PreviousSearch Grafana dashboards by query and/or folderUid, tag, and starred. Returns matching dashboards with title, UID, folder, tags, and URL.
- CurrentSearch Grafana dashboards by query and/or folderUid, folderPath, tag, and starred. Returns matching dashboards with title, UID, folder, folder path, tags, and URL.
Input schema
Property Previous (2.1.1) Current (2.2.0) Change folderPathnot present stringoptional - Added
querystringoptional stringoptional - Description changed
7 unchanged entries
(schema root)folderUidlimitpagestarredtagtag › [items]
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_tempo_tracesModifiedWhat changed
- search_tempo_traces — Schema change: input property added: limit.
- search_tempo_traces — Schema change: input property added: spss.
- search_tempo_traces: description changed.
Why it could matter
- Calls or consumers built for the earlier schema may need to change.
- Models choose and call tools partly from their descriptions.
What to verify
- Validate representative existing tool calls against the new argument schema.
- Spot-check that agents still select this tool as intended.
- Declared effect
- read → read
- Description
- PreviousSearch for traces using TraceQL queries
- CurrentSearch for traces using TraceQL queries. Returns each matching trace with its root service, root span name, start time and duration, and the span sets the query matched. Each span lists its ID, start time, duration and the attributes the query returned, as an object mapping attribute names to values.
Input schema
Property Previous (2.1.1) Current (2.2.0) Change limitnot present integer, default=20optional - Added
spssnot present integer, default=3optional - Added
5 unchanged entries
(schema root)datasourceUidendquerystart
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_incidentModifiedWhat changed
- update_incident: declared effect changed from write to destructive.
Why it could matter
- An existing tool name now declares stronger authority, so a configuration that allowed it before may allow more now.
What to verify
- Re-confirm whether agents should keep access to this tool.
- Declared effect
- write → write
Input schema
Input schema unchanged.
10 unchanged entries
(schema root)customFieldscustomFields › [items]customFields › [items] › fieldcustomFields › [items] › valuescustomFields › [items] › values › [items]incidentIdseveritystatustitle
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_rules_writealerting_silences_readalerting_silences_writeanalyze_loki_labelscheck_datasources_healthcreate_annotationcreate_datasourcecreate_foldercreate_incidentcreate_snapshotdelete_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_traceql_docsgrafana_api_requestinstall_pluginlist_alert_groupslist_dashboard_versionslist_datasourceslist_incident_custom_fieldslist_incidentslist_loki_label_nameslist_loki_label_valueslist_oncall_scheduleslist_oncall_teamslist_oncall_userslist_prometheus_metric_metadatalist_prometheus_metric_nameslist_provisioning_repositorieslist_pyroscope_label_nameslist_pyroscope_label_valueslist_pyroscope_profile_typeslist_snapshotslist_tempo_attribute_nameslist_tempo_attribute_valuesquery_prometheus_histogramsearch_docssearch_folderssearch_plugin_informationsuggest_loki_alloy_label_configupdate_alert_groupupdate_annotationupdate_dashboardupdate_datasourceuser_infovalidate_provisioning_file
Evidence and provenance
- Static findings
- FAIL 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.1.1~2.2.0The published comparison identifier.- Analyzer
modelara v0.1.8Policy version not recorded.Analyzed Nov 5, 2026, 2:34 AM UTC.- Distribution
go- Previous release
github.com/grafana/mcp-grafana@2.1.179 tools · published by the registry Oct 20, 2026, 5:35 PM UTC · upstream v2.1.1Artifact integritysha256-1sjk0fV6N0uFFXIYp6iERP/BVdbN8BhUr+IdQEOv1UY=Artifactmcp-grafana_2.1.1_checksums.txtInterface fingerprintsha256:09fd47b7457fbb379c39374ed286a1690b09482abf53366adf89726eb8d20bb5Exact interface snapshot (JSON)- Current 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)- 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
Policy failures
1 findingupdate_incidentFAILChanged
Requires review
6 findingsget_dashboard_panel_queriesREVIEWChangedShow details
input property added: endinput property added: start
get_tempo_traceREVIEWChangedShow details
input property added: endinput property added: start
list_prometheus_label_namesREVIEWChangedShow details
input property matches changed: items {"properties":{"fil… → {"oneOf":[{"descrip…
list_prometheus_label_valuesREVIEWChangedShow details
input property matches changed: items {"properties":{"fil… → {"oneOf":[{"descrip…
search_dashboardsREVIEWChangedShow details
input property added: folderPathinput property query changed: description "Optional query. Om… → "Optional query. Om…
search_tempo_tracesREVIEWChangedShow details
input property added: limitinput property added: spss
Informational
11 findingsrender_grafana_appINFOAddedget_dashboard_panel_queriesINFOChangedget_tempo_traceINFOChangedquery_loki_logsINFOChangedquery_loki_patternsINFOChangedquery_loki_statsINFOChangedquery_prometheusINFOChangedquery_pyroscopeINFOChangedquery_tempo_metricsINFOChangedsearch_dashboardsINFOChangedsearch_tempo_tracesINFOChanged
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.