Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Persist logs in a MongoDB for caching purposes #7

Open
5 of 6 tasks
alex855k opened this issue Nov 15, 2018 · 2 comments
Open
5 of 6 tasks

Persist logs in a MongoDB for caching purposes #7

alex855k opened this issue Nov 15, 2018 · 2 comments
Assignees
Labels
in progress priority: medium Priority for issues which should be implemented. type: infrastructure Task related to improvement of infrastructure. type: story Feature to be implemented based on a user story description
Milestone

Comments

@alex855k
Copy link
Contributor

alex855k commented Nov 15, 2018

📋 User story

As a system I want to persist logs in a MongoDB for caching purposes

Description

It's a requirement to cache the logs. So in case of a system failure, it's resilient and doesn't have to be dependent on data from Mono Solutions databases.

Prerequisites

Acceptance Criteria

  • The MongoDB should be elastic replicas, setup master and a slave as minimum.
  • The image solution should be stored on docker hub repository and be used when booting up the
    docker file.
  • Logs errors and action in var/main.log.
@alex855k alex855k added type: infrastructure Task related to improvement of infrastructure. type: story Feature to be implemented based on a user story description labels Nov 20, 2018
@alex855k alex855k changed the title Setup mongoDB docker image As a system I want to persist logs in a MongoDB for caching purposes Nov 20, 2018
@alex855k alex855k changed the title As a system I want to persist logs in a MongoDB for caching purposes Persist logs in a MongoDB for caching purposes Nov 21, 2018
@alex855k alex855k added priority: high Priority for issues which MUST BE implemented. priority: medium Priority for issues which should be implemented. backlog sprint backlog in progress and removed priority: high Priority for issues which MUST BE implemented. backlog sprint backlog labels Nov 21, 2018
@alex855k alex855k added this to the Sprint 2 milestone Nov 23, 2018
@davi7725
Copy link
Member

This task is 8 hours but has been here almost for 2 sprints? Just wondering if this is correct or if anyone is still actually actively developing it?

@alex855k
Copy link
Contributor Author

alex855k commented Dec 18, 2018

Yeah didn't branch it, it is on the refiner service branch.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
in progress priority: medium Priority for issues which should be implemented. type: infrastructure Task related to improvement of infrastructure. type: story Feature to be implemented based on a user story description
Projects
None yet
Development

No branches or pull requests

3 participants