DiamondLightSource / DiamondLightSource/mx-bluesky

Properly configure debug logging for plans running with BlueAPI

Open
#1,208 2 comments 0 reactions 0 assignees View on GitHub
Dominant language
Python
Stars
4
Forks
5
Avg merge
1d 30m
Merged PRs (30d)
2

Description

The BlueAPI helm chart currently has some [simple configuration](https://github.com/DiamondLightSource/blueapi/blob/08334bc62e4b7ea19219b34e0b109d7bfa66aed9/helm/blueapi/values.yaml#L209) for logging. BlueAPI configures the root logger, which is then automatically used by our dodal+bluesky+ophyd logs.

Our debug logs are too noisy to be sending to graylog, so we need a way to save our debug logs to a file when there's an exception.
Using k8's for logs also isn't suitable since it deletes them after 2 pod restarts.

Proposed short term solution:
- Run dodal's `set_up_DEBUG_memory_handler` in our blueapi plan entry-points
- In ixx-values.yaml, mount the debug logging location to a PVC
This will effectively give us the same behaviour as Hyperion has

Longer-term solution:
See https://github.com/DiamondLightSource/mx-bluesky/issues/1213

## Acceptance Criteria
- All of our debug logs are retrievable when running BlueAPI

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.