SPIKE: Member Logging analysis

[davidkelliott]

User Story

As a modernisation platform engineer I need to understand logging needs and options So that I can build a logging platform

Value

We need a way to access logs for the platform, and our users to access their application infrastructure, and application logs.

This ticket is probably linked, and could be closed pending the result of this spike

Questions / Assumptions

We should reuse / align with other MoJ areas where possible.

Definition of done

• [ ] Analysis on logging options on the market
• [ ] Analysis of logging options within the moj currently available
• [ ] Discussion with other areas of the MoJ / Operations Engineering on any areas which could be reusable
• [ ] Options paper with solutions that we should spike to inform a decision.
• [ ] another team member has reviewed

Reference

How to write good user stories

[davidkelliott]

Spoke with David Read, Cloud Platform is looking to move Elastic to Loki, it's on their roadmap for early next year. https://github.com/ministryofjustice/cloud-platform/blob/main/architecture-decision-record/023-Logging.md

[davidkelliott]

We have decided to continue with the centralisation of the platform logging, but put the member logging centralisation on hold for the moment until we better understand the needs of users. We are working closer with cloud platform now and hope to find a common solution with them or operations engineering.

[dms1981]

Is this worth bringing back up in light of us having a user researcher? (Hello @ScottSeaward !)

[github-actions[bot]]

This issue is stale because it has been open 90 days with no activity.

[dms1981]

Closed this one in light of the existence of Observability Platform's existence