datadog | Dogstatsd client -

Create a composite monitor that triggers on your two queries, one with the count threshold and one with the percentage threshold.

You can't. Per the docs, "Tags are converted to lowercase."

https://docs.datadoghq.com/getting_started/tagging/#defining-tags

After some digging I found there is an option you can enable via the init script called enable_query_name_tag which is disabled by default as it can cause there to be a ton of tags created when you are not using query names.

The modification is shown here:

A way around this is to have the file be owned by a non-root user. This can be done by calling cron -f inside of a startup script from CMD after switching users.

At the end of my Dockerfile

I figured out part of the answer, by simply skipping all GET requests:

In theory you could Secret as a environment variable, and pass it to a Pod using ConfigMap.

Two things must be true in order for Terraform to be able to find a particular provider:

1. The .terraform.lock.hcl file must specify a selected version for that provider, and the allowed plugin checksums for that version.
2. There must be a package for that selected version in .terraform/providers -- the local plugin cache directory -- which matches one of the checksums.

From what you shared it seems like the second of these is being handled by you passing the cache between steps using features of your CI system.

In order for the first to be true though, you'll need to run terraform init on your development machine in order to generate the .terraform.lock.hcl file and then check that file into version control as part of your configuration, which will hopefully then make your CI system place it in the right place as a normal part of checking out the source code.

When running terraform init in a non-interactive environment like this I would suggest adding the -lockfile=readonly option, which will cause Terraform to fail with an error if the lock file has become inconsistent with the rest of the configuration. That'll then allow your CI system to catch this problem early in the first step and return an explicit error about it, whereas in your current workflow terraform init can update the lock file itself but that then doesn't carry forward to the other steps, causing strange downstream errors.

API keys do not need to be replaced when a user is deleted. They belong to your entire account, and if the creator of the tag is deleted, the API key still works just fine. API keys are like the password to your organization, and are used for submitting data.

https://docs.datadoghq.com/account_management/api-app-keys/#api-keys

Application keys are used for automating behaviors in your account. Anything a user can do in the account like create a dashboard or edit a monitor, the application key will be required for when using the API. Application keys are tied to a specific user and will inherit all the permissions of that user. So if that user does not have the ability to edit dashboards, neither will the Application Key.

You can avoid the issue of general automation tasks being tied to a specific human by utilizing service accounts. Service accounts are meant to be robotic users, which can be provided roles and create application keys. They should be linked to a common distribution list that your team has access to so it's not tied to a single person.

Got it! After replacing all ILogger with ILogger and removing the line builder.Services.AddSingleton(sp => new SerilogLoggerProvider(Log.Logger, true)); everything worked as expected.