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 alarm metric dimension CacheClusterId #62

Closed
wants to merge 4 commits into from

Conversation

chelomontilla
Copy link

@chelomontilla chelomontilla commented Feb 17, 2020

what

  • Update CacheClusterId dimension of the alarms

why

  • The current dimension doesn't match the right cluster id

references

Copy link
Contributor

@maximmi maximmi left a comment

Choose a reason for hiding this comment

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

@chelomontilla please, try to provide CacheNodeId dimension as well as stated in documentation here and see if it will help.

@chelomontilla
Copy link
Author

@maximmi I did an aws elasticache describe-cache-clusters and the output doesn't display any CacheNodeId.
Here the output:

{
   "CacheClusterId":"my-cluster-cache-001",
   "ReplicationGroupId":"my-cluster-cache",
   "CacheClusterStatus":"available",
   "SnapshotRetentionLimit":0,
   "ClientDownloadLandingPage":"https://console.aws.amazon.com/elasticache/home#client-download:",
   "PendingModifiedValues":{

   },
   "Engine":"redis",
   "CacheSecurityGroups":[

   ],
   "NumCacheNodes":1,
   "AuthTokenLastModifiedDate":"2020-02-24T08:35:42.379Z",
   "AutoMinorVersionUpgrade":true,
   "TransitEncryptionEnabled":true,
   "SecurityGroups":[
      {
         "Status":"active",
         "SecurityGroupId":"sg-xxxxxxxx"
      }
   ],
   "CacheNodeType":"cache.t2.small",
   "PreferredMaintenanceWindow":"wed:03:00-wed:04:00",
   "CacheSubnetGroupName":"my-cluster-cache",
   "AuthTokenEnabled":true,
   "AtRestEncryptionEnabled":false,
   "EngineVersion":"5.0.6",
   "CacheClusterCreateTime":"2020-01-15T11:55:02.665Z",
   "PreferredAvailabilityZone":"eu-west-1a",
   "SnapshotWindow":"06:30-07:30",
   "NotificationConfiguration":{
      "TopicStatus":"active",
      "TopicArn":"arn:aws:sns:eu-west-1:xxxxxxxxxxx:xxxxxxxxxxxxxxxxxxx"
   },
   "CacheParameterGroup":{
      "CacheNodeIdsToReboot":[

      ],
      "CacheParameterGroupName":"my-cluster-cache",
      "ParameterApplyStatus":"in-sync"
   }
}

@osterman
Copy link
Member

/test all

1 similar comment
@jamengual
Copy link
Contributor

/test all

@jamengual
Copy link
Contributor

/rebuild-readme

@chelomontilla chelomontilla requested a review from a team as a code owner November 9, 2020 20:47
@chelomontilla chelomontilla requested review from adamcrews and woz5999 and removed request for a team November 9, 2020 20:47
@jamengual
Copy link
Contributor

@chelomontilla can you rebase from master, please?

@mergify
Copy link
Contributor

mergify bot commented Dec 21, 2020

This pull request is now in conflict. Could you fix it @chelomontilla? 🙏

@nitrocode nitrocode requested review from a team as code owners August 12, 2021 23:15
@mergify mergify bot dismissed maximmi’s stale review August 12, 2021 23:15

This Pull Request has been updated, so we're dismissing all reviews.

@nitrocode
Copy link
Member

Looks like this was fixed by a previous PR.

@nitrocode nitrocode closed this Aug 12, 2021
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.

Cloudwatch alarms insufficient data
7 participants