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.

Sign up for GitHub

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

Jump to bottom

Spike: Research redis storage capability/monitoring #1283

Open
exalate-issue-sync bot opened this issue Jan 15, 2025 · 0 comments
Open

Spike: Research redis storage capability/monitoring #1283

exalate-issue-sync bot opened this issue Jan 15, 2025 · 0 comments
Assignees
@toddlees
Labels
DevOps

Comments

@exalate-issue-sync
Copy link

We currently use redis-3 node, which has 512 mb of storage (docs: https://cloud.gov/docs/services/aws-elasticache/ ). Running out of storage can cause production issues - we should get a sense of how to monitor redis storage and make sure we’re expiring objects.

QA Notes

null

DEV Notes

null

Design

null

See full ticket and images here: FECFILE-1950
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@toddlees toddlees

Labels
DevOps
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@toddlees