# Help me, with synthetic monitor with hearbeat and zip url doesn't work

**URL:** <https://discuss.elastic.co/t/help-me-with-synthetic-monitor-with-hearbeat-and-zip-url-doesnt-work/312495>\
**Category:** Synthetics\
**Created:** [August 19, 2022, 6:55pm UTC](https://discuss.elastic.co/t/help-me-with-synthetic-monitor-with-hearbeat-and-zip-url-doesnt-work/312495 "2022-08-19T18:55:47Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![odelacruzc](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/odelacruzc/32/48992_2.png) [@odelacruzc](https://discuss.elastic.co/u/odelacruzc)\
**Post date:** [August 19, 2022, 6:55pm UTC](https://discuss.elastic.co/t/help-me-with-synthetic-monitor-with-hearbeat-and-zip-url-doesnt-work/312495/1 "2022-08-19T18:55:47Z")

</div>

Please, help me, what another info do you need?

```auto
{"log.level":"info","@timestamp":"2022-08-19T18:52:57.620Z","log.origin":{"file.name":"source/local.go","file.line":146},"message":"Ran /usr/share/heartbeat/.node/node/bin/npm install (254) got 'npm ERR! code ENOENT\nnpm ERR! syscall open\nnpm ERR! path /tmp/elastic-synthetics-unzip-3062228563/package.json\nnpm ERR! errno -2\nnpm ERR! enoent ENOENT: no such file or directory, open '/tmp/elastic-synthetics-unzip-3062228563/package.json'\nnpm ERR! enoent This is related to npm not being able to find a file.\nnpm ERR! enoent \n\nnpm ERR! A complete log of this run can be found in:\nnpm ERR! /usr/share/heartbeat/.npm/_logs/2022-08-19T18_52_56_937Z-debug-0.log\n': (exit status 254) as (1000/1000)","service.name":"heartbeat","ecs.version":"1.6.0"}
{"log.level":"debug","@timestamp":"2022-08-19T18:52:57.622Z","log.logger":"processors","log.origin":{"file.name":"processing/processors.go","file.line":210},"message":"Publish event: {\n \"@timestamp\": \"2022-08-19T18:52:57.622Z\",\n \"@metadata\": {\n \"beat\": \"heartbeat\",\n \"type\": \"_doc\",\n \"version\": \"8.3.3\"\n },\n \"ecs\": {\n \"version\": \"8.0.0\"\n },\n \"agent\": {\n \"name\": \"3a21a0c3dc7a\",\n \"type\": \"heartbeat\",\n \"version\": \"8.3.3\",\n \"ephemeral_id\": \"4306b2b4-a01b-49c0-8dab-d8efd90bca04\",\n \"id\": \"bcee9be4-34cc-482b-81cf-b9c4a4d0d664\"\n },\n \"monitor\": {\n \"timespan\": {\n \"gte\": \"2022-08-19T18:52:57.622Z\",\n \"lt\": \"2022-08-19T18:55:57.622Z\"\n },\n \"type\": \"browser\",\n \"project\": {\n \"name\": \"CANVIA-AULAVIRTUAL\",\n \"id\": \"AULAVIRTUAL\"\n }\n },\n \"alp\": 103333,\n \"cliente\": \"CANVIA_02\",\n \"event\": {\n \"dataset\": \"browser\"\n },\n \"observer\": {\n \"ip\": [\n \"172.17.0.2\"\n],\n \"mac\": [\n \"02:42:ac:11:00:02\"\n],\n \"hostname\": \"3a21a0c3dc7a\",\n \"geo\": {\n \"continent_name\": \"South America\",\n \"city_name\": \"Lima\",\n \"name\": \"Lima\"\n }\n }\n}","service.name":"heartbeat","ecs.version":"1.6.0"}

```

---

<div class="post-metadata">

**Author:** ![kyungeunni](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kyungeunni/32/125539_2.png) [@kyungeunni](https://discuss.elastic.co/u/kyungeunni)\
**Post date:** [August 22, 2022, 12:13pm UTC](https://discuss.elastic.co/t/help-me-with-synthetic-monitor-with-hearbeat-and-zip-url-doesnt-work/312495/2 "2022-08-22T12:13:11Z")

</div>

Hi @odelacruzc.

The error message indicates that it couldn't find the `package.json` in the remote endpoint.  
Can you confirm that your remote endpoint has been properly set up as a [NPM project](https://docs.npmjs.com/cli/v7/commands/npm-init)?

You can find the documentation [here](https://www.elastic.co/guide/en/beats/heartbeat/current/monitor-browser-options.html#monitor-source-zipurl), and also you can take a look at a few examples how to set up your synthetics test project [here](https://github.com/elastic/synthetics-demo/tree/main/todos/synthetics-tests).

---

<div class="post-metadata">

**Author:** ![odelacruzc](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/odelacruzc/32/48992_2.png) [@odelacruzc](https://discuss.elastic.co/u/odelacruzc)\
**Post date:** [August 22, 2022, 6:16pm UTC](https://discuss.elastic.co/t/help-me-with-synthetic-monitor-with-hearbeat-and-zip-url-doesnt-work/312495/3 "2022-08-22T18:16:48Z")

</div>

Hi @kyungeunni I can set my monitor with zip url. but doesn't see in uptime, I only can see the bar in time series T\_T

 ![test01](https://us1.discourse-cdn.com/elastic/original/3X/9/e/9ee7a2ca344484bca95fed3faf0b6da5c203f925.png)

---

<div class="post-metadata">

**Author:** ![Andrew\_Cholakian1](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/andrew_cholakian1/32/3612_2.png) [@Andrew\_Cholakian1](https://discuss.elastic.co/u/Andrew_Cholakian1)\
**Post date:** [August 26, 2022, 4:31pm UTC](https://discuss.elastic.co/t/help-me-with-synthetic-monitor-with-hearbeat-and-zip-url-doesnt-work/312495/4 "2022-08-26T16:31:16Z")

</div>

Apologies for the delay @odelacruzc , I'd strongly recommend moving away from zip\_url monitors which are tricky to troubleshoot. In the Elastic stack 8.4.0 we support [`project`](https://www.elastic.co/guide/en/observability/current/synthetic-run-tests.html) monitors, which let you push monitors into the elastic stack. These can run locally on heartbeat nodes, or on fleet / elastic agent with the [private locations](https://www.elastic.co/guide/en/observability/current/uptime-set-up-choose-agent.html#private-locations) feature in 8.4.0

With project monitors this category of error you're seeing goes away.

I've opened [[Synthetics] Remove all references to zip\_url monitors · Issue #2149 · elastic/observability-docs · GitHub](https://github.com/elastic/observability-docs/issues/2149) to track the docs change here.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [September 19, 2022, 4:32pm UTC](https://discuss.elastic.co/t/help-me-with-synthetic-monitor-with-hearbeat-and-zip-url-doesnt-work/312495/5 "2022-09-19T16:32:07Z")

</div>

This topic was automatically closed 24 days after the last reply. New replies are no longer allowed.
