Monitor Cognitive Services Flashcards
AZ cognitive services enables you to integrate artificial intelligence in dual applications and services.
It is important to be able to monitor cognitive services in order to track utilisation determine trends and detect and troubleshoot issues
AZ cognitive services provides a cloud-based platform for building artificial intelligence capabilities into applications.
Like any software service you should monitor cognitive services to track costs identify utilisation trends and detect potential issues.
Monitor cast:
One of the main benefits of using cloud-based services that you can cost efficiencies for only paying for the services as you use them.
So I’m cognitive services resources off of a three-tier with restrictions on use which is useful for development and testing; and one or more bull terriers that incurred charges based on transactions will stop the specific billing rate depends on the resource type.
Plan costs for cognitive services:
Before deploying a solution that depends on cognitive services you can estimate costs by using the AZ pricing calculator.
Do use the pricing calculator to estimate cognitive services costs create a new estimate and select a z cognitive services in the AI + machine learning category.
Then select the specific cognitive service API you plan to use for example text Analytics the region where he planned to provision it and the pricing tier of the Instance you plan to use semicolon and fill in the expected usage metrics and support option.
To create an estimate that includes multiple cognitive service api’s add additional AZ cognitive services products to the estimate
View costs for cognitive services kerala
In common with the AG resources UK and view details of accumulated cost for cognitive services resources in the agportal turn on new line to view costs or cognitive services sign into the AZ portal and select your subscription. You can then view overall cost for the subscription by selecting the cost analysis stub. Give you only costs for cognitive services and a filter that restrict the dogs to reflect resources with the same name of AZ cognitive services
Create alerts kola
Microsoft AZ provides alerting support for resources through the creation of alert rules.
You can use alert rules to configure notifications and alerts for your resources based on events or metric thresholds will stop these alerts will ensure that the correct team knows when a problem arises.
Alert rules colour new line to create an alert rule for a cognitive service resource select The resource in the AZ portal and on the alert stab at a new alert rule. To define the alert rule you must specify:
The scope of the alert role in other words The Resource you want to monitor.
A condition on which the alert was triggered. The specific trigger for the alert is based on a signal type which can be activity log an entry in the activity log created by an action performed on the resources such as regenerating its subscription keys or metric and metric threshold such as the number of errors exceeding 10 in an hour.
Optional actions such as sending an email to an administrator notifying them of the alert or running and a geologic up to address the issue automatically.
Alert rules details such as a name for the alert Rule and The Resource group in which it should be defined
View metrics turn on new line AZ monitor collect metrics for AZ resources at regular intervals so that you can track indicators of resource utilisation health and performance.
The specific metrics gather depend on as a resource will stop in the case of cognitive services AZ monitor collects metrics relating to the Endpoint requests data submitted and returned errors and other useful measurements.
New metrics in the Aether portal toll online you can view metrics for an individual resource in the AZ fossil by selecting the resources and viewing its metrics page.
On this page you can address or specific metrics to charts by default and empty chart is created for you and you can add more shots as required.
You can add multiple metrics to a chart and choose appropriate aggregations and shot types will stop when you are satisfied with the truck you can share it by exporting it to excel or copying a link to it and you can clone it to create a duplicate chart in the metrics page-potentially acting as a starting point for a new chart that shows the same metrics in a different way
Add metrics for a dashboard for a new line in the Aether portal you can create dashboards that consists of multiple visualisations from different resources in your AZ to help you gain an overall view of the health and performance of your AZ resources
To create a dashboard select dashboard in the ad for sylvania your default view may already be set to dashboard rather than the portal homepage. From here you can add up to 100 names dashboards and encapsulate views for specific aspects of your AZ services that you want to track. You can add a range of tiles and other visualisations to a dashboard and when viewing metrics were specific resource in a chart as described previously you can add the chart to a new or existing dashboard.
Managing diagnostic:
diagnostic logging enable you to capture its operational data for a cognitive services resource which can be used to analyse service usage and troubleshoot problems.
Create resources for diagnostic log storage:
To capture diagnostic logs for a cognitive services resource you need a destination for the log data.
You can use AZ eventhub as a destination in order to then forward the data to a custom telemetry solution and you can connect directly to some third-party Solutions; but in most cases you will use one or both of the following kinds of resource within your AZ subscription:
AZ log analytics-a service that enables you to query and visualise log data within the AC portal.
Az storage-a cloud-based data store that you can use to store logs archives which can be exported for analysis in other tools as needed.
You should create these resources before configuring diagnostic logging for your cognitive services resource.
If you intend to archive log data to AZ storage crate the AZ storage account in the same region as your four connective services resource
Configure diagnostic settings colour new line with your logs destinations in place you can configure diagnostic settings for your cognitive services resource.
Hue define diagnostic settings on the diagnostic settings page of the blade for your cognitive services resource in the agportal. When you add diagnostic settings you must specify:
A name for your diagnostic settings The categories of Law given data that you want to capture
Details of the destinations in which you want to still the log data
View log data in a z log analytics:
It can take an hour or more before diagnostic data starts flowing to the destinations but when the data has been captured you can view it in your AC log Analytics resource by running queries.
