Skip to content
This repository has been archived by the owner on Dec 11, 2022. It is now read-only.

Unexpected Message Error in email alert notifications #329

Closed
tmanh17 opened this issue Apr 29, 2021 · 2 comments
Closed

Unexpected Message Error in email alert notifications #329

tmanh17 opened this issue Apr 29, 2021 · 2 comments
Labels
duplicate This issue or pull request already exists

Comments

@tmanh17
Copy link

tmanh17 commented Apr 29, 2021

Bug Report

Get error in email alert notifications:
tsdb.HandleRequest() response error &{json: cannot unmarshal object into Go struct field queryModel.group of type string json: cannot unmarshal object into Go struct field queryModel.group of type string A [] [] 0xc000eaf6b0}

Expected Behavior

Get the abnormal metric name and its value

Actual Behavior

Get the Error message tsdb.HandleRequest() response error &{json: cannot unmarshal object into Go struct field queryModel.group of type string json: cannot unmarshal object into Go struct field queryModel.group of type string A <nil> [] [] 0xc000eaf6b0} instead of the metric name and its value

Steps to Reproduce the Problem

1.create a new dashboard
2.create a panel with BigQuery plugin
3.create a BigQuery query
4.create an email channel and alert to that channel
5.check the email alert notification

image

Specifications

  • Version: 2.0.1
  • Platform: Debian 8.5
  • Grafana Version: Grafana v7.4.2
@tmanh17
Copy link
Author

tmanh17 commented Apr 29, 2021

Some logs

t=2021-04-29T17:06:16+0700 lvl=eror msg="Alert Rule Result Error" logger=alerting.evalContext ruleId=4 name=Alert error="tsdb.HandleRequest() error could not find executor for data source type: doitintl-bigquery-datasource" changing state to=alerting

t=2021-04-29T17:06:30+0700 lvl=eror msg="Alert Rule Result Error" logger=alerting.evalContext ruleId=5 name="Panel Title alert" error="tsdb.HandleRequest() error could not find executor for data source type: doitintl-bigquery-datasource" changing state to=alerting

@ofir5300 ofir5300 added the duplicate This issue or pull request already exists label Apr 29, 2021
@ofir5300
Copy link
Collaborator

Duplication of #301 which is solved by #322
Should work properly on the next plugin release v2.0.2

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
duplicate This issue or pull request already exists
Projects
None yet
Development

No branches or pull requests

2 participants