Grafana 13.2: Cannot add prometheus as data source - No selection

Grafana
1

Hi All

As title: After installing Grafana 13.2 (download RPM) in KylinOS, I go to “Add data source”, and found NO prometheus. It is completely GONE!

grafana011
grafana0111665×583 55.7 KB

grafana021
grafana0211665×582 35.5 KB

As a result, I cannot add prometheus as data source.

I am sure that in grafana.ini prometheus is not disabled/ban/removed/deleted etc. Grafana and Prometheus are all installed in the same machine.

So, can anyone please help?

Thank you very much.

2

Starting with Grafana v13.2, the Prometheus data source is packaged as a standalone plugin rather than being built into the Grafana codebase. It is still preinstalled, and Grafana normally checks the plugin catalog and installs the latest version on server restart.

Since Prometheus is completely missing from Connections → Add new connection, first check whether the plugin is installed and whether Grafana reported any plugin-related errors:

grafana cli plugins ls
grafana-server -v

If Grafana is running as a systemd service, you can also check:

journalctl -u grafana-server -b | grep -i plugin

If the Prometheus plugin is not listed, try installing it manually:

grafana cli plugins install prometheus
sudo systemctl restart grafana-server

Then check Connections → Add new connection again for Prometheus.

If the installation fails, check whether the KylinOS server can reach the Grafana plugin catalog. Grafana documents CLI installation and alternative installation methods for environments where the plugin catalog cannot be reached.

3

Thanks @infofcc3 . I’ve read the documentation and found the following:

  • In Grafana 13.2, the default plugin directory is /var/lib/grafana/plugins-bundled, not plugins
  • And when I run grafana cli --pluginsDir "/var/lib/grafana/plugins-bundled" plugins install prometheus , it will go to “https://grafana.com/api/plugins/prometheus/versions” to get the version. However, my machine is in a closed network, it cannot go to the Internet to get the version number. So I still cannot install prometheus plugins.

May I ask if there are still any ways to install the plugin? Or I can only just fall back to 13.1 where Grafana and Prometheus “just work”.

Thank you.

By the way, when I download the .deb version of Grafana 13.2, there is no problem selecting Prometheus as data source, it is the .rpm version that causes this trouble.

4

Since the server is in a closed network, grafana cli plugins install prometheus cannot retrieve the plugin metadata from Grafana’s plugin catalog. You can use Grafana’s documented ZIP based installation method for an air-gapped environment instead.

On a machine with Internet access →

Download the Prometheus plugin ZIP for the required version from the official Grafana plugin page.
Transfer the ZIP to the KylinOS server.
Extract it into the plugin directory that your Grafana 13.2 RPM is configured to use.
Make sure the extracted plugin directory is owned by the grafana user.
Restart Grafana and verify that the Prometheus plugin is loaded.

Before changing grafana.ini, I would first verify the actual plugin directory used by this RPM installation, since you’ve already found that Grafana 13.2 is using /var/lib/grafana/plugins-bundled.

You can also check the installed plugins with:

grafana cli plugins ls

If the Prometheus plugin is still missing after the ZIP installation, check the Grafana server log for the plugin-loading error.

The fact that the 13.2 DEB package works in the same closed-network environment while the 13.2 RPM package does not is also important. I would report that difference as part of a Grafana issue, rather than assuming the RPM is definitely defective until the package contents/configuration have been verified.