Is there a posibilities using an automation script that can generate an outbound payload even the event listener from publish channel is disabled?
I'm trying to create a automation script that can generate payload with disabled event listener from publish channel, but I don't have idea how to do it.
Related
I have a node.js server running on an Azure app service. I would like to receive an automated email notification in the event that the node app crashes. I've been Googling and there seem to be so many options around monitoring provided by Azure, that it's quite overwhelming. I looked at Azure Application Insights, but couldn't see the functionality I'm after + it seems expensive.
Is there a simple Azure approach for monitoring node.js app crashes, or a free third party solution which would do it?
If you are looking for receiving an email notification when your node.js app crashes or when returning Http 5XX status code, You can use azure monitor alert and then setting email notification in the action group.
Go to your Azure portal and navigate to your app service's page> under Monitoring click on Alerts blade> create new alert rule and add condition> Select signal type Http Server Errors.
Now set Thresholds as required> then under "Actions", click on the "Add action group" button and create a new action group that includes your email address as a notification receiver> Save the alert rule.
Then go your action group's page and click on the "Add action" button and select "Email/SMS/Push/Voice" as the action type> add email address details> Save the action group.
Additionally you may also refer to this document for setting threshold and understanding metrics: https://learn.microsoft.com/en-us/azure/app-service/web-sites-monitor
I am doing my final year project Using Azure Cloud. I have connected my raspberry pi where I have deployed my python code to trigger the device connected to its GPIO pins. These pins are triggered by "Azure-iot-Hub direct method call". How can I integrate this thing in website? I want to create a button on website and every time when I will press this button the direct method should be called. Is there any way to do this?
Unless creating website is in the scope of project, the easiest option is to use IoT Central, create a device template with associated telemetry, properties and commands.
If creating a custom website, wire the direct method IoT Hub Rest API to your application web page. https://learn.microsoft.com/en-us/rest/api/iothub/service/devices/invoke-method
or use the nodejs service client https://github.com/Azure/azure-iot-sdk-node/blob/main/service/samples/javascript/invoke_command.js
Depending on what web stack you are using, the appropriate SDK can be used (nodejs, python, c#, c or java)
As part of our production environment we have several App Services running inside of Azure. I would like to implement notifications to be sent to a specific email address upon file or configuration changes within those App Services. I have tried enabling Application Changes for the service but it does not appear to provide the capability to set up alerts on the changes,
I have also tried enabling App Service alerts but it does not appear that any of the test configuration changes that I have made were captured by the signal "Apply Web App Configuration".
The last thing that I tried was to enable Diagnostic Settings to capture AppServicePlatformLogs and AppServiceFileAuditLogs and stream them to an Event Hub, however, I cannot determine how to set up the email notification from the hub for the events.
I am hoping that there may be an easier way to set this up and was hoping that someone may have some pointers or resources that I can follow.
I was able to accomplish this under "Monitoring" -> "Alerts". A more detailed walkthrough can be found here https://perituza.com/blog/azure-app-service-monitoring-and-alerts/. The key was selecting "Activity Log - Administrative" as the Monitor Service in the Condition.
I've got an Azure Logic App that I want to run whenever a file is uploaded to a specific Azure Storage Account. The Logic App is deployed via an ARM template (which has also been configured to create the Event Grid and Blob Storage API connections).
When I deploy the ARM template, the Event Grid trigger isn't working as there's no event subscription in the Azure Storage Account.
FYI., I can get event subscriptions to work if I create a Logic App via the quick start option i.e. from my Azure Storage Account under Events > Get Started > Logic Apps > When a new blob is uploaded > Create.
^^ This creates a new Logic App with an Azure Event Grid trigger (When a resource event occurs), but I actually want to create/link the event subscription to an existing Logic App i.e. the one that I deployed via the ARM template, and I want to be able to automate this.
If I reverse engineer the event subscription that was created by the Logic App quick start; I can see it's got an endpoint type of WebHook with an endpoint of the form {logic-app-access-endpoint}/triggers/{name-of-trigger}/versions/{logic-app-version}/run. I can reconstruct this to something like the following by getting the params from my Logic App:
https://prod-24.australiaeast.logic.azure.com:443/workflows/12433cc68f0e916dc3048c1775333506/triggers/When_blah_blah_blah/versions/12345678901234567890/run
I can enter the Subscriber Endpoint and Confirm Selection, but when I try to create it; I'm getting the following error:
Deploying Event Subscription: Test123
Deployment has failed with the following error: {"code":"Url validation","message":"The attempt to validate the provided endpoint https://prod-24.australiaeast.logic.azure.com:443/workflows/12433cc68f0e916dc3048c1775333506/triggers/When_blah_blah_blah/versions/12345678901234567890/run failed. For more details, visit https://aka.ms/esvalidation."
What's strange is if I go into my logic app and change the event grid connection to a different one (but with the exact same properties) and then save my logic app; I can then create my event grid subscription without the error. It seems a bit temperamental...
I've tried a few things such as authorizing my event grid API connection, but it doesn't work...
Does anyone know if how set up event grid subscriptions to an existing Logic App without the errors / temperamental behavior... also how would one go about automating the creation of the event grid subscriptions (given there's some dynamic properties such as the logic app version).
TIA - Ryan.
It looks like your Logic App trigger endpoint is a bit off. It should look something like this:
https://prod-24.australiaeast.logic.azure.com:443/workflows/12433cc68f0e916dc3048c1775333506/triggers/When_blah_blah_blah/paths/invoke?api-version=2016-10-01&sp=%2Ftriggers% When_blah_blah_blah%2Frun&sv=1.0&sig=1234567890abcdefghij
You can find the exact value by clicking See trigger history from your Logic App overview blade.
From the ARM template automated deployment standpoint, you can get the trigger endpoint using the following code:
[listCallbackUrl(concat(resourceId('Microsoft.Logic/workflows',variables('myLogicAppName')),'/triggers/When_blah_blah_blah'), '2016-10-01').value]
I highly recommend either deploying your Logic App and Event Grid subscriptions together or adding a "Logic App was changed" trigger to your Event Grid subscription deployment. You'll need this in case your Logic App trigger endpoint changes which should only happen at deployment time (friends don't let friends save in the portal).
I have a requirement where I need to create Remote Event Receivers for SharePoint Online list because Event Receivers were used in SharePoint 2010 version.
According to various sources and examples, it seems that Provider Hosted Add-In is the way to create Remote Event Receivers which requires Azure Access Control Service (ACS).
As Azure Access Control Service (ACS) is about to be deprecated, is there any other way to create Remote Event Receivers for SharePoint Online list?
Currently, SharePoint Online Remote Event Receiver still necessary to use Azure Access Control Service and it is still available now until Nov 7 2018.
In the future, after ACS deprecated, I think Microsoft will have alternative way to handle Remote Event Receiver for SharePoint Online, but now please still use ACS.