Optional
requestFactory: AWSLogsIntegrationApiRequestFactoryOptional
responseProcessor: AWSLogsIntegrationApiResponseProcessorPrivate
configurationPrivate
requestPrivate
responseThe request object
Optional
options: ConfigurationTest if permissions are present to add log-forwarding triggers for the
given services and AWS account. Input is the same as for EnableAWSLogServices
.
Done async, so can be repeatedly polled in a non-blocking fashion until
the async request completes.
created
when it's checking if the permissions exists
in the AWS account.waiting
while checking.checked and ok
if the Lambda exists.error
if the Lambda does not exist.The request object
Optional
options: ConfigurationAttach the Lambda ARN of the Lambda created for the Datadog-AWS log collection to your AWS account ID to enable log collection.
The request object
Optional
options: ConfigurationDelete a Datadog-AWS logs configuration by removing the specific Lambda ARN associated with a given AWS account.
The request object
Optional
options: ConfigurationEnable automatic log collection for a list of services. This should be run after running CreateAWSLambdaARN
to save the configuration.
The request object
Optional
options: ConfigurationList all Datadog-AWS Logs integrations configured in your Datadog account.
Optional
options: ConfigurationGet the list of current AWS services that Datadog offers automatic log collection. Use returned service IDs with the services parameter for the Enable an AWS service log collection API endpoint.
Optional
options: ConfigurationGenerated using TypeDoc
Test if permissions are present to add a log-forwarding triggers for the given services and AWS account. The input is the same as for Enable an AWS service log collection. Subsequent requests will always repeat the above, so this endpoint can be polled intermittently instead of blocking.