Andrew Connell
Andrew Connell

Reputation: 5307

$logs Container not created when enabling logging on Azure blob account

I am trying to enable logging so I can get hit/access counts for files within a specific container. I've gone into the portal, selected the storage account and under CONFIGURE, checked the READ REQUESTS under LOGGING for the BLOB and set the RETENTION to 0 days. However I am not seeing the $logs container automatically created in the blob as stated here. Is there some special trick?

I'm fairly certain this is what I should be doing to get this working, but can't figure out what's wrong. I'm simply trying to get hit counts on files accessed in the the blob so if there is another way, I'm all ears.

Upvotes: 1

Views: 1169

Answers (1)

Gaurav Mantri
Gaurav Mantri

Reputation: 136306

There's no special trick really :). You just have to wait out. Once you have enabled storage analytics properly, these containers and tables are created automatically by storage service when it needs to push some data there. Just ensure that you have configured it properly.

Is there a particular reason why you have set the rentention period as 0 days? Try setting it to 1 and see if that makes the difference.

Update

It is important to realize that when blob containers (or for that matter tables) are listed, the analytics blob container (and tables) are not returned in that listing. If you're using a client utility to view data in these containers/tables, please ensure that the tool supports storage analytics feature.

Upvotes: 0

Related Questions