Manage Diagnostic Logging

By Ashwin Venugopal -

 






Introduction

Diagnostic logging allows you to collect detailed operational data for an Azure AI services resource, which can be utilized to assess service usage and resolve issues.

Create Resources for Diagnostic Log Storage

To collect diagnostic logs for an AI services resource, you must establish a destination for the log data. Azure Event Hubs can serve as a destination, allowing you to forward the data to a custom telemetry solution, and it can also connect directly to certain third-party solutions. However, in many instances, you will utilize one (or both) of the following types of resources within your Azure subscription:

  • Azure Log Analytics - a service that enables you to query and visualize log data within the Azure portal.

  • Azure Storage - a cloud-based data store that you can use to store log archives (which can be exported for analysis in other tools as needed).

It is essential to generate these resources prior to setting up diagnostic logging for your AI services resource. If you plan to store log data in Azure Storage, ensure that the Azure Storage account is established in the same region as your AI services resource.

Configure Diagnostic Settings

After setting up your log destinations, you may set up your AI services resource's diagnostic settings. On the blade's Diagnostic settings page for your AI services resource in the Azure portal, you can specify diagnostic settings. When adding diagnostic parameters, you have to indicate:

  • A name for your diagnostic settings.

  • The categories of log event data that you want to capture.

  • Details of the destinations in which you want to store the log data.

View Log Data in Azure Log Analytics

Diagnostic data may not begin to flow to the destinations for up to an hour, but once it has, you may view it in your Azure Log Analytics resource by executing queries.

Conclusion

We have successfully learnt about Diagnostic Log storage.















Comments

Post a Comment

Popular posts from this blog

Information Protection Scanner: Resolve Issues with Information Protection Scanner Deployment

By Ashwin Venugopal -
Image
  About If you are experiencing problems with the Microsoft Purview Information Protection scanner, check the health of your deployment by utilizing the Start-ScannerDiagnosticsPowerShell cmdlet to start the scanner diagnostic tool. The diagnostics tool checks the following details and then creates a log files with the results: Whether the database is up to date. Whether network URLs are accessible. Whether there's a valid authentication token and policy can be acquired. Whether the profile is defined in the Azure portal. Whether offline/online configuration exists and can be acquired. Whether the rules configured are valid.  The Start-ScannerDiagnostics command does not perform a comprehensive check of prerequisites. If you encounter problems with the scanner, you need to verify that your system meets the scanner's requirements, and that your scanner's configuration and installation are finished.  Verify Scanning Details Per Scanner Node and Repository Run the Get-ScanSt...
Read more

How AMI Store & Restore Works?

By Ashwin Venugopal -
Image
  CreateStoreImageTask The CreateStoreImageTask API stores an AMI as a single object in an S3 bucket. The API initiates a task that collects all the data from the AMI and its associated snapshots, subsequently using an S3 multipart upload to store this data in an S3 object. It gathers all elements of the AMI, including most of the non-Region-specific metadata and all EBS snapshots included in the AMI, and consolidates them into a single object in S3. During the upload process, the data is compressed to minimize the space utilized in S3, which means that the S3 object could be smaller than the total sizes of the snapshots in the AMI. If the account making this API call has access to AMI and snapshot tags, they will be retained. The S3 object shares the same ID as the AMI, except it has a .bin extension. Additionally, the S3 metadata tags for the object include the AMI name, AMI description, AMI registration date, AMI owner account, and a timestamp indicating when the store operation...
Read more

Create A Store Image Task

By Ashwin Venugopal -
Image
  Introduction When you save an AMI in an S3 bucket, a task for storing the image is initiated. This store image task allows you to track the progress and result of the procedure. Securing your AMIs It is crucial to verify that the S3 bucket is set up with adequate security to protect the content of the AMI and that this security is upheld for the entire duration that the AMI objects are stored in the bucket. If this cannot be achieved, it is advisable to refrain from using these APIs. Make sure that public access to the S3 bucket is prohibited. It is suggested to activate Server-side encryption for the S3 buckets where you keep the AMIs, even though it’s not mandatory. When AMI snapshots are transferred to the S3 object, they are sent over TLS connections. It is possible to save AMIs that contain encrypted snapshots; however, the snapshots will be decrypted during the storing process. Identify the source AMI used to create a new Amazon EC2 AMI You can determine the AMI that was us...
Read more