Add logging for container instances

[JimMadge]

✅ Checklist

• You have given your pull request a meaningful title (e.g. Enable foobar integration rather than 515 foobar).
• You are targeting the appropriate branch. If you're not certain which one this is, it should be develop.
• Your branch is up-to-date with the target branch (it probably was when you started, but it may have changed since then).

🚦 Depends on

⤴️ Summary

🌂 Related issues

Contributes to #1922

🔬 Tests

Tested in a new deployment, screenshots below.

[github-actions]

Coverage report

Click to see where and how coverage changed

File	Statements	Missing	Coverage	Coverage (new stmts)	Lines missing
data_safe_haven/infrastructure/programs
declarative_sre.py					213
data_safe_haven/infrastructure/programs/sre
apt_proxy_server.py					39
clamav_mirror.py					36
gitea_server.py					60
hedgedoc_server.py					63
identity.py					45
remote_desktop.py					70
software_repositories.py					44
user_services.py					63
Project Total

This report was generated by python-coverage-comment-action

[JimMadge]

Logs are ingested into the log analytics workspace.
There are event logs from the container instance (container started, image pulled, bootloop occurring) and not the output of the container process.

And container process logs

[jemrobinson]

LGTM and this is definitely worth merging on its own. However, is it possible to get the container logs into the workspace too? They're more interesting than logging when containers turn on and off (which is unlikely to be very useful to many people).

[JimMadge]

LGTM and this is definitely worth merging on its own. However, is it possible to get the container logs into the workspace too? They're more interesting than logging when containers turn on and off (which is unlikely to be very useful to many people).

Yes, they are there too 🚀

[jemrobinson]

@JimMadge: does this include logs from terminated containers (which are otherwise inaccessible)?

[JimMadge]

Yes, as long as the workspace gets the log it is kept there.