Skip to content

Commit 5356203

Browse files
Merge pull request #10067 from feddovanede/patch-984510
Clarify Datadog host billing
2 parents d7f49dc + 5e53986 commit 5356203

1 file changed

Lines changed: 9 additions & 0 deletions

File tree

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

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -227,6 +227,15 @@ 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
231+
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).
238+
230239
## Read More
231240

232241
* [Monitor Your Mendix Apps with Datadog](https://www.mendix.com/blog/monitor-your-mendix-apps-with-datadog/) – a Mendix blog about the capabilities of Datadog and using Datadog with Mendix

0 commit comments

Comments
 (0)