I've had a site running on a azure 2.4 cloud service for some time without any problems. This site is using diagnostics to log errors and user inputs to a wad_logs_table in a storage account. After upgrading to 2.8 this doesn't work anymore.
Ive tried to enable diagnostics after upgrade and configure the "new" config diagnostics.wadcfgx file with storage account info, but I don't think it is working. As I understand it will not be using the wad_logs_table anymore? What do I need to change? Where can I access the logs?
Related
I was genuinely interested into deploying datados as a MaaS from the azure marketplace, and I did so just to try how it works. The configuration was extremely easy and I was able to see all the metrics and infrastructure and the logs of all my infra.
But the fact that my data leaves EU to get to US, I didn't like it too much. So I was reading that Datadog has a EU infra but you require to have a vm and install the host there.
So I did follow the official documentation and configured:
Azure Windows VM
Download and installed the agent
Once the agent was installed, I configured azure integration
Created the app registration
Set the role to Monitor reader
Configured the app service principle in the azure integration in Datadog.
Everything worked just as expected, but when I try to access the logs blade in the left hand side, I don't see any log but instead a initial configuration that needs to be done, like:
Server
Container
Cloud
Client
Other
Can please anyone help to understand what I am doing wrong here?
If I want to ingest all the logs from my monitoring (which I have already the permissions set) do I really need to create the event grid, azure function as mentioned under the Cloud section?
I though that the monitoring service principle was more than enough to ingest all the data.
Just out of curiosity, under logs => Server I tried to follow the configurations for .net and enable the logs
logs_enabled: true
site: datadoghq.eu
and set the sharp Configuration file. but nothing, after restarting the service, I am still unable to receive any log from my subscription.
If anyone can help understand what I am doing wrong here, I would be really grateful.
Please if yo need any extra info, just let me know
I have created a custom OS images on Azure containing my app, omsagent, and a configuration file to track my application logs. I verified that the custom logs were available on Log Analytics Workspace for that VM.
When I create a new VM with this custom OS, using Python SDK, I don't receive logs in the workspace. I verified that omsagent is working. It is sending heartbeats that are visible on the Log Analytics Workspace > Insights > Agents.
I found out that the new is was not Connected to the workspace.
So my question is how do I automatically connect a VM to Log Analytics Workspace at creation time?
I would advise against baking the Log Analytics Agent (OMS Agent) into the image directly - Azure doesn't recommend this kind of setup. Instead, you should be using an Azure Policy that they provide exactly for this scenario.
We have dozens of VMs and Scale Sets we need to manage with Log Analytics Agent installed on each of them when we build the custom images. In the beginning everything was working fine but a couple of months later those images stopped working.
After spending some time investigating with the Azure team we found out that the agent's certificate wasn't being renewed and it wouldn't connect to the Workspace automatically. Even worse was that because of this, it was failing all our images builds.
We were told that this is not the right practice and we should look at Azure Policies. They are rather easy to setup - just assign once and forget about them. It's also good for compliance and will let you know if there's any machine that's non-compliant.
Check this link for more info about Azure Monitor policies.
And this link will open your Azure Portal directly into the policies page for Windows VMs.
Here's a preview of the policies available:
I have a WCF service solution which contains the WCF service and a Azure Cloud Service project.
When running the cloud service project in the Azure Compute Emulator (version 2.5 on my PC), all I see in the output for each role is
[fabric] Role state Busy
[fabric] Role state Aborted
I've tweaked the logging level in Compute Emulator to log Warning, or Error and even tried Critical, but no more detailed messages are displayed. I have been Googling to see if there are any event log entries, or log files on disk, that I can view to find out why the cloud service is not working, but to no avail.
What can I do to find out more about what is causing the Cloud Service role to abort and and retry?
Diagnostics logs are not collected in the Azure compute emulator – For projects that target the Azure SDK version 2.5, the Azure compute emulator no longer supports the collection of diagnostics logs, including performance counters, infrastructure logs, IIS logs, and event logs. In addition, logs are no longer stored in Azure storage or development storage. You can continue to view application logs in the Visual Studio Output window or the compute emulator. This only affects projects that target Azure SDK version 2.5; projects that continue to target Azure SDK 2.4 are not affected.
Source: http://msdn.microsoft.com/en-us/library/azure/dn873976.aspx
In my case, it turned out to be a startup task defined in ServiceDefinition.csdef that was the problem. After I removed the <Task> my service ran fine in Compute Emulator.
I have successfully deployed my service to the azure cloud services and its working great. But I am having one problem, I have a logging layer in my service which logs activities and error to the log files. But now when I have deployed my service to azure cloud services I am unable to access the log files, since I made the package file for deploying it to azure. Can somebody tell me how to access those logs file.
Windows Azure Diagnostics - http://msdn.microsoft.com/en-us/library/windowsazure/gg433048.aspx.
There is also a couple short 5 minute videos that shows how to set it up and use it - http://channel9.msdn.com/Series/DIY-Windows-Azure-Troubleshooting/Enabling-WAD and http://channel9.msdn.com/Series/DIY-Windows-Azure-Troubleshooting/WAD-Intro.
I have an Azure Worker Role (WR) which is supposed to pick up it's config from the .cscfg files using:
var setting = CloudConfigurationManager.GetSetting("My.Setting.Name");
Running in the emulator this is fine, I get the:
Getting "My.Setting.Name" from ServiceRuntime: PASS.
message. However, when I publish to my remote environment, I get:
Getting "My.Setting.Name" from ServiceRuntime: FAIL.
Getting "My.Setting.Name" from ConfigurationManager: FAIL.
messages. In the 'CloudServices/Configure' section of the Azure Management Portal I can see the setting listed in the configuration, and it's set correctly.
I'm using Azure SDK 2.0
Are you deploying correct Azure SDK .DLL's with your project? Did you by chance upgrade recently to a newer Azure SDK? I would check your .DLL references to make sure that they all match across the solution