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

chore: Add Recon #2260

Merged
merged 1 commit into from
Oct 25, 2024
Merged

chore: Add Recon #2260

merged 1 commit into from
Oct 25, 2024

Conversation

cmaddox5
Copy link
Contributor

Memory usage seems to be higher than normal recently and we aren't sure why. Adding in a process that logs the top 20 memory usage processes every 5 minutes. Took inspiration from RTS: https://github.com/mbta/realtime_signs/blob/main/lib/engine/health.ex. Just left out network checks.

@cmaddox5 cmaddox5 requested a review from a team as a code owner October 24, 2024 15:30
@digitalcora
Copy link
Contributor

Let's test this out on dev-green and see if the resulting info seems likely to give us some insights on production. Actual implementation looks okay to me.

@cmaddox5
Copy link
Contributor Author

This provides about the same info as our Phoenix Live Dashboard but gives the advantage of getting historical context. A decent preliminary query I made is index="screens-dev-green-application" screens_process_health | bin _time span=1h | eventstats max(memory) as mem BY name, _time | table _time name mem for reference.

Copy link
Contributor

@digitalcora digitalcora left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm okay with trying this. I think we might end up wanting better visibility into the specific things within e.g. the V3 API cache that are taking up a lot of space (like which resources?), but this would tell us whether we should look there in the first place.

@cmaddox5 cmaddox5 merged commit d22dd73 into main Oct 25, 2024
14 checks passed
@cmaddox5 cmaddox5 deleted the cm/add-recon branch October 25, 2024 20:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants