You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is handy as a spot check. However, there isn't really an equivalent when deployed as service. Some information is logged about listeners, and for HTTP triggers there's a bit more, but these tend to be scattered, and there isn't a clear way to just get the list of Functions that were loaded.
Describe the solution you'd like
A log or sequence of logs should inform the user of each function that was loaded, as well as its trigger type.
Describe alternatives you've considered
Other methods can be used as well (such as the endpoints to list functions), but this is diagnostic information which should be available when troubleshooting issues with a given function loading, etc.
The text was updated successfully, but these errors were encountered:
What problem would the feature you're requesting solve? Please describe.
When debugging locally with the Core Tools, you get a clear log of what Functions are loaded, as well as the endpoint for any HTTP triggers:
This is handy as a spot check. However, there isn't really an equivalent when deployed as service. Some information is logged about listeners, and for HTTP triggers there's a bit more, but these tend to be scattered, and there isn't a clear way to just get the list of Functions that were loaded.
Describe the solution you'd like
A log or sequence of logs should inform the user of each function that was loaded, as well as its trigger type.
Describe alternatives you've considered
Other methods can be used as well (such as the endpoints to list functions), but this is diagnostic information which should be available when troubleshooting issues with a given function loading, etc.
The text was updated successfully, but these errors were encountered: