I have a REST API running on an Azure server. I turned on Application Logging to "verbose". I can now see all my request coming in, but I can't see the HTTP headers sent by the client. I know they're there, because my code receives them. I tried looking at both the the Application and Web server logs under "Log stream" - not there.
Am I looking at the wrong place? Missing a setting? Is this an authorization issue?
Where can I find my custom HTTP headers in Azure logs?
It seems that this feature is still on the backlog but with no concrete ETA. You may upvote the feature request and keep a watch on for the update.
Related
The Microsoft documentation states:
Provide a notification endpoint URL: In the Notification Endpoint URL
box, provide an HTTPS Webhook endpoint to receive notifications about
all CRUD operations on managed application instances of this plan
version.
I created a simple Logic App and copied the HTTP endpoint into my MPN App Plan under the
It looks like this and has the sig at the end:
https://prod-08.australiaeast.logic.azure.com:443/workflows/fe287d1b9a8c48619a1b44765dad6dc7/triggers/manual/paths/invoke?api-version=2016-10-01&sp=%2Ftriggers%2Fmanual%2Frun&sv=1.0&sig=C9JYfNPjvq-efsLwW66A4K4zTgx6qxGT1oH0RZZRsI0
To test it I hit it with PostMan and confirm that it is getting an HTTP200 as per the MS Docs.
I publish the app to the marketplace:
(you can see the app live here - https://azuremarketplace.microsoft.com/en-us/marketplace/apps/data-drivenai1581501556049.cloudmonitor-analytics-engine)
However - the endpoint never gets called at all. I can see in the logs that no attempt (failed or past) has been made to call it.
I raised a Microsoft Support Ticket and asked a Technical Specialist, however no one can tell me how to debug it or why it is not calling back on installs or failed installs.
Has anyone seen this working?
Update
I found out that each PLAN has a GUID that is automatically used for deployment. Mine is "pid-34881ea9-xxxx--xxxx-xxxx-2cf731e06ef7-partnercenter" - should I be putting this on the callback notification URL as sig=ThisGUID?
In the example for Managed apps with notifications, it shows that managed applications will send a post to https://{your_endpoint_URI}/resource. Can you try adding /resource to your listener and see if it triggers your logic app? I believe that should fix this.
I hosted a web API on azure app service using a docker image (linux)
And for production purpose I need all http requests to be logged.
I tried " Diagnostic settings (preview)" and I selected "Archive to a storage account"
, But when I checked my logs I found all http request data except request & response body and header.
So, is there a way to log this details for debugging purpose.
Thanks in advance.
You won't get the response body and header values in the AppServiceHTTPLogs. You can find the description of the log over at https://learn.microsoft.com/en-us/azure/azure-monitor/reference/tables/appservicehttplogs.
The feature; however, is still in preview though so that means you can submit feedback asking to include the body and header values.
I want to implement event notification webhook method into my app. I am using docusign-java-client SDK for docusign, but I am unable to find any example using SDK. Can anyone provide some example to achieve this?
I'm sorry to report that we (DocuSign) don't yet have a Java recipe for this. We do have a Python example. Java is on the list of things to do. Perhaps someone else can provide an example in the meantime.
Here is a general description:
First, set up your webhook subscription. You can have an envelope-specific webhook subscription by including the eventNotification fields in your envelope create request.
Or you can set up a more general subscription by using the "Connect" feature. You can setup Connect subscriptions either via the DocuSign web tool, or programmatically.
As part of the subscription you provide your url for the incoming XML notification messages.
To handle them, you write a small web app using whatever web app framework is easiest for you and your stack. Your web server will receive the incoming https calls from DocuSign.
You can see what the incoming XML messages look like by using the beta Recipe Framework. Run it on Heroku. Use the embedded signing recipe and click the button to see the Webhook / Connect messages. You can then see the sorts of messages that you will receive.
Your incoming message web server will simply parse the XML messages and then handle them accordingly.
Thanks for using the webhook system. Please ask more questions here if you have any issues.
I am using the DocuSign Rest API v2. During envelope creation process, we will send our rest API URL to receive the notifications.
The events are properly receiving in our live setup. But in our local development setup we are not receiving the notifications.
For this, we have whitelisted the IP ranges mentioned in the DocuSign Page on our side.
https://trust.docusign.com/en-us/trust-certifications/ip-ranges/
But still, we are not receiving notifications to the development setup.
What else we need to do to get this done?
Unfortunately I'm unable to respond to the original post, however I've experienced the same issue (reported here). It only appears to occur when envelopes are sent as far as I can tell, and I'm able to retrieve the status afterwards - but it's not in line with what the API guide tells us, nor what was happening previously.
I registered for Evernote webhook successfully with a valid end point recently. But whenever I make any changes to my evernote account, either by creating or updating a note, I am not being notified by the webhook. I am using a page created with http://requestb.in/ as an endpoint but I don't see evernote making any requests to it. I have reached out to Evernote support but haven't received a response yet.
How do you test to see if Evernote Webhook is working as expected?
The easiest way is to check the web logs of the web server you've set up to receive them.
I have a couple of web hooks set up and they seem to work. I've used a node.js app to receive the webhooks.
Double-check that you asked for the right kinds of notifications? What filter did you ask for?
Other than double-checking the URL you gave them, and double-checking the logs, and if using https ensuring you are using a valid certificate, there isn't much else other than waiting for the support response.
In the meantime you can test your code by hitting your webhook server with appropriately formatted URLs.