Skip to content

Agent not updating after scaling up instance #159

@OysterKing

Description

@OysterKing

The following slack alerts seem to be triggering based on outdated information.

The ec1-r1 cluster was scaled up manually from a t4g.medium to a t4g.large and the agent does not seem to have accounted for this.

https://xata-hq.slack.com/archives/C08EETY7VB8/p1746087356367569

For example:

Actions to take  
- Scale up the Aurora instance to a larger class to provide more memory and prevent outages.
- For example, in AWS Console or via AWS CLI, modify the DB cluster to use db.t4g.large or db.r6g.large:
 
  aws rds modify-db-instance \
    --db-instance-identifier <your-instance-identifier> \
    --db-instance-class db.t4g.large \
    --apply-immediately

Metadata

Metadata

Assignees

Labels

bugSomething isn't workingdogfoodIssues surfaced through dogfooding the agent

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions