AWS CloudWatch logs exporter should have an option to automatically create log group/stream #4714
Comments
errordeveloper
changed the title
|
xref #4721 |
|
Being able to create external resources is rather powerful thing, I worry adding something like this could mean that users could spawn too many resources for them to be easily managed, maintained and leading to them being orphaned. |
|
@alolita could you assign me to this? |
|
Assigned @aateeqi |
|
This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping |
|
Pinging code owners for exporter/awscloudwatchlogs: @boostchicken. See Adding Labels via Comments if you do not have permissions to add labels yourself. |
|
This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
|
Hey @aateeqi , Is this done? |
|
This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
|
Creating a new log group and setting retention policies is now supported |
**Description:** Recreate #23820 with updates and fixes Original PR body ``` Description: Replaced old example in documentation with a new one. Also clarified some important information for the user, such as the fact that log groups and log streams are created automatically, and that Resource ARNs are not supported. Additionally, updated some descriptions of configs. Link to tracking Issue: #4714 Testing: N/A Documentation: Added a new example in documentation that shows how to configure the Exporter to send EMF Logs Clarified that log group and log stream are automatically created for user Stated Resource ARN isn't supported in the Additional Notes section Updated some descriptions of configs ``` --------- Co-authored-by: Zahid Mirza <zam19@rogers.com> Co-authored-by: bryan-aguilar <46550959+bryan-aguilar@users.noreply.github.com>
|
Looks like there is no possibility create log streams with unique names automatically. They should be preconfigured, and a proper name should be set to a config. Which is rather inconvenient for a Kubernetes setup with multiple dynamic containers. A related PR adding a possibility to parameterise stream names was never merged: #12179 |
Is your feature request related to a problem? Please describe.
Currently log exporter relies on having an existing log group and log steam, it would be more convenient if auto-create option was available. Being able to set TTL would be nice also.
Describe the solution you'd like
Add an auto-create option to the exporter config, it would be nice if it was enabled by default.
Describe alternatives you've considered
An alternative requires user to either go to console and click around, or use another tool to automate it. For getting started this seems like extra work one shouldn't have to do. Also, in some cases user might want to generate collector configuration and shouldn't need to worry about CloudWatch setup.
The text was updated successfully, but these errors were encountered: