Description

It'd be great if there was an official ARM64 build of this plugin, please?

What happened?

{"message":"id is invalid","traceID":""}

Description

Currently we only support http for serviceMap it would be nice to also support TCP.
Probably need to figure out how to handle mixmode.

Description

Was originally: grafana/grafana-plugin-repository#1043

It's now a submitted through the grafana cloud portal.

Description

I found problem: when grafana send api-request on Kuma Control Plane API in kuma-mesh with hundreds dataplanes, it get only 100 first sorted alphabetically services (Kuma API pagination):

curl 10.0.3.1:5681/meshes/default/service-insights

response:

{
 "total": 325,
 "items": [..]
 ],
 "next": "http://10.0.3.1:5681/meshes/default/service-insights?offset=100"
}

Accordingly, the Mesh Map in grafana almost does not work, as there are not enough relationships to form it.
kuma doc says that pagination works on 1000 elements (default - 1000).

If the implementation of pagination takes time, then you can make a fix, just add a parameter like ?size=1000
I think this simple "crutch" will not affect the work, since now the service map does not work in large mesh networks anyway.

Description

The plugin seems to use a deprecated API, see

https://grafana.com/docs/grafana/latest/developers/http_api/data_source/#data-source-proxy-calls-by-id

The recommended API uses UID instead of ID.

Any schedule to support Grafana 9.x?

Description

We now have a plugin that's versioned and distributed.

It would be good to have the dashboards from: https://github.com/kumahq/kuma/tree/master/app/kumactl/data/install/k8s/metrics/grafana packaged in the plugin instead.
Once this is done we can version these separately from the Kuma and only publish updates when needed.

Description

test

Description

Docker containers are easier to download from anywhere.

Description

Upon inspecting the plugin code, specifically in src/datasource.ts at:
https://github.com/kumahq/kuma-grafana-datasource/tree/master

In the meshGraphQuery method of the DataSource class, there's this segment:

typescript

let interval = (request.intervalMs - (request.intervalMs % 60000)) / 60000;
if (interval === 0) {
interval = 1;
}

I believe this code determines the time interval for the queries sent to Prometheus. The current behavior seems to round it to the nearest minute and defaults to 1 minute if the interval is zero.

Feature Requests:

User Configurable Time Intervals: Allow users to configure the time interval instead of it being fixed. This ensures that users can set the interval based on their specific needs.

Avoid Blank Data Display: Alter the plugin behavior so that even if there's no traffic, it doesn't display blank data. The service map should provide some context or default view rather than appearing empty.

Potential Solutions:

Introduce a configuration setting in the plugin settings where users can specify their desired interval.
Incorporate a fallback visualization or a message indicating "No traffic data" rather than showing an empty graph, giving users a clearer indication of the situation.

Benefits:

Enhanced user customization leading to a more personalized experience.
Improved UX by ensuring users are not met with blank, uninformative screens.