Score:0

alarm for direct connect is showing insufficient data with terraform, how to fix that?

kr flag

I tried creating alarm for direct connect using this link.

But it is showing insufficient data, so I tried creating manually from aws console and it is working.

So, did a side by side comparison and tried following changes in dimensions.

connection_id  -> ConnectionId 
    aws_account_id -> "Account ID",AccountID,AccountId
    region         --> kept and removed 

Not fruitful, as getting same insufficient data.

Please suggest.

Tim avatar
gp flag
Tim
I generally create an alarm in the console, look at the namespace / dimension / whatever else, then put it into infrastructure as code. If you want help you'll need to provide more information, such as screenshots of the two alarms showing the details of what they're monitoring.
kr flag
fields are same now, but getting insufficient data. And I used exact steps as in the link I shared in first line.
Tim avatar
gp flag
Tim
Please edit your question to clearly say what you're trying to achieve, in plain language. Also include screenshots. eg "I want to be alerted when DC is unavailable". You said "alarm" but on which metric? You are best to get it going in the console before Terraform.
kr flag
all those details are in the link I shared in the question
mangohost

Post an answer

Most people don’t grasp that asking a lot of questions unlocks learning and improves interpersonal bonding. In Alison’s studies, for example, though people could accurately recall how many questions had been asked in their conversations, they didn’t intuit the link between questions and liking. Across four studies, in which participants were engaged in conversations themselves or read transcripts of others’ conversations, people tended not to realize that question asking would influence—or had influenced—the level of amity between the conversationalists.