Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add ability to controll WebJob history for continuous WebJobs #752

nibras85 opened this issue Jun 21, 2016 · 2 comments

Add ability to controll WebJob history for continuous WebJobs #752

nibras85 opened this issue Jun 21, 2016 · 2 comments


Copy link

@nibras85 nibras85 commented Jun 21, 2016

From reading the documentation, I see that I can control the history size for a triggered WebJob using the WEBJOBS_HISTORY_SIZE flag as explained here. I however, couldn't see any knob I can use to control the history length for continuous WebJobs.

I have a continuous WebJob listening to a queue that gets millions of messages and my Storage Account is getting filled quickly because of that. If possible, I'd like to limit the invocation history logs for this continuous WebJob.

Copy link

@mathewc mathewc commented Jun 21, 2016

I believe this is a duplicate of #560. That issue tracks the feature request for log retention policies. You're talking about the Dashboard storage logs, right?

Until that feature work is done, your only other options are:

  • Apply TraceLevelAttribute to your high throughput function to limit or disable the logging for that single function.
  • Turn Dashboard logging off completely. Of course this is not an option if you're dependent on these logs.
@christopheranderson christopheranderson added this to the Backlog milestone Jul 13, 2016
Copy link

@christopheranderson christopheranderson commented Jul 13, 2016

We're locking down new features for the next release, so I'm going to pop this into backlog for now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
3 participants
You can’t perform that action at this time.