Repository navigation
feat(container): update image docker.io/grafana/mcp-grafana (2.2.0 ➔ 2.3.0) - #6831
Merged
Merged
Conversation
Contributor
Author
|
Tip Routine: only container-image and chart-version changes; 1 resource across 1 app
konflate 0.6.6 · rendered |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
2.2.0→2.3.0Warning
Some dependencies could not be looked up. Check the Dependency Dashboard for more information.
Release Notes
grafana/mcp-grafana (docker.io/grafana/mcp-grafana)
v2.3.0Compare Source
Added
run_panel_queryruns Elasticsearch panels, through/api/ds/querywith Lucene variable formatting (${var:lucene}works for every datasource) and the panel interval sent so auto date histograms stay under Elasticsearch's bucket limit. ES|QL panels are rejected (#1468)query_elasticsearchacceptsformat: "compact", which returns only the timestamp, message and level fields, andfieldsto pick source fields, so log responses are much smaller. The default output is unchanged (#1513)--prometheus-guardrail-require-selective-labelsrequires every selector to carry a positive label matcher beyond the metric name, so unscoped queries likeuporup{instance=~".*"}are flagged or rejected (#1470)grafana://irm/incidents/{id}, alongside datasources. Any incident can be read by URI, and a resource kind that fails or times out is left out of the list without hiding the others (#1472)render_grafana_appcan add up to five short notes after its text line, such as a failed query, so the model sees them in the same turn (#1492)0, the SSE and streamable HTTP transports bind a free port and write the bound address tomcp-grafana-addressin the working directory (#1480)Fixed
run_panel_queryand dashboard inspection match Grafana more closely:$__intervaland$__autoare rounded like Grafana (30s for 1h, not 36s) and honour the panel's max data points and min interval and the datasource's interval, and the Loki step keeps sub-second values (#1524, #1527)$__interval, stay literal, and macros only match complete names, so$__interval_envisn't partially replaced (#1522, #1451)$jobto the datasource (#1525)get_dashboard_by_uidkeeps the version in the body, soupdate_dashboardwithoverwrite: falsesaves instead of failing with an empty 409, and a real conflict says to read the dashboard again (#1516)get_dashboard_by_uidandget_dashboard_summaryfillcreated,updated,versionandprovisionedin meta (#1504)alerting_rules_writekeeps snake_casenotification_settingskeys asalerting_rules_readreturns them, instead of silently dropping grouping, timings and time intervals on update, and rejects unknown keys (#1517)list_loki_label_names,list_loki_label_valuesandanalyze_loki_labelsdefault to the last hour, as documented, instead of sending no range (#1554)query_loki_logsworks again on Grafana before 11.0 (#1488)/resourcesfallback goes to a real Loki route, so stats, patterns and label tools no longer fail with Loki's HTML UI page until restart (#1380)list_tempo_attribute_namesandlist_tempo_attribute_valuesacceptstartandend(default the past hour), so they find attributes from older traces (#1536)list_pyroscope_label_namesandlist_pyroscope_label_valuesaccept bare matchers likeservice_name="x"(#1538)query_cloudwatch_logsno longer times out when query caching is enabled on the datasource (#1515)query_sqlcaps only top-levelLIMITs, so aLIMITin a comment, string or CTE no longer skips the cap and subquery limits are left alone (#1503)pageis omitted in proxy mode, as they do otherwise (#1547)generate_deeplinkandget_panel_imageconvert RFC3339, date-only and naive times to epoch milliseconds, so links and renders no longer open at 1970 (#1501, #1546)query_elasticsearchand the Quickwit tool say numeric timestamps are Unix milliseconds (#1539)list_prometheus_metric_metadataapplieslimitPerMetric(#1496)x[30d + 30d]as unparseable instead of letting them past the range cap (#1507)list_dashboard_versionsdescribesstartas an offset (#1467)Changed
alerting_rules_writeandalerting_silences_writeaccept only create, update and delete; list and get are on the read tools registered alongside them.create_datasourceno longer requiresname, andcreate_datasource,update_datasourceandcreate_snapshotsetopenWorldHint(#1511)Security
--loki-enforced-matchersapplies to every/api/ds/queryrequest that reaches a Loki datasource, whichever tool builds it, andquery_prometheusrejects Loki and VictoriaLogs datasources. In v2.2.0, a LogQL metric query throughquery_prometheuscould return streams outside the enforced matchers (#1182)Configuration
📅 Schedule: (in timezone Europe/Stockholm)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about these updates again.
This PR has been generated by Mend Renovate CLI.