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
There is currently no way to differentiate log request size from the certificate request size. The Python script does not differentiate the two and this is a problem in our environment. for example we have over 10k certificates which requires us to set the req_limit to 50k in order for the Datadog agent to accurately read and report what we have. However the req_limit is also used for the cert issuance time metrics, this then pulls the last 50k log objects which, for us will span a time period of over 12 hours. We don't want to know the average request time over twelve hours we need to be able to see the overage over say 10 minutes. Having a separate field for this would give us the ability to customize the Datadog agent to our needs.
The text was updated successfully, but these errors were encountered:
There is currently no way to differentiate log request size from the certificate request size. The Python script does not differentiate the two and this is a problem in our environment. for example we have over 10k certificates which requires us to set the req_limit to 50k in order for the Datadog agent to accurately read and report what we have. However the req_limit is also used for the cert issuance time metrics, this then pulls the last 50k log objects which, for us will span a time period of over 12 hours. We don't want to know the average request time over twelve hours we need to be able to see the overage over say 10 minutes. Having a separate field for this would give us the ability to customize the Datadog agent to our needs.
The text was updated successfully, but these errors were encountered: