-
Notifications
You must be signed in to change notification settings - Fork 381
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
Support for "enable_logs_sample" in logs monitor. #139
Comments
Any change of movement on this issue? I've just run into a problem that this would fix! You get the log alert but it's not really useful without the log itself as the alert doesn't contain and information about where the event occurred. |
Not sure when it is going to be merged... PR got moved from milestone 1.7.0 to 1.8.0. @masci can I help somehow to speed up this process ? |
Since #151 has been merged and is working correctly, this issue can be closed. |
@bkabrda it looks like wrong PR has been merged. I added https://github.com/terraform-providers/terraform-provider-datadog/pull/140 from 4.01.2019 and you merged one from 13.02.2019 https://github.com/terraform-providers/terraform-provider-datadog/pull/151. 151 does not look like it is working, gives "Error: datadog_monitor.log_errors: : invalid or unknown key: enable_logs_sample" with provider provider.datadog v1.8.0 |
@kgrodzicki I'll take a look at this, but do note that the referenced PR has been merged after the 1.8.0 version of the provider was released, so this would only work after we do next release. |
Yeah, using build of the provider from the current master branch works with the example from the original comment in this issue report. @kgrodzicki are you ok with me closing #140 as it's no longer necessary? FTR, I'm sorry for not noticing it. I should have merged your PR, because it was opened earlier, I just had not noticed. |
Terraform Version
Terraform v0.11.11
Terraform Configuration Files
See https://docs.datadoghq.com/monitors/monitor_types/log/
The text was updated successfully, but these errors were encountered: