Skip to content

Commit 5e53986

Browse files
chore: language review
1 parent 52715c4 commit 5e53986

1 file changed

Lines changed: 7 additions & 4 deletions

File tree

content/en/docs/deployment/mendix-cloud-deploy/monitoring-with-apm/datadog-metrics.md

Lines changed: 7 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -227,11 +227,14 @@ If you have any issues related to accessing Datadog, contact their support on th
227227

228228
Metrics on Datadog can include an additional namespace, `datadog`, which contains metrics on Datadog usage.
229229

230-
### Datadog host billing
230+
### Datadog Host Billing
231231

232-
Every instance of your application will run its own Datadog agent; they will show up as separate hosts in Datadog. Single-instance applications will count as one host, multi-instance applications will count for as many hosts as instances it is scaled to. Datadog uses host-based pricing, so you will be billed for every instance of your application.
233-
In the past, when Mendix Cloud ran on Cloud Foundry, Datadog didn't always correctly identify and bill each host. On Kubernetes, this process works correctly, which might result in more hosts showing up in Datadog if your applications run on Kubernetes.
234-
You will only be billed by Datadog if your application sends metrics to Datadog. If you add a `DD_LOGS_COLLECTION_ONLY` custom environment variable with value `true`, the application will only send logs to Datadog, and you won't be billed for the host(s).
232+
Datadog uses host-based pricing, so you will be billed for every instance of your application. Each instance of your application runs its own Datadog agent and shows up as separate hosts in Datadog.
233+
234+
* A single-instance application counts as one host
235+
* A multi-instance application counts for as many hosts as it has scaled instances
236+
237+
Previously, when Mendix Cloud ran on Cloud Foundry, Datadog did not always accurately identify and bill every host. With the transition to Kubernetes, this process now works correctly and may result in more hosts showing up in Datadog for your Kubernetes-based applications. However, billing occurs only when your application sends metrics to Datadog. If you add a `DD_LOGS_COLLECTION_ONLY` custom environment variable with value `true`, the application will only send logs to Datadog, and you will not be billed for the host(s).
235238

236239
## Read More
237240

0 commit comments

Comments
 (0)