i have a managed mariadb (10.3.23) in Azure.
The log_error parameter is not available in the Azure portal and audit log i don't think will give me what i need.
(i'm getting a few mariadb crashes that azure recovers ok but i'd like to know why..)
is there anyway in Azure i can switch on mariaDB's error logging and get to see the results ?
thanks
Related
I have been using Rest API from Azure Data factory to scale up and scale down Azure SQL DB.
This was running fine last couple of months. But recently I started getting some intermittent error. Sometimes the rest api from ADF showed below error.
"internalServerError","message: an unexpected error occurred while processing the request"
But when I check the database I found that the database is successfully scaled up / scaled down.
Even though, Azure SQL DB activity log shows an an error related to 'auditIfNotExists' Policy action.
Can anyone help me with this ?
I am using api-version 2017-10-01 ? Is this policy error related api version ? How to decide which api version we need to use ? Is it always latest version to use ?
Or is the error related to something else ?
I have an Azure WebApp that continually reports "Your app experienced failure(s) due to a transient storage access issue." The suggested solution is "Explore Local Cache feature for your web app." but my webapp exceeds the maximum storage (3GB) for this option.
The problem mostly occurs between midnight and 6am in the morning when the site is LEAST active, but there seems to be an increasing number of occurrences during the day.
What are the underlying causes of this problem? Is this something to do with my WebApp or is it the Azure Infrastructure. In either case, how do I determine the underlying issue(s) and resolve?
"Your app experienced failure(s) due to a transient storage access issue."
The Web Apps environment provides diagnostic functionality for logging information from both the web server and the web application. You could try to enable Logging and check the logs that generated within that period of time.
According to the error, it seems that a temporary issue causes app failure, and it suggests enabling local cache. You could follow the suggested solution and make sure if it helps resolve issue.
Besides, you could try to scale your web app (which would take additional charge) and check if it could mitigate the issue.
Updates:
As we know App Service offers a shared, persistent storage for the application. Maybe something wrong with the shared storage when the instances in farm access the storage, which may be the cause of the issue.
To determine the underlying issue, you may try to enable diagnostics logging for your web app. This should provide more information on what is happening at the storage level and what kind of activity is going on.
We are using the SQL Database Sync feature in Azure and whilst it generally works without issues it does occasionally fail. The failures can be due to lost database connections or failures in which the error messages in the Azure Sync Log don't help. I see no way in the Azure portal to set up alerts to email us when a sync fails and I don't see any Azure cmdlets that will return the status of a database sync. Does anyone have any ideas how we can add monitoring to the service?
Thanks!
I did crosspost this later to the msdn forum that user6133663 listed below.
The answer from Xu Ye (who I assume works for MS) was:
You are right. Currently SQL Data Sync did not support API & failure alert. We will keep you update if any update on this.
So, to answer my original question, there is currently no way to monitor the success or failure of a SQL database sync.
I have a website hosted on Azure. I am using Trace.Error to output all my error logs to file system. However when I enable Application Logging on Azure website, it only remains enabled for 12 hours.
This is also confirmed in this article: http://www.hanselman.com/blog/StreamingDiagnosticsTraceLoggingFromTheAzureCommandLinePlusGlimpse.aspx
Now I will like to keep storing error logs indefinitely (i.e. till my website is live). I am not sure if I am missing the point here. How can I keep logging enabled forever?
You can store your logs in Azure Storage (tables or blobs). This doesn't have the 12 hour constraint that the file system does.
When I access a SQL table via the server scripts is the sql azure retry logic implemented somewhere following the
request.execute(); ?
Yes, the underlying code will try several times to complete the operation with SQL Azure over a 30 second window.