In the Azure Portal, I've created blob storage as follows:
http://mymedia.blob.core.windows.net/
I've enabled logging by going to mymedia > configure > logging and enabling it.
Unfortunately when I go to:
http://mymedia.blob.core.windows.net/$logs
I get a "resource not found error".
So my question is this. Once I've enabled logging for storage, how do actually access it? :/
Cheers
Pete
I also spent some time looking for it.
It seems that:
the $logs container does not show up in the online Azure Portal
the $logs container does also not show in in the Visual Studio (2015) Cloud Explorer
But it does show up in the Microsoft Azure Storage Explorer tool
I don't believe the $logs container is public by default. Can you use a tool like Cerebrata's Azure Management Studio to open your storage account and view the $logs container?
They won't be under "Blob Containers" node but under "Storage Analytics" --> "Raw Data" node as shown in the screenshot below:
Cerebrata's tools are great, or for some free options check out the following:
Azure Storage Explorer 5. http://azurestorageexplorer.codeplex.com/
Azure Explorer. http://www.cerebrata.com/labs/azure-explorer
Another tool to go through Azure storage logs is CloudVyzor LogPad, now in beta. Comparing to Storage Explorer, you can actually search through there logs. This video explains it in details: https://youtu.be/q8el9e71jIE
Related
I am wondering if the Azure Storage explorer can be used to access the files in Azure NetApp. If not, what is the storage explorer-like solution for Azure NetApp?
No storage explorer cannot be used to access NetApp files. I highly doubt if there is an explorer available as of now unless you use some commands and create your own onw
I couldn't find this from Microsoft support page,
but Is it possible to add description/metadata to an Azure Blob using Azure Portal? Without using any lines of code.
Use Microsoft Azure Storage Explorer to do it.
http://storageexplorer.com/releasenotes.html
It allows you to edit metadata graphically like so:
After generating SAS for an Azure Storage Container, when using it in Cloudberry or Azure Storage explorer tool, a base64 error is shown.
My question is can a Shared Access Signature for a container be used in client tools like Cloudberry or Azure Storage explorer?
No. AFAIK, all the client tools today support managing storage accounts using account name/key with the exception of ClumsyLeaf CloudXplorer. You can give that a try.
In 2020, SAS connection is also supported by Microsoft Azure Storage Explorer.
If anyone trying to solve 'ACL on azure storage' in your company without having full Azure AD - for now you're just going to have to get inventive with managing those connection keys, but this platform keeps evolving so keep an eye on the space.
I want to monitor a cloud service in azure portal . When I go to the azure portal , I get the message as "LEVELThis setting is not currently available." under monitoring tab.
Then I learnt from the msdn that , right click on web role in visual studio and check the "enable diagnostics" checkbox.
Then I redeployed the application azure portal .
Still the monitoring option is not configurable. What could be the issue ? What am I missing here?
For Storage you can enable monitoring and logging from within the respective tabs within the Storage configuration pages of the portal.
Jason
In the previous Silverlight Azure Management portal it was possible to "browse storage" and select a service package and the service configuration from Blob Storage:
and that was very convenient.
Now in the "preview" new portal the equivalent dialog looks like this:
Looks like the only option now is uploading the file directly from my computer.
How do I create or update a deployment from files in Blob Storage now?
I don't think this is available just yet in the new portal. You can always go to the old portal from the newer one and use the feature from there. There are still a number of things that the new portal will not do (e.g. SQL Azure Management, Managing Co-admins etc. to name a few) and for those, you would need to go to the old portal.
Hope this helps.