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

fix: top-level ELB error metric and logs, downscale to min capacities #592

Merged
merged 14 commits into from
Mar 25, 2024

Conversation

chris13524
Copy link
Member

@chris13524 chris13524 commented Mar 22, 2024

Description

  • Add ELB errors to top of the Grafana like in Notify Server
  • Add other ELB metrics to the bottom
  • Add error logs from CloudWatch to the top of the Grafana like in Notify Server
  • Downscale everything to min-capacities on staging
  • Upgrade to latest version of grafonnet-lib
  • Switch to grafonnet-lib Redis panels because there was some breaking change
  • Disable alarms on prod staging
  • Rename just amigood to just devloop like in other repos e.g. Notify Server

How Has This Been Tested?

Not tested

Due Diligence

  • Breaking change
  • Requires a documentation update
  • Requires a e2e/integration test update

@chris13524 chris13524 changed the title fix: top-level error metric fix: top-level error metric, downscale to min capacities Mar 22, 2024
@chris13524 chris13524 changed the title fix: top-level error metric, downscale to min capacities fix: top-level ELB error metric and logs, downscale to min capacities Mar 22, 2024
@chris13524 chris13524 marked this pull request as ready for review March 22, 2024 21:06
Comment on lines +60 to +61
// panels.app.http_request_rate(ds, vars) { gridPos: pos._4 },
// panels.app.http_request_latency(ds, vars) { gridPos: pos._4 },
Copy link
Member Author

Choose a reason for hiding this comment

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

These panels were specific to Notify Server, but leaving them here as a reminder to put request rate and request latency up here at the top as those are important high-level metrics.

Copy link
Member Author

Choose a reason for hiding this comment

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

Opened issue: #593

@@ -47,7 +47,7 @@ curl -X POST "http://localhost:3000/v1?chainId=eip155:1&projectId=someid" --data
## Testing

```bash
just amigood
just devloop

Choose a reason for hiding this comment

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

why the name change?

Copy link
Member Author

Choose a reason for hiding this comment

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

See PR description

Choose a reason for hiding this comment

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

amigood makes more sense than devloop imo but it's fine

Copy link
Member Author

Choose a reason for hiding this comment

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

The idea was "am I good" to commit but it was awkward to type and the concept of a "developer loop" is more familiar to people.

@DGBgithub

This comment was marked as off-topic.

@chris13524 chris13524 merged commit 7cf125d into master Mar 25, 2024
32 checks passed
@chris13524 chris13524 deleted the fix/top-level-error-metric branch March 25, 2024 13:30
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.

3 participants