Application Insights: why is data still temporarily inaccessible? - azure

(There doesn't seem to be an option to select Application Insights when reporting a support issue in the Azure portal, hence this post)
For about 12 hours I keep seeing the following error message in the Azure portal when I try and look at Application Insights for a particular App Service:
Data is temporarily inaccessible, see http://aka.ms/aistatus .
That link currently says:
All Application Insights Services are now working as expected.
which is clearly incorrect!
Anyone from the Azure team know what is going on here please? (And why isn't Application Insights available as an option in the drop down list when submitting a support request please?).

For anyone coming across this issue, try disabling your ad-blocker and see if that fixes it.
In my case, Live Metrics would show this error because my ad-blocker was blocking the request.
If anyone from Microsoft/Azure sees this, the "aka.ms" link in the error message just goes to an empty Bing page now. Not sure if it worked previously.

Application Insights should appear in the drop down. Please see picture :)
Application Insights Support Request:

Related

Teams Toolkit: Search based Message Extension not returning Adaptive-Card

I kinda have an issue with the search-based Message Extension.
When I debug locally, my app works fine. After deploying the messaging extension on Azure and testing it in the Teams app, I can search for specific queries. The Message Extension gives me the desired results, up to here we are good to go.
The Problem:
After I select one of the delivered search results, the messaging extension does not return the adaptive card. The chat-box in Teams is simply empty.
Is anyone familiar with this issue?
I cannot reproduce this issue. Can you always reproduce this issue? I think you can retry several more times.
Or copy and paste the codes in bot/teamsBot.js here for troubleshooting.

Logging Exceptions to Slack in Microsoft Azure

I have got a python script that checks if a web-page contains information or if it's empty. I want to make an application that runs this script, and tell me, preferably on slack, whether it worked or not. And I want this to happen every hour. I believe I can do this by using Application Insight with Azure, but I have not found an easy way to do this.
I'm entirely new to azure so any help would be appreciated, even simply links to other pages.
Edit 1
Instead of using python I instead want to try and log the exceptions I find in App insight to slack. I find these exceptions by going to app insight, then "Failures" and then "drill into operations"
Failures in App insight
These Exceptions I want to log to Slack

Azure Application insight not working from UWP device

I have setup the application insights for my app, I can see all the data when I am running my app from the PC, when I am debugging the app running on device, I still see the data in the VS output window and can see "Data from Debug session telemetry" option in Visual studio, but the data from the device is not showing up at app insight portal. Any idea, what might be wrong?
Things to check:
does your UWP app allow outbound network calls? depending on the template/version you started with, the UWP app might not be allowed to send outbound data at all, preventing data from being sent to appinsights.
is it going out at all? use fiddler or something similar (including the extra work to enable it to see traffic from UWP apps, and allow it to decode https) look for outbound calls to dc.services.visualstudio.com
if it is going out, is it being accepted/succeeding? or are the calls failing?
if it is going out, is it using the ikey you expect? so that the data is actually going to the same app you're looking at on the portal
As others have commented, if you want a newer SDK, the hockeyapp.uwp nuget package also allows you to send data to application insights.

Application approval submission failing with "We're sorry. Something went wrong. Please try again later. The backend responded with an error"

I understand this isn't a typically appropriate question for Stack Exchange but the Nest customer service has basically no information whatsoever on developer support, and the Works with Nest support contact form recommends using Stack Exchange tagged with nest-api. Anyway, I have created an application in the developer portal I need to submit for a user limit increase, and I have been unable to submit the form for the last 3 days. I receive a generic error that says:
We're sorry. Something went wrong. Please try again later. The backend responded with an error
As I said, I contacted every customer support outlet Nest offers and have yet to get any assistance. If anyone has encountered this error or has the proper avenue to reach out to Nest's developer support team, please let me know. Thank you in advance, again I apologize for the narrow scope of this question.
If anyone else runs into this issue, my final resolution was to re-create a second application on a different developer account, and then migrate my web service to use the new application's client secret, API tokens etc.. Albeit a huge hassle, the submission (using the exact same form data as before) worked on the new application.

Application Insight works fine localhost but in Azure only client side data

I have a problem with Application Insights that is really similar to this.
Application Insights - Getting only client side data, no server data.
For me however it works fine when i just hit F5 and run the application, i get performance metrics for both client and server side.
However when i deploy the application i dont not get any server side data as far as i can tell. The site runs as a Azure Web App (Web Site). I do get client side data thou.
Anyone have any tips?
Ok, i'm officially an idiot.
I had a Web.Config transformation that was supposed to only replace an attribute in the part of Webconfig but it replaced the entire section. And yeah, now it works hehe. Sorry.
Feel free to remove this post since it was clearly just my code / debugging skill that was lacking.

Resources