---
title: "Edelbyte Datasource changelog for Grafana"
description: "Grafana data source for Edelbyte. Edelbyte Datasource plugin for Grafana by Edelbyte. Available in Grafana Cloud and self-managed Grafana."
---

> This is the Markdown version of https://grafana.com/grafana/plugins/edelbyte-kql-datasource/changelog/

# Edelbyte Datasource - Change log

# Changelog

## 0.7.4

- New README for the catalog page: what the plugin does, configuration, querying, and the data it sends to third parties. Installation from source, development and build steps are no longer in the README; they moved to `doc/dev-setup.md` in the repository.
- The README states the minimum Grafana version as 11.6.11, matching `grafanaDependency`.

## 0.7.3

- Removed the Workload Identity Federation auth type, with its configuration fields and documentation. It read token files and environment variables, which plugins cannot rely on (and which is not supported in Grafana Cloud). A datasource still set to `workloadidentity` now fails to load with a message asking for another auth type.
- The AWS STS `AssumeRole` call of the AWS IAM Role auth type now uses Grafana's SDK HTTP client instead of the AWS SDK's default transport.
- Trace tag and log conversion, and the (currently disabled) time-series conversion, validate types and timestamps and return conversion errors instead of panicking on unexpected values.
- Updated the Edelbyte SDK to v0.7.3. **`.edelbyte.com` is no longer a trusted domain**: it is not an Edelbyte-owned domain, so the access token is no longer sent to it. The trusted domains are now `.edelbyte.dev`, `.edelbyte.cloud` and `.edelbyte-dev.cloud` (plus loopback). A datasource whose Cluster URL is on `.edelbyte.com` fails with "not a trusted Edelbyte domain" until the URL is changed or **Trust cluster host** is enabled for it.

## 0.7.2

- Removed usage analytics (`reportInteraction`, dashboard-load tracking).
- Workload Identity Federation now uses the Edelbyte Go SDK's provider. The plugin no longer reads environment variables or token files itself.
- Health check returns fixed messages (DNS, TLS, connection refused, timeout, authentication) instead of upstream error text.
- OpenAI query generation uses the Grafana SDK HTTP client with the request context, and the response body is no longer closed before it is read. New **OpenAI API key** field in the config editor.
- README and editor disclose the data sent to OpenAI and the Grafana LLM app.
- `grafanaDependency` is now `>=11.6.11`.
- Upstream URLs and error text are logged at Debug level only.
- Removed unused bundled `bridge.js` and `monaco.min.js`, and left the AKS/EKS/EC2 provisioning scripts out of the packaged source.
- Renamed the npm package to `edelbyte-kql-datasource`.

## 0.7.0

- Updated the Edelbyte Go SDK (`api`, `auth`, `query`) from v0.5.5 to v0.7.0.
- KQL editor: completions and error diagnostics now come from the Edelbyte KQL parser, with schema-aware column completion. Grafana variables and macros (`$table`, `$__timeFilter(col)`, `$__timeInterval`) are expanded before parsing so they are not flagged as errors. Synced the tokenizer fix for hyphenated operators (`parse-where`, `project-away`, …) from the Edelbyte KQL editor.
- Query builder: a datetime or timespan filter value that is already a function call (`ago(1h)`, `now()`) is no longer quoted as a string. Arithmetic such as `now() - 1h` is still quoted; see `doc/troubleshooting.md`.
- Config editor: Issuer URL, Client ID and Client Secret are marked required for Client Credentials (OIDC); the Issuer URL placeholder now shows a Microsoft Entra example.
- New plugin logo.
- `provisioning/datasources/aks/dashboards/telemetry.json` uses a `DS_EDELBYTE` datasource variable instead of a hard-coded datasource uid.

## 0.6.1

- Config editor: **Reload databases** now shows a warning when the cluster returns no databases, pointing at the datasource identity's Viewer role.
- Fixed `Rows is not iterable` when the databases response has no rows.

## 0.6.0

- Added the "Trust cluster host" datasource option. When enabled, the host of the configured cluster URL receives the access token even if it is outside the SDK's built-in Edelbyte domains (e.g. a custom domain). Per-query cluster overrides are still checked against the built-in domains.

## 0.5.1

- Bumped `github.com/edelbyte-dev/edelbyte-sdk/go/{auth,api,query}` to v0.5.5. No behavior change here — `awsiam_auth.go`'s `awsIamTransport` still overrides the `Authorization` header itself, since `go/query`'s generated client hardcodes `Bearer` independently of `AccessToken.Scheme`.

## 0.5.0

- Client Credentials (OIDC) auth now delegates to the Edelbyte Go SDK's `auth.NewOIDCTokenProvider` (cached via `auth.NewDefaultTokenManager`) instead of the plugin's own hand-rolled OIDC discovery and token-fetch code.
- Removed the `wifScope`, `oidcScopes`, and `oidcAudience` datasource config fields. Workload Identity Federation and Client Credentials (OIDC) auth now resolve their Entra scope/audience automatically from the cluster's RFC 9728 protected-resource document (`/.well-known/oauth-protected-resource`) instead of requiring it to be configured by hand.
- Bumped `github.com/edelbyte-dev/edelbyte-sdk/go/auth` to v0.5.1.

## 0.4.1

- Forward host env vars (`GF_PLUGINS_FORWARD_HOST_ENV_VARS=edelbyte-datasource`) so AWS IAM Role and WIF auth can reach ambient credentials (task role creds, federated tokens) from the plugin's backend subprocess on Fargate/EKS/AKS.
