Logging configuration for Application Insights

[swebberuk]

Description

Changes for logging to Application Insights, now I have access to Azure to check. This builds on top of what was already merged in #1153

---

To test I added these log lines to the show clinic page:

    logger.critical("Logging at CRITICAL")
    logger.error("Logging at ERROR")
    logger.warning("Logging at WARNING")
    logger.info("Logging at INFO")
    logger.debug("Logging at DEBUG")

Then in Application Insights I could see them. Except the DEBUG message, as log level is INFO:

---

When I forced an error (by trying to check information of an appointment that had not been started) I could see the exception details in Application Insights. The Custom Properties included user and correlation_id:

Jira link

https://nhsd-jira.digital.nhs.uk/browse/DTOSS-12264

[github-actions]

The review app is available at this URL:
https://pr-1203.manage-breast-screening.non-live.screening.nhs.uk
You must authenticate with HTTP basic authentication. Ask the team for credentials.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[swebberuk]

No longer specify logger_name in call to configure_azure_monitor. logger_name was a blocker for full log visibility

The logger_name parameter tells the SDK to attach its App Insights log handler only to the "insights-logger" logger. Every other logger is unaffected.

[swebberuk]

Used more descriptive name, rather than insights-logger.

[swebberuk]

No longer specify "handlers": ["console"] and "propagate": False - instead let them propagate up and be handled by the root logger, which is configured to use "handlers": ["console"].

[swebberuk]

Keeping "filters": ["suppress_duplicate_exceptions"] to avoid duplicate logging of 500 errors that will of been logged separately by ExceptionLoggingMiddleware