Mandatory use of Grafana UI components when developing Datasource Plugin?

Grafana Plugin Development
,
1

Greetings,

I am currently developping my own Grafana Datasource Plugin and while I was checking the best practicies on publishing my plugin as a Datasource one, I saw it is preferable (mandatory ?) to use the graphical components from the Grafana UI library.

I quote this line coming from the best practicies for plugin development :slight_smile:
“When building frontend components, make sure to use Grafana components as the base and follow the Saga Design System.”

Will my datasource really be rejected from being published if I’m using, for example, Carbon Design instead of the Saga Design System ?

2

Hey - the advice is for the following reasons:

  • to avoid developers having to author and maintain custom components (faster development)
  • minimise the amount of code needing review (faster publishing)
  • encourage a consistent look and feel across different data sources to simplify the experience for users (faster usage).

It’s not something we’d necessarily reject, but it might depend what you’re actually doing.

3

Hi

Thank you for your fast answer and for clarifying the statement concerning the Grafana components.