You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It is now possible to configure alerts in the Librato provider, which is very useful. However, sometimes we need to alert based on a composite metric. We must create the composite metric manually in the "metrics" section of the Librato admin and give it a name. We can then use the name to create the librato_alert resource.
It would be nice to be able to specify the composite metric in Terraform configuration as well, via some sort of librato_metric or librato_composite_metric resource. (The former naming might make sense if the resource would also allow setting default attributes on non-composite metrics, but that's a different request really.)
The text was updated successfully, but these errors were encountered:
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.
ghost
locked and limited conversation to collaborators
Apr 10, 2020
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
It is now possible to configure alerts in the Librato provider, which is very useful. However, sometimes we need to alert based on a composite metric. We must create the composite metric manually in the "metrics" section of the Librato admin and give it a name. We can then use the name to create the
librato_alert
resource.It would be nice to be able to specify the composite metric in Terraform configuration as well, via some sort of
librato_metric
orlibrato_composite_metric
resource. (The former naming might make sense if the resource would also allow setting default attributes on non-composite metrics, but that's a different request really.)The text was updated successfully, but these errors were encountered: