Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

logging.exception does not create entry in exceptions table

Aperta
#866 9 commenti 2 reazioni 1 assegnatario Vedi su GitHub

Nessuno ha ancora preso questa issue.

Valutazione

Questa issue non è ancora stata valutata.

Descrizione

area:python-functions needs-investigation

When logging.exception("Simple Exception") then it should show up in the exceptions table in App Insights. It only shows up when it is explicitly raised.

If we want to show 403,404 as an "exception from the app's point of view" and correlate with requests etc currently the app insights will only show failures that explicitly raised an exception. If a valid HttpResponse is sent with 403, it will be shown as successful request because the function executed successfully. But from the app's point of view, if it needs a simple correlation between requests/traces and exceptions, the workaround is to use logging.exception and assign it a error for ease of querying.

But the logging.exception when used outside of a try/catch context in Python functions does not log the exception inside exceptions table in app insights.

Here is a sample code that can be used to test this:

def main(req: func.HttpRequest, context: func.Context) -> func.HttpResponse: logging.exception("Before exception logging") try: raise ValueError("Oops. something went wrong") except ValueError as err: logger.exception("Simple exception logging:" + str(err)) #raise #HTTP 500 kill -> failed.

In this sample "Before exception logging" statement does not show up in the exceptions table
traces
| where message contains "Before"

exceptions
| where message contains "Before"

Overall this would have been an easier stopgap method to correlate exceptions in Python as it does not have a provision to override the custom telemetry model offered by App Insights.

Lingua principale
Python
Stelle
357
Fork
116
Merge medio
32m
PR unite (30g)
1

Guida per i contributori

Apri la guida per i contributori

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di Azure/azure-functions-python-worker

Tutte le issue di Azure/azure-functions-python-worker

Issue simili

Altre issue su Python

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.