[monitor-docker] Error reading monitor statistics: TypeError: Cannot read properties of undefined (reading 'usage')

Which Caliper version are you using?

v0.5.0-unstable-20220408135025

Which Node.JS version are you using?

v17.8.0

Which operating system are you using?

macOs Monterey 12.2.1

Please provide some context for your error. For example, when did the error occur? What were you trying to achieve, and how?

I tried to monitor remote docker containers.

npx caliper launch manager --caliper-bind-sut fabric:latest-v2 --caliper-workspace ./ --caliper-bind-cwd ./ --caliper-networkconfig networks/networkConfig.yaml --caliper-benchconfig benchmarks/config.yaml --caliper-flow-only-testcat

What was the observed incorrect behavior?

Caliper cannot gather monitoring information because of the error

Please provide the error logs and their surroundings.

[monitor-docker]  Error reading monitor statistics: TypeError: Cannot read properties of undefined (reading 'usage')

Please provide your benchmark configuration file content, if possible.

test:
  name: initial try
  description: it is just a proof of concept 
  workers:
    type: local
    number: 1
  rounds:
    - label: main
      description: fixed
      txDuration: 60
      rateControl:
        type: fixed-rate
        opts:
          tps: 5
      workload:
        module: workload/createIdentity.js
monitors:
  resource:
  - module: docker
    options:
      interval: 5
      containers:
        - dev-peer0.org2.example.com-identity_1.0-42252d58153bcf4ee71291af75bf27a4575826b9fe0d5596e34735f00db464d8
        - dev-peer0.org1.example.com-identity_1.0-42252d58153bcf4ee71291af75bf27a4575826b9fe0d5596e34735f00db464d8

Please provide your network configuration file content, if possible.

-

Please provide your workload module content, if possible.

-

Please provide any additional information you deem relevant to the error.

No response

[fraVlaca]

Thanks! I have just tryied now as well and got the same error …investigating now, will let you know asap.

[davidkel]

@aronaks In your monitor section could you try changing your interval value. 5 = 5 milliseconds, so I wonder do you get the same problem if you increase the interval to say 500 = 500 milliseconds?