search

projectkudu / kudu

Kudu is the engine behind git/hg deployments, WebJobs, and various other features in Azure Web Sites. It can also run outside of Azure.
Apache License 2.0
3.12k stars 655 forks source link

Allow storing webjobs history to Azure blob storage to make swapping experience better #1779

Closed kamranayub closed 4 months ago

kamranayub commented 8 years ago

x-post from azure/azure-webjobs-sdk#586

So this is an interesting issue.

When I perform a swap in Azure, I noticed that the job data that Kudu displays in the web jobs dashboard also swaps.

Case in point.

On my dev slot, I issued a triggered job run:

image

Take note of the run time: Tue, 20 Oct 2015 03:36:42 GMT

Then, after I swapped, I see that exact run in my production slot's dashboard:

image

To prove it, I also can issue an API request against the production slot and see my run ID:

{
  "id": "201510200336425903",
  "name": "201510200336425903",
  "status": "Success",
  "start_time": "2015-10-20T03:36:42.5903978Z",
  "end_time": "2015-10-20T03:37:02.8328967Z",
  "duration": "00:00:20.2424989",
  "output_url": "https://xxx.scm.azurewebsites.net/vfs/data/jobs/triggered/QueueUpdates/201510200336425903/output_log.txt",
  "error_url": null,
  "url": "https://xxx.scm.azurewebsites.net/api/triggeredwebjobs/QueueUpdates/history/201510200336425903",
  "job_name": "QueueUpdates",
  "trigger": "External - Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/46.0.2490.71 Safari/537.36"
}

It returns a 404 if I try the same API call against the dev slot.

(I didn't include the URLs but you'll have to trust me)

I assume each time I swap, it's swapping the dashboard storage connections too. I double checked my own connection strings (AzureWebJobsDashboard and AzureWebJobsStorage) and they are Slot Settings and remain the same after a swap.

davidebbo commented 8 years ago

Today, Kudu never deals with storage accounts. Conceivably, there could be a provider model that would allow us to save things to alternate stores. This could be useful for both WebJobs history and Deployment history, which both behave a bit strangely during swaps when using the file system.

Maybe the simplest solution is to wait until Azure Web Apps get general support for Azure File storage. Then it would be a matter of mapping the relevant files to a different folder, without having to deal with a different protocol. Though that could take a while.

jvano commented 4 months ago

Hi

Kudu will continue to run in Azure App Service. However, this repo will no longer be maintained. If the problem persists and is related to running on Azure App Service, please open a support incident in Azure: https://learn.microsoft.com/en-us/azure/azure-portal/supportability/how-to-create-azure-support-request

This way we can better track and assist you on this case

Thanks,

Joaquin Vano Azure App Service