Closed omarfakhreddine closed 1 year ago
Thanks for opening this issue. The ticket INTMDB-872 was created for internal tracking.
Hi @omarfakhreddine
We are unable to allow OPLOG_REPLICATION_LAG_TIME
metric to be setup in this context. Verified internally that this should be excluded from the documentation. We are working on removing this metric from Atlas API documentation and can be tracked via internal ticket CLOUDP-185612.
Thank you @maastha
Does this mean I will need to manually configure this alert through the Atlas UI and I won't be able to import it using Terraform and manage it that way?
@omarfakhreddine no you can still leverage Terraform for alert configuration, it is just that OPLOG_REPLICATION_LAG_TIME
parameter is not available to leverage. hope this helps to clarify. feel free to open a new issue in case you need anything else. thank you.
Terraform CLI and Terraform MongoDB Atlas Provider Version
Terraform cloud workspace version: v1.5.0 MongoDB Atlas Provider Version: v1.9.0
Terraform Configuration File
Steps to Reproduce
Expected Behavior
After applying the planned change in TFC, the run apply will succeed and create the alert in the Atlas projects
Actual Behavior
The run apply fails and returns
Error: error creating Alert Configuration
Debug Output
Additional Context
The metric name should be correct based on the Atlas API docs