# Deploy external monitors using Monaco V2

**URL:** <https://community.dynatrace.com/t/deploy-external-monitors-using-monaco-v2/40360>\
**Category:** Synthetic Monitoring\
**Tags:** monaco, synthetic-monitoring\
**Created:** [June 23, 2023, 3:23pm UTC](https://community.dynatrace.com/t/deploy-external-monitors-using-monaco-v2/40360 "2023-06-23T15:23:01Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![f098wr09w0e9fdw](https://avatars.discourse-cdn.com/v4/letter/f/c5a1d2/32.png) [@f098wr09w0e9fdw](https://community.dynatrace.com/u/f098wr09w0e9fdw)\
**Post date:** [June 23, 2023, 3:23pm UTC](https://community.dynatrace.com/t/deploy-external-monitors-using-monaco-v2/40360/1 "2023-06-23T15:23:01Z")

</div>

Hello Dynatrace community,

I’m currently using Dynatrace Monaco v2.3.0 to manage my Dynatrace configuration and I’m trying to create an external monitor of type SYNTHETIC. (API&nbsp;/api/v1/synthetic/ext/tests ). However, it seems that Monaco is not currently supporting the creation of external monitors.

I have reviewed the documentation ([list of supported apis in monaco](https://github.com/Dynatrace/dynatrace-configuration-as-code/blob/main/api_coverage.md?plain=1#L91)) and searched through community forums to confirm that this is a current limitation. However, before I close this case, I was wondering if someone from the support team could let me know if there is a way to create external monitors using Monaco, or if this is a feature expected to be added in a future release.

Could you please confirm whether this is a known limitation of Monaco or if there is a workaround?

Thanks!

---

<div class="post-metadata">

**Author:** ![AntonioSousa](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/antoniosousa/32/50_2.png) [@AntonioSousa](https://community.dynatrace.com/u/AntonioSousa)\
**Post date:** [June 23, 2023, 5:21pm UTC](https://community.dynatrace.com/t/deploy-external-monitors-using-monaco-v2/40360/2 "2023-06-23T17:21:10Z")

</div>

[@f098wr09w0e9fdw](https://community.dynatrace.com/user/59186),

Slightly different, check out how it can be done with containerized auto-scalable private location deployment, eliminating the need to deploy individual synthetic ActiveGates on separate hosts or virtual machines:

> **[Dynatrace delivers flexible and scalable Kubernetes native synthetic private...](https://www.dynatrace.com/news/blog/dynatrace-delivers-flexible-and-scalable-kubernetes-native-synthetic-private-locations/)**
>
> Dynatrace now offers containerized auto-scalable private location deployment, eliminating the need to deploy individual synthetic ActiveGates on separate hosts or virtual machines.

---

<div class="post-metadata">

**Author:** ![AntonPineiro](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/antonpineiro/32/49_2.png) [@AntonPineiro](https://community.dynatrace.com/u/AntonPineiro)\
**Post date:** [June 25, 2023, 9:32pm UTC](https://community.dynatrace.com/t/deploy-external-monitors-using-monaco-v2/40360/3 "2023-06-25T21:32:18Z")

</div>

Hi,

I can see that API in the [documentation](https://www.dynatrace.com/support/help/shortlink/configuration-as-code-supported-configuration#configs):

 ![AntonPineiro_0-1687728616377.png](https://global.discourse-cdn.com/dynatrace/original/3X/b/7/b7fbe4c68c29e9b9d5f6698488ddce93f0f4b990.png)

I would suggest to create one manually, download configuration using Monaco, and having a look to existing YAML and JSON files.

Best regards

---

<div class="post-metadata">

**Author:** ![f098wr09w0e9fdw](https://avatars.discourse-cdn.com/v4/letter/f/c5a1d2/32.png) [@f098wr09w0e9fdw](https://community.dynatrace.com/u/f098wr09w0e9fdw)\
**Post date:** [June 26, 2023, 9:04am UTC](https://community.dynatrace.com/t/deploy-external-monitors-using-monaco-v2/40360/4 "2023-06-26T09:04:28Z")

</div>

Hi&nbsp;[@AntonioSousa](https://community.dynatrace.com/user/17213)

Thank you very much for your response! I have been reading the documentation you suggested and I don’t think it will fit my current architecture.

In my case, the tests are executed from a [third-party source](https://www.dynatrace.com/support/help/dynatrace-api/environment-api/synthetic/third-party-synthetic). So, I think that defining a new location within a cluster will not help me because I don’t want Dynatrace to execute my tests. Instead, I want the third party to push the test data to Dynatrace (&nbsp;[API&nbsp;/api/v1/synthetic/ext/tests](https://www.dynatrace.com/support/help/dynatrace-api/environment-api/synthetic/third-party-synthetic/post-third-party-monitors) ). I&nbsp;was wondering if there was a way to create the synthetic placeholder (id, name, url etc) using Monaco and then send the test run data updates using the API.

Thank you very much for your response, it has helped me understand how containerized&nbsp;auto-scalable private locations work and how to use them in the future.

---

<div class="post-metadata">

**Author:** ![Julius\_Loman](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/julius_loman/32/51_2.png) [@Julius\_Loman](https://community.dynatrace.com/u/Julius_Loman)\
**Post date:** [June 26, 2023, 9:28am UTC](https://community.dynatrace.com/t/deploy-external-monitors-using-monaco-v2/40360/5 "2023-06-26T09:28:02Z")

</div>

[@f098wr09w0e9fdw](https://community.dynatrace.com/user/59186)&nbsp;what kind of configuration to create third-party synthetic monitors do you want to push using configuration as code?

3rd party monitors actually are not “configured”, you actually just push the data and monitors are created automatically.
