# Support Datadog with Fargate

**URL:** <https://community.convox.com/t/support-datadog-with-fargate/642>\
**Category:** Feature Requests\
**Created:** [November 4, 2019, 7:20am UTC](https://community.convox.com/t/support-datadog-with-fargate/642 "2019-11-04T07:20:20Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![sam](https://avatars.discourse-cdn.com/v4/letter/s/5f9b8f/32.png) [@sam](https://community.convox.com/u/sam)\
**Post date:** [January 6, 2020, 8:31am UTC](https://community.convox.com/t/support-datadog-with-fargate/642/2 "2020-01-06T08:31:44Z")

</div>

So its been a while since i submitted this and I figure I should get off my butt and fix my own problems… So if I was to implement this feature myself so I can offer it as a PR on the rack repo, is there any particular objection to a fargate specific configuration option?

My current thought is adding an array to `convox.yml` under/in the `services:` yaml dict, called something like `fargate-sidecars` that would be ignored if the Fargate template parameter is false and would connect some config options, to a section of the cloudformation template `service.json.tmpl` that contains the necessary for correctly configuring it the way DataDog recommend.

Any advice/input from @ddollar / @ed_convox / other Convox people, would be most appreciated.

---

_[View the full topic](https://community.convox.com/t/support-datadog-with-fargate/642)._