Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

"The next 5 occurrences of the schedule will be:" <- can this logging state be for 'Info' instead of 'Verbose'?

See original GitHub issue

When I run my webjeb with Verbose logging, I can see this :

The next 5 occurrences of the schedule will be:
[02/03/2016 23:39:55 > 44c742: INFO] 2/5/2016 2:00:00 AM
[02/03/2016 23:39:55 > 44c742: INFO] 2/6/2016 2:00:00 AM
[02/03/2016 23:39:55 > 44c742: INFO] 2/7/2016 2:00:00 AM
[02/03/2016 23:39:55 > 44c742: INFO] 2/8/2016 2:00:00 AM
[02/03/2016 23:39:55 > 44c742: INFO] 2/9/2016 2:00:00 AM

which is awesome. But i don’t see it when logging is set to Info (ie. for our production webjob).

Could this information please be promoted to Info level, if my guess is accurate?

Issue Analytics

State:
Created 8 years ago
Comments:5 (3 by maintainers)

Top GitHub Comments

1reaction

mathewccommented, Oct 19, 2016

Addressed via @brettsam’s commit

0reactions

brettsamcommented, Sep 28, 2016

So I thought this was going to be dead-simple. But turns out we actually prevent ‘Info’ logging by default: https://github.com/Azure/azure-webjobs-sdk/blob/master/src/Microsoft.Azure.WebJobs.Host/ConsoleTraceWriter.cs#L59

I can get around this by specifying “WebJobs.Execution” as my source for the log. @mathewc, is that what you’d expect an extension to have to do in order to log to the console? See PR #155 for what I mean.

Top Results From Across the Web

Azure WebJobs TimerTrigger not triggering

Recommend turning on Verbose logging locally - the JobHost will then print the execution schedule to the Console on startup, so you can...

Azure Function App - Timer trigger not firing

Hello, We have a Function App with a single Timer trigger. It is hosted on an App Service Plan (P1v2). We have Always...

Logging HOWTO — Python 3.11.4 documentation

Call this method only from an exception handler. Logger.log() takes a log level as an explicit argument. This is a little more verbose...

Log Levels Explained and How to Use Them

Log levels are essentially labels that indicate the severity or urgency of the various events in your application. Their primary purpose is to...

Chapter 23. Viewing and Managing Log Files

Log files are files that contain messages about the system, including the kernel, services, and applications running on it. There are different log...