Get TFS Webhook SubscriptionStatus - azure

From my previous question link here it appears that we do not have a feature in any version of TFS/Azure DevOps to setup monitoring for the webhook subscriptions.
As a workaround I'm now looking to write a PowerShell script to check the heartbeat of the subscription. From the Microsoft documentation link here it appears we can get the SubscriptionStatus by querying the subscription ID.
On a GET request for below API I receive all the details specified in the documentation but I'm unable to find "status" in the response.
Does anybody know if there is any other way to get the SubscriptionStatus.
https://collectionurl/_apis/hooks/subscriptions/3d9af4ba-d642-4c80-8d62-34cabca322f9

Try listing the subscriptions instead:
GET https://collectionurl/_apis/hooks/subscriptions?api-version=5.1
You can filter the results using query parameters as follows:
GET https://collectionurl/_apis/hooks/subscriptions?publisherId={publisherId}&eventType={eventType}&consumerId={consumerId}&consumerActionId={consumerActionId}&api-version=5.1
You should see status there somewhere.

I found that my API in question is correct, but for some reason i'm not getting 'enabled' status, I tested successfully for all other status mentioned here.
I'm now setting up my PowerShell to execute every 5mins to check the webhook for its status and send an email for any other status than 'enabled'.
If the status is 'enabled' or 'empty' I further check consumerInputs.url to check if the webhook is alive.
This works perfectly fine.

Related

How to Access Talend Cloud Webhook Header

I'm just starting to work with Webhooks in Talend cloud.
how do I access the webhook callback header?
So far I have successfully:
Created a job
Published the artifact to the cloud
configured the environment and engine
invoked the webhook from the command line with curl
Output the payload via the context.resource_webhook_payload variable
I see my problem. I'm still learning API calls and such and Smartsheet API indicated they would send Header attributes.
When in fact this is simply in the payload, not a separate header designation.
Sorry for the naive question.

Demo Docusign Connect Notification "Delivered" is not working

I just have issues with the Connect notification "delivered" from my DocuSign demo account. I'm able to get other notifications like Sent or Completed via Backend and via API. I just tried to get the notification "delivered" via Backend and via API and the log details in the backend shows me this message: "Error loading log details. Try it again."
With other Notifications it shows me the XML with Status sent/completed or something else.
Is this behaviour expected because i just have a demo account? The other notifications like sent and completed seems to work.
This is the message i get if i try to get the notification "delivered".
And this is the message i get if i try to get the notification "sent" or "complete".
Please advise.
If you want a notification of when an envelope has been delivered to an individual recipient, it is better to use the event user.delivered rather than envelope.delivered.
Also, if you're using the default Connect queuing system, delivered statuses can be subsumed by the completed status if it occurs within a minute or so of the delivered status.
To ensure that you always get every notification, use the SIM queuing system. (Select via Admin tool / Updates screen.)
This behaviour is not related to you demo account and you should not see this error.
I tested myself and everything works as expected. Perhaps you can post a screenshot of the error.

Microsoft Graph Security Alerts. Problem with status

I'm having problems with the 'status' field from the Microsoft Graph Security API.
example
GET /graph.microsoft.com/v1.0/security/alerts/03da5d48-a892-4ea6-9949-dc902283e2d8f
Returns status 200 with a JSON object.
The problem is that the alert is 'resolved' in Cloud App Security.
But the API returns "status": "newAlert" on the object.
Does anyone have an idea of what I'm doing wrong?
Docs: link
If you updated the alert status via Cloud App Security portal and then called Get method from the Graph Security API, you should see that the alert status returned from the API reflected as such. If you don't see the status update as expected, then please file a Github issue with details of your issue here.

Updating apns credentials in azure notification hubs causing error in portal

I'm trying to update the existing APNS Credential for my Azure notification hub.
Regardless if I try to upload a new certificate or click "Delete Credential" I get the same error:
Error updating notification hub
{"error":{"message":"Object reference
not set to an instance of an object.","code":"InternalServerError"}}
If I check the developer console in the browser, there's a PATCH request made, where the only parameter is pnsCredential: null.
I've tried multiple browsers and computers with same results.
Thank you for your edit, it is correct: this was a transient issue in the Notification Hubs creation. This is now resolved and we are not expecting that specific issue to happen again.
Thanks, Karl
Updating for anyone else who may find this.
This seems to have been an issue on Azure Portal. It has since been resolved and now works as expected, without any further action on my end.
I did report it to #AzureSupport but have not heard of any action taken by them, so not sure if that is why it was resolved.

Grafana webhooks - failed to send

I'm trying to set up Grafana to send webhooks to Microsoft Teams. I'm able to curl via terminal to the address but it's not possible via Grafanas interface.
I add the URL to Grafanas "webhook" and when I click "Test" it only shows me an error. Anyone know the solution?
I have not entered username/password since i don't know what to supply.
I tried this also.
With a variety of settings (post, put, slack, webhook)
Long story short, Grafana doesn't support the team webhook format.
I Can curl the webhook and get the hello world example to work (without credentials so it isn't the username and password).
Error grafana gives is:
Webhook response status 400 Bad Request
Getting started with connectors
Action reference

Resources