Uploaded image for project: 'OpenShift Request For Enhancement'
  1. OpenShift Request For Enhancement
  2. RFE-4911

Allow Collector to set retention policy in Cloudwatch

XMLWordPrintable

    • Icon: Feature Request Feature Request
    • Resolution: Unresolved
    • Icon: Major Major
    • None
    • None
    • Logging
    • None
    • False
    • None
    • False
    • Not Selected
    • 0
    • 0% 0%

      On  [1] the credential request for log forwarding is set to configure:

      logs:PutLogEvents 
      logs:CreateLogGroup 
      logs:PutRetentionPolicy 
      logs:CreateLogStream 
      logs:DescribeLogGroups 
      logs:DescribeLogStreams 
      

      However, there seems to be no way to set the policy, policy settings seem to be only available for Lokiy and ES

      CU own comment:

      It would be greatly appreciated if the log retention could be set some way in the pipeline. 
      
      We have set the retentions manually while developing, but for production, as it creates new log groups per namespace and namespaces come and go, it means a lot of manual labor. If the logging doesn't support setting the retention, we most likely have to develop some sort of tool that periodically scans our log groups and sets the retention. As such this can also be translated to a feature request, in case it isn't supported yet.

       

      [1] https://docs.openshift.com/container-platform/4.13/logging/log_collection_forwarding/log-forwarding.html#cluster-logging-collector-log-forward-sts-cloudwatch_log-forwarding

       

            jamparke@redhat.com Jamie Parker
            rhn-support-vmedina1 Victor Medina
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: