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

Jump to bottom

Azure App Insights Alert error - tsdb.HandleRequest() failed to convert dataframe "" to tsdb.TimeSeriesSlice #26897

Closed
bhozar opened this issue Aug 10, 2020 · 3 comments
Closed

Azure App Insights Alert error - tsdb.HandleRequest() failed to convert dataframe "" to tsdb.TimeSeriesSlice #26897

bhozar opened this issue Aug 10, 2020 · 3 comments
Assignees
@kylebrandt
Labels
add to changelog area/alerting Grafana Alerting
Projects
Backend Platform Backlog
Milestone
7.1.4

Comments

@bhozar
Copy link

bhozar commented Aug 10, 2020

What happened:
Setting up App Insights to alert on metrics throws an error when tested, or in the grafana.log when left setup:
error:"tsdb.HandleRequest() failed to convert dataframe "" to tsdb.TimeSeriesSlice: input frame is not recognized as a time series"

Screenshot of Query:
image

What you expected to happen:
Trigger an alert when the count is higher than X.

Environment:

  • Grafana version: 7.1.3
  • Data source type & version: Azure Application Insights
  • OS Grafana is installed on: Ubuntu 18:04
  • User OS & Browser: Win10/Chrome
@sakjur sakjur added datasource/Azure/Insights needs investigation for unconfirmed bugs. use type/bug for confirmed bugs, even if they "need" more investigating labels Aug 10, 2020
@sakjur sakjur added this to Inbox in Backend Platform Backlog via automation Aug 10, 2020
@kylebrandt kylebrandt self-assigned this Aug 10, 2020
kylebrandt added a commit that referenced this issue Aug 10, 2020
@kylebrandt
dataframe: to tsdb.TimeSeries accept "empty" time series
46b2106 
this is in order to trigger no data when used with alerting.
I currently assume this is cause of issue #26897.
This is perhaps better solved in the SDK but that needs more thought and is tracked in grafana/grafana-plugin-sdk-go#214
@kylebrandt kylebrandt mentioned this issue Aug 10, 2020
Merged
kylebrandt added a commit that referenced this issue Aug 10, 2020
@kylebrandt
fixup! dataframe: to tsdb.TimeSeries accept "empty" time series this …
21d3350 
…is in order to trigger no data when used with alerting. I currently assume this is cause of issue #26897. This is perhaps better solved in the SDK but that needs more thought and is tracked in grafana/grafana-plugin-sdk-go#214

typo fix
@kylebrandt
Copy link
Contributor

I suspect that this from a "no data" state. I was able to replicate this by picking a short query time in the alerting view, and also noticing that these metrics seem to be sparse (in other words no requests/failed, no datapoints). So assuming this is the case, I have created PR #26903 to handle the situation such that alert result will be "no_data" instead of an error.

@kylebrandt kylebrandt added add to changelog area/alerting Grafana Alerting and removed needs investigation for unconfirmed bugs. use type/bug for confirmed bugs, even if they "need" more investigating labels Aug 11, 2020
@kylebrandt kylebrandt added this to the 7.1.4 milestone Aug 11, 2020
Backend Platform Backlog automation moved this from Inbox to Done Aug 12, 2020
aknuds1 pushed a commit that referenced this issue Aug 13, 2020
@kylebrandt @aknuds1
Dataframe/Alerting: to tsdb.TimeSeriesSlice - accept "empty" time ser…
fc66b91 
…ies (#26903)

this is in order to trigger no data when used with alerting.
fixes #26897.

This is perhaps better solved in the SDK but that needs more thought and is tracked in grafana/grafana-plugin-sdk-go#214
@tincann
Copy link

tincann commented Aug 13, 2020 •
edited

@kylebrandt Not sure if this is the right place to comment, but we're also experiencing this same issue with Azure log analytics queries. This makes our alerts basically fire randomly every couple of hours, so I'm very glad it's solved! I'm seeing that it's added to the 7.1.4 milestone. Do you have any idea when this version will be rolled out to Grafana Cloud?

aknuds1 pushed a commit that referenced this issue Aug 14, 2020
@kylebrandt @aknuds1
Dataframe/Alerting: to tsdb.TimeSeriesSlice - accept "empty" time ser…
d005669 
…ies (#26903)

this is in order to trigger no data when used with alerting.
fixes #26897.

This is perhaps better solved in the SDK but that needs more thought and is tracked in grafana/grafana-plugin-sdk-go#214
wbrowne pushed a commit that referenced this issue Aug 20, 2020
@kylebrandt @wbrowne
Dataframe/Alerting: to tsdb.TimeSeriesSlice - accept "empty" time ser…
6eaef8d 
…ies (#26903)

this is in order to trigger no data when used with alerting.
fixes #26897.

This is perhaps better solved in the SDK but that needs more thought and is tracked in grafana/grafana-plugin-sdk-go#214

(cherry picked from commit f432e15)
wbrowne pushed a commit that referenced this issue Aug 20, 2020
@kylebrandt @wbrowne
Dataframe/Alerting: to tsdb.TimeSeriesSlice - accept "empty" time ser…
54f81d2 
…ies (#26903)

this is in order to trigger no data when used with alerting.
fixes #26897.

This is perhaps better solved in the SDK but that needs more thought and is tracked in grafana/grafana-plugin-sdk-go#214

(cherry picked from commit f432e15)
@aknuds1 aknuds1 mentioned this issue Aug 20, 2020
Merged
@StupidScience StupidScience mentioned this issue Feb 8, 2021
Closed
@nanirover
Copy link

I'm experiencing the above error after upgrading the grafana to 7.1.1 using helm, Any thoughts on how we can fix that?
Data source we are using Azure Monitor and App-insights

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@kylebrandt kylebrandt

Labels
add to changelog area/alerting Grafana Alerting
Projects
No open projects
Backend Platform Backlog
Done
Milestone
7.1.4
Development

No branches or pull requests
5 participants
@sakjur @bhozar @tincann @kylebrandt @nanirover