Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

OpenSearch Plugin in Grafana Uses Old _opendistro Endpoint for PPL, Resulting in 400 Bad Request Error #499

Closed
Alexadra opened this issue Nov 8, 2024 · 1 comment · Fixed by #502
Assignees

Comments

@Alexadra
Copy link

Alexadra commented Nov 8, 2024

When attempting to run PPL (Piped Processing Language) queries in Grafana using the OpenSearch plugin, the plugin defaults to using the old Open Distro endpoint (/_opendistro/_ppl). This endpoint results in a 400 Bad Request error because OpenSearch has transitioned to using the newer _plugins folder for PPL queries (/_plugins/_ppl).

Steps to Reproduce:

  1. Install and configure the latest version of OpenSearch and ensure the SQL/PPL plugin is installed and enabled.
  2. Set up Grafana and configure an OpenSearch data source.
  3. Attempt to run a PPL query in Grafana, such as:
    source=test | where SampleLabel is not null | stats avg(ResponseTime) by SampleLabel
  4. Observe the request sent by Grafana to the OpenSearch instance.

Expected Result:

Grafana should send the request to the endpoint: http://opensearch-node1:9200/_plugins/_ppl.

Opensearch version 2.18.0
Opensearch plugin version 2.21.2

@Alexadra Alexadra added datasource/OpenSearch type/bug Something isn't working labels Nov 8, 2024
@github-project-automation github-project-automation bot moved this to Incoming in AWS Datasources Nov 8, 2024
@iwysiu iwysiu self-assigned this Nov 12, 2024
@iwysiu iwysiu moved this from Incoming to In Progress in AWS Datasources Nov 12, 2024
@github-project-automation github-project-automation bot moved this from In Progress to Done in AWS Datasources Nov 13, 2024
@iwysiu
Copy link
Contributor

iwysiu commented Nov 13, 2024

Hi @Alexadra ! Thanks for the bug report, I've updated the endpoint and it should be fixed in the next release

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Done
Development

Successfully merging a pull request may close this issue.

2 participants