无法通过docker在多个.js/.ts文件中运行查看Kibana仪表板中的监视器向上/向下详细信息

我们运行“heartbeat.yml”文件，在“todos”文件夹路径中配置多个.js文件，并运行docker run命令，因此无法在Kibana仪表板中查看上/下监视器的详细信息，但是，当我们使用内联脚本运行heartbeat文件时，我们可以通过docker run命令在Kibana仪表板中查看上/下监视器的详细信息

要检查内联和多个文件的日志比较，内联作业运行的观察者会按如下方式记录其显示行：

2021-05-25T17:44:16.953Z INFO synthexec/synthexec.go:128 Running command: /usr/share/heartbeat/.node/node/bin/elastic-synthetics --inline --screenshots --json --network --outfd 3 in directory: ''
2021-05-25T17:44:39.690Z INFO synthexec/synthexec.go:176 Command has completed(0):

内联作业日志：

"monitor_starts":1},"scheduler":{"jobs":{"active":1},"tasks":{"active":1}}},"libbeat":{"config":{"module":{"running:0}}

多个.js文件日志：

"monitor_starts":1}},"libbeat":{"config":{"module":{"running":0}}

内联计划程序作业激活后，它将以如下方式显示：

2021-05-25T17:44:16.953Z INFO synthexec/synthexec.go:128 Running command: /usr/share/heartbeat/.node/node/bin/elastic-synthetics --inline --screenshots --json --network --outfd 3 in directory: ''
2021-05-25T17:44:39.690Z INFO synthexec/synthexec.go:176 Command has completed(0):

在此之后，我们可以通过heartbeat.yml文件中运行的内联脚本查看Kibana仪表板中的上下监控详细信息

但是，当在多个js文件中运行时，我们无法查看

"INFO synthexec/synthexec.go:128 Running command" and
"INFO synthexec/synthexec.go:176 Command has completed(0): "

详细信息，而在运行时，我们可以在日志中查看以下详细信息：

"monitor_starts":1}},"libbeat":{"config":{"module":{"running":0}},"output":{"events":{"acked":1,"active":0,"batches":1,"total":1},"read":{"bytes":5097},
"type":"elasticsearch","write":{"bytes":2860}},"pipeline":{"clients":1,"events":{"active":0,"published":1,"retry":1,"total":1},"queue":{"acked":1}}},
"system":{"cpu":{"cores":1},"load":{"1":0.05,"15":0.11,"5":0.09,"norm":{"1":0.05,"15":0.11,"5":0.09}}}}}}
2021-05-25T18:12:14.910Z INFO [monitoring] log/log.go:144 Non-zero metrics in the last 30s
"monitoring": {"metrics": {"beat":{"cgroup":{"cpuacct":{"total":{"ns":3856349}},"memory":{"mem":{"usage":{"bytes":90112}}}},"cpu":
{"system":{"ticks":60},"total":{"ticks":120,"time":{"ms":4},"value":120},"user":{"ticks":60,"time":{"ms":4}}},"handles":{"limit":{"hard":4096,"soft":1024},
"open":9},"info":{"ephemeral_id":"607833fc-eebd-4577-8a21-ed5749a8d97a","uptime":{"ms":60056}},"memstats":{"gc_next":9914592,"memory_alloc":5992064,
"memory_total":19761336,"rss":52703232},"runtime":{"goroutines":14}},"libbeat":{"config":{"module":{"running":0}},"output":{"events":{"active":0}},
"pipeline":{"clients":1,"events":{"active":0}}},"system":{"load":{"1":0.03,"15":0.1,"5":0.08,"norm":{"1":0.03,"15":0.1,"5":0.08}}}}}}

下面是我们用于此多个js文件运行的文件：

heartbeat.yml：

     heartbeat.monitors:
        - type: browser
          id: my-monitor
          name: My Monitor
          schedule: "@every 1m"
          source:
            local:
              path: "./todos"

todos/elastic.travely.js：

    import { journey, step } from '@elastic/synthetics';
    import { deepStrictEqual } from 'assert';
    
    journey("Ensure elastic home page is correct", async ({page}) => {
       step("Go to elastic.co", async () => {
          await page.goto('https://www.elastic.co');
       });
    });

docker运行命令：

sudo docker run \
  --rm \
  --name=heartbeat \
  --user=heartbeat \
  --volume="$PWD/heartbeat.yml:/usr/share/heartbeat/heartbeat.yml:ro" \
  --volume="$PWD/todos:/usr/share/heartbeat/todos:ro" \
  docker.elastic.co/beats/heartbeat:7.12.0 heartbeat -e \
  -E cloud.id=""
  -E cloud.auth=""

此问题的根本原因和可能的解决方案是什么