The open and composable observability and data visualization platform. Visualize metrics, logs, and traces from multiple sources like Prometheus, Loki, Elasticsearch, InfluxDB, Postgres and many more.
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
 
 
 
grafana/docs/sources/developers/plugins/add-support-for-explore-que...

3.6 KiB

+++ title = "Add support for Explore queries" +++

Add support for Explore queries

This guide explains how to improve support for [Explore]({{< relref "../../explore/_index.md" >}}) to an existing data source plugin.

This guide assumes that you're already familiar with how to [Build a data source plugin]({{< relref "/tutorials/build-a-data-source-plugin.md" >}}).

With Explore, users can make ad-hoc queries without the use of a dashboard. This is useful when users want to troubleshoot or to learn more about the data.

Your data source already supports Explore by default, and will use the existing query editor for the data source. If you want to offer extended Explore functionality for your data source however, you can define a Explore-specific query editor.

Add a query editor for Explore

The query editor for Explore is similar to the query editor for the data source itself. In fact, you'll probably reuse the same components for both query editors.

  1. Create a file ExploreQueryEditor.tsx in the src directory of your plugin, with the following content:

    import React from 'react';
    
    import { ExploreQueryFieldProps } from '@grafana/data';
    import { QueryField } from '@grafana/ui';
    import { DataSource } from './DataSource';
    import { MyQuery, MyDataSourceOptions } from './types';
    
    export type Props = ExploreQueryFieldProps<DataSource, MyQuery, MyDataSourceOptions>;
    
    export default (props: Props) => {
      return (
        <h2>My query editor</h2>
      );
    };
    
  2. Configure the plugin to use the ExploreQueryEditor.

    import ExploreQueryEditor from './ExploreQueryEditor';
    
    export const plugin = new DataSourcePlugin<DataSource, MyQuery, MyDataSourceOptions>(DataSource)
      .setConfigEditor(ConfigEditor)
      .setQueryEditor(QueryEditor)
      .setExploreQueryField(ExploreQueryEditor);
    
  3. Add a [QueryField]({{< relref "../../packages_api/ui/queryfield.md" >}}) to ExploreQueryEditor.

    import { QueryField } from '@grafana/ui';
    
    export default (props: Props) => {
      const { query } = props;
    
      const onQueryChange = (value: string, override?: boolean) => {
        const { query, onChange, onRunQuery } = props;
    
        if (onChange) {
          // Update the query whenever the query field changes.
          onChange({ ...query, queryText: value });
    
          // Run the query on Enter.
          if (override && onRunQuery) {
            onRunQuery();
          }
        }
      };
    
      return (
        <QueryField
          portalOrigin="mock-origin"
          onChange={onQueryChange}
          onRunQuery={props.onRunQuery}
          onBlur={props.onBlur}
          query={query.queryText || ''}
          placeholder="Enter a query"
        />
      );
    };
    

Support multiple Explore modes

Explore lets you query any data source, regardless of whether it returns metrics or logs. You can change which type of query you want to make, by setting the Explore mode.

The query modes that the plugin supports are defined in the [plugin.json]({{< relref "metadata.md" >}}) file.

The query mode is available on the props object for both the query editor and the start page. For example, here's how you can change the query editor based on the currently selected mode:

export default (props: Props) => {
  const { query, exploreMode } = props;

  switch (exploreMode) {
    case ExploreMode.Metrics:
      return <MetricsQueryField query={query} />;
    case ExploreMode.Logs:
      return <LogsQueryField query={query} />;
    default:
      return <p>Unsupported mode</p>;
  }
}