dotnet
Staging - [Alerting] Test Reporting Services Monitoring alert
:broken_heart: Metric state changed to alerting
Hey FR! The Dev WF team should be on top of these alerts until we hand it off.
(When we have engineering documentation, we should add it here, until then, contact one of the v-team members for the Dev WF epic to help investigate).
- AzureDevOpsTestAggregation Exceptions 1
@dotnet/dnceng, please investigate
Automation information below, do not change
Grafana-Automated-Alert-Id-fcb554ece9d8452a98c1e18d3ffb8fe8
![dotnet-eng-status-staging[bot] avatar](https://avatars.githubusercontent.com/in/45907?v=4 "Published by a pub.dev verified publisher"){kind=small}
:green_heart: Metric state changed to ok
Hey FR! The Dev WF team should be on top of these alerts until we hand it off.
(When we have engineering documentation, we should add it here, until then, contact one of the v-team members for the Dev WF epic to help investigate).
:broken_heart: Metric state changed to alerting
Hey FR! The Dev WF team should be on top of these alerts until we hand it off.
(When we have engineering documentation, we should add it here, until then, contact one of the v-team members for the Dev WF epic to help investigate).
- AzureDevOpsTestAggregation Exceptions 2
:green_heart: Metric state changed to ok
Hey FR! The Dev WF team should be on top of these alerts until we hand it off.
(When we have engineering documentation, we should add it here, until then, contact one of the v-team members for the Dev WF epic to help investigate).
Looks like a ton of generic: "An error occurred while sending the request."
The only thing that looks interesting is: "Kusto client timed-out when sending a request to the service. "
Filed an IcM with Kusto per the instructions on the error we got from them in the logs :)
https://portal.microsofticm.com/imp/v3/incidents/details/333064319/home
@garath I'm assuming you want to know what I did to find the errors? I generally look at this panel to see what's going on with the service that was erroring: https://dotnet-eng-grafana-staging.westus2.cloudapp.azure.com/d/buildAnalysis/build-analysis?viewPanel=51
Kusto team closed the IcM I created with this feedback:
Cluster is healthy, this query has been executed for an hour hence the query has been timeout, please review your query and adjust it accordingly.
So, we need to investigate what caused that query to run for so long.
:broken_heart: Metric state changed to alerting
Hey FR! The Dev WF team should be on top of these alerts until we hand it off.
(When we have engineering documentation, we should add it here, until then, contact one of the v-team members for the Dev WF epic to help investigate).
- AzureDevOpsTestAggregation Exceptions 1
:green_heart: Metric state changed to ok
Hey FR! The Dev WF team should be on top of these alerts until we hand it off.
(When we have engineering documentation, we should add it here, until then, contact one of the v-team members for the Dev WF epic to help investigate).
:broken_heart: Metric state changed to alerting
Hey FR! The Dev WF team should be on top of these alerts until we hand it off.
(When we have engineering documentation, we should add it here, until then, contact one of the v-team members for the Dev WF epic to help investigate).
- AzureDevOpsTestAggregation Exceptions 1
:green_heart: Metric state changed to ok
Hey FR! The Dev WF team should be on top of these alerts until we hand it off.
(When we have engineering documentation, we should add it here, until then, contact one of the v-team members for the Dev WF epic to help investigate).
:broken_heart: Metric state changed to alerting
Hey FR! The Dev WF team should be on top of these alerts until we hand it off.
(When we have engineering documentation, we should add it here, until then, contact one of the v-team members for the Dev WF epic to help investigate).
- AzureDevOpsTestAggregation Exceptions 1
:green_heart: Metric state changed to ok
Hey FR! The Dev WF team should be on top of these alerts until we hand it off.
(When we have engineering documentation, we should add it here, until then, contact one of the v-team members for the Dev WF epic to help investigate).
:broken_heart: Metric state changed to alerting
Hey FR! The Dev WF team should be on top of these alerts until we hand it off.
(When we have engineering documentation, we should add it here, until then, contact one of the v-team members for the Dev WF epic to help investigate).
- AzureDevOpsTestAggregation Exceptions 1
:green_heart: Metric state changed to ok
Hey FR! The Dev WF team should be on top of these alerts until we hand it off.
(When we have engineering documentation, we should add it here, until then, contact one of the v-team members for the Dev WF epic to help investigate).
:broken_heart: Metric state changed to alerting
Hey FR! The Dev WF team should be on top of these alerts until we hand it off.
(When we have engineering documentation, we should add it here, until then, contact one of the v-team members for the Dev WF epic to help investigate).
- AzureDevOpsTestAggregation Exceptions 1
:green_heart: Metric state changed to ok
Hey FR! The Dev WF team should be on top of these alerts until we hand it off.
(When we have engineering documentation, we should add it here, until then, contact one of the v-team members for the Dev WF epic to help investigate).
:broken_heart: Metric state changed to alerting
Hey FR! The Dev WF team should be on top of these alerts until we hand it off.
(When we have engineering documentation, we should add it here, until then, contact one of the v-team members for the Dev WF epic to help investigate).
- TestDataAggregationService Exceptions 1
- AzureDevOpsTestAggregation Exceptions 1
:green_heart: Metric state changed to ok
Hey FR! The Dev WF team should be on top of these alerts until we hand it off.
(When we have engineering documentation, we should add it here, until then, contact one of the v-team members for the Dev WF epic to help investigate).
:broken_heart: Metric state changed to alerting
Hey FR! The Dev WF team should be on top of these alerts until we hand it off.
(When we have engineering documentation, we should add it here, until then, contact one of the v-team members for the Dev WF epic to help investigate).
- AzureDevOpsTestAggregation Exceptions 1
:green_heart: Metric state changed to ok
Hey FR! The Dev WF team should be on top of these alerts until we hand it off.
(When we have engineering documentation, we should add it here, until then, contact one of the v-team members for the Dev WF epic to help investigate).
:broken_heart: Metric state changed to alerting
Hey FR! The Dev WF team should be on top of these alerts until we hand it off.
(When we have engineering documentation, we should add it here, until then, contact one of the v-team members for the Dev WF epic to help investigate).
- AzureDevOpsTestAggregation Exceptions 1
:green_heart: Metric state changed to ok
Hey FR! The Dev WF team should be on top of these alerts until we hand it off.
(When we have engineering documentation, we should add it here, until then, contact one of the v-team members for the Dev WF epic to help investigate).
:broken_heart: Metric state changed to alerting
Hey FR! The Dev WF team should be on top of these alerts until we hand it off.
(When we have engineering documentation, we should add it here, until then, contact one of the v-team members for the Dev WF epic to help investigate).
- AzureDevOpsTestAggregation Exceptions 1
:green_heart: Metric state changed to ok
Hey FR! The Dev WF team should be on top of these alerts until we hand it off.
(When we have engineering documentation, we should add it here, until then, contact one of the v-team members for the Dev WF epic to help investigate).
