In the last 24 hours I've attempted promotions twice now for a single DialogFlow agent, when I show "All versions" from the Environments tab, the two most recent deployments are still showing a status of "Deploying".
I've tried to repromote.
There is no code involved.
When I request the promotion of a trained agent, I expect the promotion to complete; in this case, the promotion "appears" to complete successfully, however, when I check the "All versions" page, it shows both of the last two promotions as still "Deploying".
Long running deployments
Related
We are using Application Insights by Azure. At the moment I have to manually check the exceptions after each deployment to see if a new one appeared. Has anyone figured out a way to get notified (via Azure alert) once a new exception appears? For example, other error trackers like Sentry support this.
Example:
We did a deployment at 15:15
A previously unknown exception appears at 15:17
An email is sent to me with content "New exception X appeared in project Y"
Here is a screenshot demonstrating this a bit more clearly:
Smart detections are being replaced by alets. The only way to get notifications is to write a query that will see your new exceptions. Configure the period to let alerts activate.
Navigate to the Application insights resource on Azure Portal.
Select Logs under the Monitoring blade.
Construct your log query and check the results.
Click on + New alert rule.
Configure your alert as follows:
The above alert fires whenever the count of results in Custom log search log query for the last 1 day is greater than 0, and is evaluated every 6 hours. You can customize the Period and frequency as needed.
You can also run through this detailed guide for troubleshooting problems with Azure Monitor alerts. Please check if this helps.
You can try Smart Detection, specifically the alert for abnormal rise in exception volume.
When would I get this type of smart detection notification?
You get this type of notification if your app is showing an abnormal rise in the number of exceptions of a specific type, during a day. This number is compared to a baseline calculated over the previous seven days. Machine learning algorithms are used for detecting the rise in exception count, while taking into account a natural growth in your application usage.
If you never got a specificy exception before a release, I would consider that a rise in exceptions for that type and you should get an alert. Though the alert won't happen if there are very few exceptions occuring, and it won't be as detailed as you described in your question.
OK, so I simply want to create an alert, for when my URL is unreachable.
As a test, I followed the steps found here to create an availability test for https://www.google.com, and as success criteria, I put 500 as my HTTP response; it was felt that this will trigger an alert.
The action group that I created is an MS Teams group; this is working, I know this because it is used by different alerts. Then, I created a new Alert, with the Condition of my newly created availability test, then I waited.
I expected to get an alert upon failure of my test. I can see that the test is failing, but there is no alert. What might I [not be grasping/be doing wrong]?
Turns out I must have mistyped something. All I know is that doing it from scratch (for the 3rd time) fixed it.
I've established an email alert inside azure. This alert listens to the response times of a specific azue function. If the average response time exceeds a threshold (e.g. 300ms), then the alert will be triggered and an email will be sent. If the average response time falls below the threshold a couple of minutes later, then a second email will be sent ("alert resolved")
Furthermore I established a suppress condition which suppresses the alert at night.
I've noticed that the second resolve-mail will still be sent at night (when the suppress condition is active). The first trigger-mail will not be send at night anymore.
I want that the second resolve-email will also be really suppressed at night. Does anybody have an idea?
The ideal way to suppress notifications for your alerts would be to use the Action Rules feature, which is currently in preview.
The best part about action rules is that you can define them at any scope: at the subscription, resource group, or individual resource level, with other available filters. While all actions and notifications on the selected scope and filters will be suppressed for the time period configured, alerts will continue to monitor.
As an example, the following action rule is configured to suppress alert notifications from 7 PM - 7AM every day.
Please give it a try and see if it fits your need. More about this here. Hope this helps!
How to schedule an email newsletter? Documentation seems to missing that. I have newsletter with widget that will take news from last 2 weeks. I would like to automatically send that newsletter every 2 weeks.
Kentico 11
Re-sending newsletters based on some interval (e.g every week) is not supported in Kentico at this time. It is possible through some customization, however.
By scheduling a newsletter to be sent at some time in the future, a scheduled task is created in the Scheduled Tasks application (under your site > System Tasks). This task only runs once and is then deleted, but you can alter the configuration of the task to run periodically and not delete itself. Or, you can manually create a task that uses CMS.Newsletters.QueueSender and TaskData equal to the issue's GUID.
There is another issue to solve once the task has been scheduled to run periodically- the issue's IssueStatus will be changed to Finished (5) after it is sent the first time, but the QueueSender will only re-send the issue if the status is ReadyForSending (1).
You can use an object event handler or custom scheduled task to automatically change the IssueStatus to 1 before the issue is sent once again.
Seeing if anyone else has had this problem and a resolution to it.
I have a visual studio sequential workflow on a list (not a library) which does NOT use tasks, the approval process is done through the Approve/Reject OOTB buttons on the list item. The approval is a 2 stage approval, whereby if the 1st stage is completed (via clicking the Approve OOTB button), i reset the ModerationInformation.Status from Approved back to pending then send an email to the 2nd stage approver.
My problem is, when i set the the ModerationInformation.Status back to Pending from Approved so there is never an approved version, the Creator loses permissions to view the item, and i get the "cannot find item" error from SharePoint for the person who created the item. The 1st and 2nd level approvers and anyone with approve rights CAN still see the item.
Some more background information. the code i am using to update the moderationinformation is
I get the properties from the workflow event and get a hook into the listitem
properties.Item.ModerationInformation.Status = SPModerationStatusType.Pending;
properties.Item.Update();
can anyone help.
Try using properties.Item.SystemUpdate(); this prevents SHarePoint from triggering any attached EventReceivers etc. I've had the same thing happen also. IMHO this is related to the fact that the item goes into update mode, then SharePoint basically has taken control over the item (seeing as workflows are usually run as the System account) but still sends you back to the the return url (i.e. the EditItem page of the list).
Since SharePoint is probably still doing work on the item (and when you use item.Update() it goes through all events etc. etc.) you cannot open it anymore, because you are not the system account.
When SharePoint finishes (after sent the emails etc.) the item is accessible by users again.
Like I said, I had the same thing happen during long running (i.e. longer than 2 to 3 seconds) EventReceivers / Workflows.