-
Notifications
You must be signed in to change notification settings - Fork 1.3k
Conversation
It is always triggered. See https://www.bwplotka.dev/2019/golang-memory-monitoring.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM but please file an issue on me for the fact that we cannot monitor gitserver memory usage at all - that sucks badly
monitoring/git_server.go
Outdated
@@ -92,7 +92,6 @@ func GitServer() *Container { | |||
Rows: []Row{ | |||
{ | |||
sharedContainerCPUUsage("gitserver"), | |||
sharedContainerMemoryUsage("gitserver"), |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This doesn't get triggered (and probably shouldn't, since its threshold is at 99%) - I think we should leave this one in, and it would address @slimsag 's comment about being unable to see any memory stats
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Agree with keeping this as @bobheadxi said 👍
The issue I filed / was talking about is a bit separate (about alerting, not just being unable to see any memory stats).
Filed an issue: https://github.com/sourcegraph/sourcegraph/issues/12685 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Some updates I made:
- add back container memory usage (current)
- add lower-bound 7d memory usage
- fix wording for provisioning solutions (!!!!)
https://github.com/sourcegraph/deploy-sourcegraph-dot-com/pull/3125 will remove the relevant silence
It is always triggered. See https://www.bwplotka.dev/2019/golang-memory-monitoring.