I have a .NET Core application deployed to Azure and I setup a healthcheck endpoint.
I noticed my app has been healthy for the most part except on July 19th per this graph:
My questions:
How can I get an alert notification that the app is unhealthy? As of right now, checking my email on that date I didn't get anything.
Are there more details to this activity? Maybe a kusto query I can run to get some more info?
Related
We are trying to use Adjust to measure our ASA campaign result. We have a subscription iOS app. For subscription tracking, they said that we need to add their subscription tracking URL in our AppStore Connect settings where we already have our own server's URL for receiving server-to-server notifications.
If we replace our URL with Adjust's URL, we will stop receiving server to server notifications on our own server.
Can someone guide how you are handling this?
Last year I developed a chatbot with Microsoft Bot Framework that I integrated in the Facebook Messenger of a page. Everything worked fine until 16th of December (last successful log). The page is not used by a lot of people therefore the application might have worked also longer than that.
Today I tried to use the chatbot again and I did not get any response. In the Logs I just found the error message "Operation returned an invalid status code 'Forbidden`".
After a bit of Debugging I found out that the problem is sending messages back to the Facebook Messenger.
context.SendActivityAsync(...)
I did not change any configuration within my Azure Bot Channel registration recently. I am aware of the privacy changes within the Facebook API, but as I already struggle with sending a simple text response like "Hi" I assume that cannot be the problem. Also the permission scheme has changed for Facebook apps. I have the permission for "pages_messaging". Do I need another permission now? Or did I miss another change in the Facebook API?
Technical Details:
Facebook API Version v6 (tried also v9 but no change in behavior)
Chatbot based on .Net Core 2.1
Bot Builder SDK v 4.11
Any hints what I did wrong or where I can look for further information is much appreciated.
Edit: I tried to add a new page to my Facebook App and get following message:
There is a hint that a permission is missing, but I cannot find out which one I require. As I only send responses to FAQ's and if required handover to the customer service inbox I just requested the "pages_messaging" permission. Do I require any other permission now?
I found the problem. For everyone that might have the same problem:
In our case the administrator that added the Facebook pages to the application was removed from the admin permission list of the pages. After re-adding the admin permissions for the pages the bot started working again.
I am developing and testing a local service fabric cluster in a 5-node environment.
I used Microsoft.AspNetCore.Identity.
However, if I try to sign-in, I get not signed-in page of 4/5 chance.
I've looked at the documentation and tried several things, but it still does not work.
(ex. AddIdentity, UseAuthentication, AddDistributedRedisCache, AddSession, UseSession)
What is the simplest way to share a user's authentication status via Redis Session when use Microsoft.AspNetCore.Identity?
Up to this point, I had a functioning Azure Mobile Service with service-directed OAuth working nicely for Google. I tried to rehost the mobile service as an app service since mobile services are deprecated. I also have an HTML/JS web app that accesses my service through the MobileServiceClient JS client. This is where the fun starts.
After changing the redirect address to the appropriate app service address in the Google API manager, I get a message saying I'm successfully logged in in a new popup window: .
Clicking on "Return to Website" takes me to the address of my app service, not the app that initiated the OAuth request, and if I close this window, the MobileServiceClient throws a "cancelled" exception and I don't get my credentials.
What am I missing or what changed that I need to account for?
Thanks!
It turns out that this particular behavior happens when using an older version of the MobileServiceClient JS library. Replacing the 1.2.7 version with the 2.0.0beta version fixed this. To get the whole OAuth flow working, I also needed to add the appropriate addresses to the allowedExternalRedirectUrls node of the config/authsettings node through the Azure Resource Explorer. If there is a nicer way to do it than through the resource explorer, I don't know what it is.
I have android app like twitter. I want a push notification on User1 app when User2 follows User1.
I have AWS (dynamodb) as backend and integrated with GCM. I am able to publish message from AWS sns console manually also. But i want norification to be sent automatically when someone follows other guy. Right now my app directly talks with DynamoDB there is no server in between.
I want to know to publish notification programatically should i write server where i should make a call to update DynamoDB (instead of directly updating it) and publish message to GCM. OR User1's app itself should publish a message for User2 ?
I need to know very urgently.. I could not find any explanation of that sort anywhere.
Thanks in advance.
You should implement a backend server and your app only communicates with your server.
Your app requests to your server to send a message to another user, and the server is responsible to update in the DynamoDB and tell SNS to send a push.
Hope it helps.