REST API reliability challenges in Azure
For those of us that are software developers, we are accustomed to this message.
"The underlying connection was closed: A connection that was expected to be kept alive was closed by the server. T...
Forum Discussion
JackLacava The only reason I opened these issues here is because I believe they will frequently be encountered by other customers who migrate an on-prem environment to Azure. I intended to save some of them lots of time, and save your support organization from lots of unnecessary tickets.
These are technical issues, but not overly so. Any customer who is using your REST api will need to understand the potential technical issues that might arise in Azure, even if these issues aren't happening on-prem. Ideally these sorts of technical discussions would take place on stackoverflow. But the community of onestream customers doesn't seem to understand the benefit in that (yet). From what I gather, there is no onestream presence in stackoverflow, so we are left with no choice but to discuss technical issues in this curated/moderated forum instead.
As it turns out, two of my issues were, in fact, related and had the same root cause. Someone had neglected to disable SSL inspection, and that was causing both the TCP disconnection issues and the truncated payload issues.
The third issue (DNS remote name could not be resolved) is something that tech support says they have seen in the past, but it is rare and they say it might be associated with their maintenance work within Azure last night. I am going to monitor it for another week or so, to determine whether the occurrences are as rare as people say. A DNS failure that happens once a week seems reasonable, but not hourly or daily. ... From what I recall, I think the SLA for most DNS service providers is 100%.