* Chore: Update copy and comments to refer to Metrics Drilldown
* chore: replace explore-metrics with metrics-drilldown in api.ts
* chore: replace explore-metrics with metrics-drilldown in a
pi.test.ts
* chore: rename remaining instances in /public/app/features/trails
* Update public/app/features/trails/Integrations/dashboardIntegration.ts
Co-authored-by: Nick Richmond <5732000+NWRichmond@users.noreply.github.com>
* Update public/app/features/trails/Integrations/dashboardIntegration.ts
Co-authored-by: Nick Richmond <5732000+NWRichmond@users.noreply.github.com>
---------
Co-authored-by: Nick Richmond <5732000+NWRichmond@users.noreply.github.com>
This PR adds errorsource attribution to the influxql and flux query paths
when the query model cannot be parsed, which is a user error.
It also catches cases where the datasource configuration does not
contain a scheme or host, and adds downstream attribution to those
errors.
Error handling on the influxql query path is updated to match 'all errors
are per query, and stashed on the response object' pattern.
Fixes https://github.com/grafana/oss-plugin-partnerships/issues/1250
* Fixed usage of incorrect type in the 'usePluginComponents' hook.
* improved betterer.
* Changed import path of usePluginLinks types.
* improved betterer result.
What is this feature?
This change adds properties and known annotations to store them in for recording resource manager information, such as:
The type (kind) of the manager (ex. Terraform / kubectl / etc.)
The identity of the manager (ex. grafana/terraform-provider-grafana)
Whether the managers allows the resource to be edited by others.
Whether a resource is temporarily excluded from the manager's control.
These annotations are inspired by Kubernetes field management API (https://kubernetes.io/docs/reference/using-api/server-side-apply/#field-management) and known Kubernetes annotations
(https://kubernetes.io/docs/reference/labels-annotations-taints/#app-kubernetes-io-managed-by).
It also adds annotations for storing information about the source of a provisioned resource, such as path, checksum & timestamp.
Why do we need this feature?
To make it possible to mark resources as managed by specific managers, modifying how these resources appear in the UI and are treated in the backend APIs.
For example, we'd like to make managed resources read-only, or show specific docs / workflows based on the tool which is used to manage resources and so on.
The identity is required for ensuring that managers of the same kind can still be told apart.
Who is this feature for?
For as-code practitioners and API users.
---------
Signed-off-by: Igor Suleymanov <igor.suleymanov@grafana.com>
Co-authored-by: Ryan McKinley <ryantxu@gmail.com>
* Update ErrRequestErrorBase to make it more clear for developers
* Trigger build
* requestError -> requestFailureError
* Fix test
* Update pkg/plugins/backendplugin/grpcplugin/client_v2.go
Co-authored-by: Will Browne <wbrowne@users.noreply.github.com>
---------
Co-authored-by: Will Browne <wbrowne@users.noreply.github.com>
Matthew Jacobson
Vardan TorosyanandIrene Rodríguez
Kat YangandNick Richmond
beejeebus
Will Assis
Peter Štibraný
Georges Chaudy
Eric Leijonmarck
Jean-Philippe Quéméner
Carl Bergquist
Karl Persson
xavi
Marcus Andersson
Andres Martinez Gotor
Ivan Ortega Alba
Oscar Kilhed
Tom Ratcliffe
Igor SuleymanovandRyan McKinley
Ivana HuckovaandWill Browne
Charandas
grafana-pr-automation[bot]andgithub-actions[bot]
Stephanie Hingtgen
Todd Treece
Robin SchneiderandMatheus Macabu
tab0r
maiconandGeorges Chaudy
Haris Rozajac