-
Notifications
You must be signed in to change notification settings - Fork 9.4k
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
Add logging configuration to Prometheus #26444
Comments
I might pick it up soon. |
add cloudwatch_log_group_arn to aws_prometheus_workspace
I made a first attempt to add the cloudwatch_log_group_arn to the workspace configuration. I did not ad the log_level as it actually does not exist in the API and in the UI has values off/All. For me it seemed more clear to just make the cloudwatch_log_group_arn attribute optional. |
This functionality has been released in v4.35.0 of the Terraform AWS Provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading. For further feature requests or bug reports with this functionality, please create a new GitHub issue following the template. Thank you! |
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. |
Community Note
Description
The Amazon Managed Prometheus provides configuration to send log events to CloudWatch.
I would suggest to add two new fields on 'aws_prometheus_workspace' like:
New or Affected Resource(s)
Potential Terraform Configuration
References
The text was updated successfully, but these errors were encountered: