I have got two database (SQL azure) in North America, I'm getting error that the applications can't Access to the server.
I didn't update the application or database, so I supose that there are a problem with sql azure service. How can I notify Microsoft of this problem?
To 'notify' Microsoft, you have very limited options.
They have their own support forums.
They have their own support ticketing system, that costs a pretty penny but is the fastest way to get their attention.
They have their dashboard, which in my own experience is terrible. It is not a true representation, ever. The updates are very very late.
You also have StackOverflow - but there will be little that we can advise on if there is a problem on the Azure infrastructure side of life.
To help aid in your Azure support woes, I would suggest you get an account with Pingdom and get MetricHubs for your subscription. These will help in showing what goes down, when, how often, and for how long. It can help show if the problem really is in your application or not.
I would also ensure you have diagnostics set up, and log everything you can.
Many many people forget or don't know about the transient error problems. Microsoft have a huge article on it, but it does trip people up a lot.
The Azure Management Portal should also be able to give you a quick summary of if your roles & instances are actually up, healthy and stable.
Related
I have a Flask Application (python for the backend + js/vue for the front) that is running on an Azure App Service. I face very bad performance : lot of time during the day, the application takes minutes to responds. I cannot understand why, is this App Service is very bad ?
Regarding the App Service Plan, I have the P2V3 (220€/month, 16go and 4vCPU), I have also a SQL Database to store information.
I don't know if I can provide more information, but it is really impossible to use it on a long term, for example here some of metrics of the "slow down" issue :
So it is related to Azure issue (and for example can be solve moving on AWS), or to my application ?
If there is any information that I can provide to help identify the issue I can provide, I am not an infrastructure expert so I am not really able to identify myself what it is important to check.
Thanks
#kilag, thank you for confirming this. Looking at the graph you provided, this seems to happen intermittently, correct? Has this behavior been occurring since the start or did it recently start happening after a recent deployment?
Are there any other external dependencies beyond the SQL DB? Such as a CDN?
I would suggest following #azMantas's advice to try out the diagnose and solve blade. This is the same tool that support engineers use when you purchase a paid technical support ticket. More information on that here. This is the quickest way to uncover a potential issue.
Please let us know if there are any insights provided such as a storage volume failover that might be reported in the diagnose and solve blade.
If you see nothing in the diagnose and solve blade, please reach out to us at azcommunity#microsoft.com with the subject ATTN: Bryan and in the body of the email, include your azure subscription ID so we can assist you further. We look forward to your reply.
I have an Azure Cloud Service published at Microsoft and it's draining all my credit!
Payment
Pay as you go
Service resource
Minimal resource, 1 SMALL web role and 1 SMALL worker role.
I knew Azure wasn't cheap, but this is just too much. Currently my monthly cost is just under 80 USD. The only person that use this service is me, noone else, and I barely use it. So the cost is just for the upkeep.
Is this normal?
70 bucks a month!?
How much does it cost for YOU?
What Microsoft support told me
I am afraid the Cloud Services has a fixed price, and I am not aware
how it could be lowered. Maybe you want to check on how the service
itself could be tweaked to get it working as per your needs. You may
want to go through the Community Forum for that.
Community = Stackoverflow, so here I am!
If I look at my Azure subscription page I can see that it's the:
CALCULATING HOURS - Europe, Western
That is taking all my hard earned money. My service also uses SQL, storage and cache but, if I understand it correctly, these are not the cause for my expensive bill.
Before I leave you to it I just want to say that I can't use a simple web app because of my requirements. I know web apps are super cheap, but in this case I must use a cloud service..
Thank you
Update
I found out I was using A1 (small) and not A0 (extra small). The instance type for a cloudservice can be set in the servicedefinition file.
It's sad that not even Microsoft themselves could inform me about this.
Web and worker roles are like dedicated VMs if they are on, they will cost you money.
You can do one of two things
1) Stop the machines when no one is using them ( say in the off business hours). I am not sure if this is possible to do or not in your case. But if it is possible, you can run a small script to start/ stop the roles. You can even do so via apps on your phone. For example - https://itunes.apple.com/us/app/azure-management/id826446897?mt=8
2) Move to Azure Web Apps and Azure Web Jobs - Both these services are "multi-tenant" and cost much less and in fact offer a free tier. If and when you need to scale, you can always scale as your need
Hope this helps
We use the Northern Europe Azure Data Centre. We use SQL Azure Web Edition with Websites. Today we seem to be getting quite a few SQL Azure disconnections with error code 10054:
Symptom:
A transport-level error has occurred when receiving results from the server. An established connection was aborted by the software in your host machine
Mitigation:
Implement retry logic in your application
What is frustrating about this is that I cannot find any MS Azure Alerts to an issue. I suspect their SQL Azure systems will be ringing alarms. I have looked in Azure Status and Management Services.
Are there other places I can looks for these alerts, and also what is the best way to notify MS that there is an issue.
Finally how are folks monitoring SQL Azure for issues, throttling, disconnects etc? I have come across cotega.com.
P.s as a side note, I do understand the importance of putting in "retry logic", and but cannot happen quickly, and my code could be improved in this respect. However something does seem wrong with SQL Azure today. Up until now, the service has been by and large great.
EDIT 1:
Error Code:
Error Number:10054,State:0,Class:20
EDIT 2:
I think the moral of this story is to not underestimate the impact of throttling and scaling out, rather than scaling up, of SQL Azure services, and the importance of implementing retry logic/ MS Transient pattern logic. Still, this variable performance is a little frustrating, but perhaps this is the cloud for you, although with the new Data Tiers you can pay for more predictability.
EDIT 3: Interestingly SQL Azure is not performing more efficiently with no errors being noticed. So an issue with Azure. However difficult to identify apart from application error logs. I use Elmah.
Reconfigurations happen when upgrades are rolled-out to the service or when databases are load-balanced to avoid noisy neighbor issues.
The view sys.event_log in the master DB has information on why the disconnects happened (reconfiguration vs. throttling, etc.).
Service outages are reported in the portal.
We have got an application running fine on On premises and plan to move it to IaaS on Ms Azure, do we need to make any changes to it or will it work as is?
I agree with the above post. You have not detailed if you are using Virtual Machines (Sql server or going to use Azure SQL). You will have to make choices about fail-over and geo redundancy, cloud services, etc. There are IP restrictions that may affect you (I don't know since I am not sure what you are moving). More than anything, I always warn people about the cost, it is difficult to understand. Here is an article series I wrote on Azure & SharePoint, you can skip the SharePoint stuff but the cost/limitation/VMs and such would still apply.
http://www.matthewjbailey.com/sharepoint-azure-guide/
We've managed a lift-and-shift of an on-premise Windows app into Azure, but I wouldn't say it's been without its pain. The above comments definitely ring true; you need to provide a bit more of an overview of what the current application does so that people can help answer your question.
In my experience, the only stumbling blocks to moving on-premise into Azure are:
Hardware requirements; i.e. if your application requires some specific hardware
Cost: It's not always cheaper to move large systems into Azure
Licensing: Make sure that your existing licensing is compatible with a cloud system which you don't control
Windows Azure has a store.
The stuff you can by there are called Add-Ons, and they fall in two categories: Service and data.
I understand the point of some of the service offerings, but not all, and I don't yet understand the point of the data offerings at all.
With services, some offerings are database deployments such as ClearDB (MySQL) and MongoLab. That makes sense to me: You get those databases deployed and monitored with a few clicks, yet those databases run in the same data center as the applications that consume them, which is good for performance and security.
For most other services (there is a simple scheduler application, for example), it seems that the only advantage is the unified billing method. Is that a correct observation, or is there more to it?
Then the data offerings: The fact that I can buy bing query transactions cannot really have anything to do with the rest of my azure account, right? Technically, it's just bing (or whatever other data offering you look at) and presumably I'm going against the same bing api that I would have used previously (I'm assuming that was possible). There is nothing really deployed in any Azure data center the moment I buy it, is there? So in what sense is that an Add-On?
In a nutshell, am I missing something or are most Add-Ons just a method of buying external services and having the billed on my Azure account?
If you can answer the question for other 'app stores', you can answer it for Windows Azure. We know about THE App Store (as per the court battles over the name) which is the only way to get applications onto the closed (iOS) device. There is also a Mac App Store which would seem unnecessary because of the ability to install apps by yourself (which makes it more similar to the Azure store). In this case the reason for the store is discoverability, association with the store brand (where the buyer assumes a degree of vetting), a single point for updates, and simplified billing.
The Windows Azure Store (and data marketplace) exist for similar reasons. It is less about the technical benefits than the association with the Azure brand. Since SO is technical, let me highlight some (largely) technical aspects:
Don't assume that the service will run in the same data centre. In most cases it probably won't.
There is an advantage of having everything in one place from an operational point of view. Granting of operator access to the subscription means that you don't have to administer accounts on the service. I have had problems with this though - where the service made it difficult to do other things (such as get support) because the Azure identity wasn't handled very well. (I had this with New Relic).
The combined billing works on credit card payments only. Last time I checked (Summer 2013) there was no way to get an add-on with a pay-by-invoice subscription, so a second subscription (with credit card) was needed anyway.
Add-ons seems to still be in 'preview', which may indicate low adoption. Microsoft probably hasn't seen it grow the way they expected and may not be developing it much in future. This is opinion only, and shouldn't affect the service (after all the store is just a gateway, and has no (little) technical impact on the service provided)
Don't completely ignore the store however. The biggest benefit seems to be the free tier of the servers and reduced pricing, where Microsoft has managed to get service providers to make the store attractive. For example, the SendGrid free option provides 25,000 emails per month, and there doesn't seem to be a free option on SendGrid.com. New Relic pricing was (and maybe still is) significantly less.
Pay attention mainly to the pricing benefits, rather than perceived technical benefits.