Reading what is in the vsdiagnostics blob in Azure (1.7) - azure

I've enabled Diagnostics in one of my Worker roles and published it to Azure. There was a new blob container created called "vsdiagnostics" and contained within in are two binary files. I'm assuming that these files contain the output of my Trace statements, but I'm unable to open these files as I have no idea what format they are in.
I've not found anything on www.windowsazure.com about it and most of the tools they recommend are very outdated. I have installed Cerebrata's Azure Diagnostics Manager, but that isn't able to load the Trace Logs.
If anyone could point me in the right direction I'd be grateful!

Most of the time when Visual Studio is used directly with your Windows Azure application, either with deployment or with troubleshooting, it creates a container in your Azure Storage and use this container to get/put data to in between your Azure instance and your Visual Studio instance. Mostly when you see container name start with VS* i.e. VSdeploy or VSDiagnostics, you can take an account that it is related with Visual Studio.
VSdeloy container is used when you deploy your application directly from Visual Studio. First your cspkg is transferred from desktop to this container and then to RDFE.
VSDiagnostics container is used to get the intellitrace data from your Azure Instance to your Visual Studio instance and when blog is downloaded to your desktop and then it is visible in VS as intellitrace logs.

When you opt to view Intellitrace logs, it appears that they are loaded into the vsdiagnostics blob, before being transferred to Visual Studio.

Related

Why is webjob log not showing proper failed message?

I am trying to execute a manually triggered webjob. The system automatically gets failed without showing any proper failed message. I even added application insight to the program but i can't see any failed log in application insight as well.
My main application calls different interfaces and methods from different projects. I have linked all of them by adding references in my main project. I uploaded my webjob simply by using visual studio 2017 feature Publish Azure Webjob
App.config screenshot:
I have couple of connection to Azure file share and one for Database(Microsoft SQL Server)
When I am uploading .exe file from bin>release and then when i am running it this error message is showing up:
The issue is with adding reference to class library from my console application. Although the issue still persist but now at least I know where I am going wrong.
We have reproduced the issue from our end and faced the same problem while deploying the webjob from Visual Studio.
But we have successfully able to run the webjob as you can see in the below attached screenshots for your reference.
Points to be re-checked from your end to publish the webjob to azure app service without any errors:
Make sure after creating the webjob ->open the app.config file in the VS and add the below configuration properties under the <configuration>:
<add name="AzureWebJobsDashboard" connectionString="place your storage account connection string here"/>
<add name="AzureWebJobsStorage" connectionString="place your storage account connection string here"/>
We have used runtime .net framework as Version=v4.7.2 in Visual Studio 2017.
Note: copy and paste the same storage account connection string for both the above properties in app.config file i.e. AzureWebJobsDashboard and AzureWebJobsStorage.
After adding these properties in the app.config file -> save it and right click on the solution explorer tab in Visual studio and build:
Then publish to azure from the solution explorer tab in VS:
Now go to the App Service in azure portal and select webjobs then run the webjob and click on the logs tab to show the results page as shown below:
If the webjob gets successfully deployed then you can see the status as Running like in the below screenshot:
If there are any Errors after the deployment then you can see the error messages by clicking the toggle output screen and troubleshoot based on the error message like below:

Visual Studio 2017 Publish Targets Azure App Service Linux Instead of Azure App Service

We are experimenting with the templates created here: http://blog.stevensanderson.com/2016/10/04/angular2-template-for-visual-studio/. However when we open in Visual Studio 2017 and select publish we are presented with only a Linux App Service:
Instead of:
Can anyone explain what configuration is causing this to happen, as the only option is the Linux preview existing app services we have in Azure are not available to be selected.
I believe it's the presence of the Dockerfile. If you close the Publish UI, delete the Dockerfile, and reopen the Publish UI, it will show the non-Linux App Service option. See here for a little bit of info.

Redeploying an Azure WebJob

How do you redeploy an Azure WebJob? I can see in the Azure portal how to create a WebJob and do the initial upload, but the portal does not appear to allow re-uploading changes, am I right?
I've also looked in the Kudu interface but I don't see anywhere obvious there that allows uploading updates.
So when I make an update to a job how do I release the update.
Thanks.
The Azure portal currently doesn't support updating a WebJob but all you have to do is update the files in the correct place on your site which is: d:\home\site\wwwroot\app_data\jobs\{jobtype - triggered/continuous}\{jobname}'
Read more about this here: http://www.amitapple.com/post/74215124623/deploy-azure-webjobs/
As of Visual Studio 2013 Update 3 and Azure SDK 2.4 this is possible from within Visual Studio. Just right click and select Publish on the web job project.
How are you deploying ? If you use then this will generate the code in your solution to deal with the deployment. I am deploying and using this plugin with VS Team Services and Azure and it is working well.
http://visualstudiogallery.msdn.microsoft.com/f4824551-2660-4afa-aba1-1fcc1673c3d0

Visual Studio app deploy is deleting extra files on Azure web site

I'm using the AzureContinuousDeployment.11.xaml Visual Studio 2013 Template for CI builds from visualstudio.com to an Azure website and it's working great.
However, I need to keep additional files on the server (the app creates files). If I was using the "Web deploy" method, I'd simply disable the "Remove additional files at destination" property, but I don't see an option for that using the Azure deployment template.
I should be able to add /p:SkipExtraFilesOnServer=True to the MSBuild arguments in the build definition, but it isn't working. Files are still being deleted from the web server when I deploy.
I've also tried creating a publish profile and adding it to the template. It hasn't worked either.
I don't think there is a way to keep app-created files while using visual studio deployment. I suggest you to create an Azure Storage account and store those files in the storage (blob would be good enough). It seams that you are using ASP.net. See more detail at Microsoft Azure Storage Client Library for .NET.

Windows Azure Cloud Service: recover lost source code

I have a cloud service (WCF role) published on Azure. Source code has been lost. Is there anyway to download the deployment package back from Azure? Or any other way to get the DLL's back.
Perhaps. If you have RDP enabled, or at least configured, in your service definition on the role you can RDP into the instance and retrieve the DLLs that way.
If you deployed using Visual Studio then a copy of the package is in one of your Storage accounts because it uploads the package there before deploying it. Check each of your storage accounts for a vsDeploy container in your BLOB storage. I think a few other deployment mechanisms use this as well. If you find it you can download the cspkg file, rename it .zip and open it up just like a zip file. Inside for each role you'll see a cssx file. Extract that and rename it to .zip as well. Opening the csx folder will show you the code that was deployed to your instance.
Regardless of how you perform your deployments I highly recommend keeping the cspkg files you publish so that you can rollback or know what went out. I'd also recommend having RDP at least configured in your service definition but perhaps disabled for when you need to troubleshoot. Turning it on and off is a configuration update, though that can have it's own side effects.
If all else fails and you have a Windows Azure Support level of some kind above free you can put in a ticket to see if they will retrieve the DLLs for you I guess. I've not tried that.
Update: I didn't know about the operation to get package that Gaurav indicated. That should be your answer to retrieve your code.
Windows Azure Service Management API has an operation for that: http://msdn.microsoft.com/en-us/library/windowsazure/jj154121.aspx. I suggest you take a look at it.

Resources