question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Disk size monitoring unexcepted behaviour

See original GitHub issue

Description VM disk size monitored only one time after opennebula service restart using tm/driver/monitor script.

Sat Dec 29 11:24:24 2018 [Z0][ImM][D]: Datastore 3par_system (0) successfully monitored.
Sat Dec 29 11:24:24 2018 [Z0][VMM][D]: VM 97 successfully monitored: DISK_SIZE=[ID=0,SIZE=4242]
Sat Dec 29 11:25:09 2018 [Z0][InM][D]: Host tst.lin.fedora.host (0) successfully monitored.
Sat Dec 29 11:25:09 2018 [Z0][VMM][D]: VM 97 successfully monitored: STATE=a CPU=0.0 MEMORY=807324 NETRX=6317550576 NETTX=127931671 DISKRDBYTES=285341508 DISKWRBYTES=6207442432 DISKRDIOPS=8641 DISKWRIOPS=15705
Sat Dec 29 11:29:25 2018 [Z0][ImM][D]: Datastore 3par_system (0) successfully monitored.

As you see in logs, first time system ds is monitored log is followed by VM 97 successfully monitored: DISK_SIZE=[ID=0,SIZE=4242], next systems ds monitorings are without VM disk size parsing.

Expected behavior Disk size monitoring each time system datastore is monitored.

Details

  • Affected Component: Storage
  • Hypervisor: KVM
  • Version: 5.6.2

Progress Status

  • Branch created
  • Code committed to development branch
  • Testing - QA
  • Documentation
  • Release notes - resolved issues, compatibility, known issues
  • Code committed to upstream release/hotfix branches
  • Documentation committed to upstream release/hotfix branches

Issue Analytics

  • State:closed
  • Created 5 years ago
  • Reactions:1
  • Comments:6 (6 by maintainers)

github_iconTop GitHub Comments

1reaction
feldsamcommented, Jul 10, 2019

Monitor script parses disk usage stats only on each 10th run, so practically every 50minutes

Few proposals:

  • this variable should be configurable
  • most important is adding additional argument when calling ds monitor script to inform, that should NOT collect data about disk/snapshot usage, because it cost resources and it is used only every 10th run.
0reactions
rsmonterocommented, Jul 17, 2019

Merged into master

Read more comments on GitHub >

github_iconTop Results From Across the Web

Challenges in Disk Space Monitoring - ManageEngine
Disk space monitoring challenges · 1) Identifying the safer disk usage benchmark · 2) Leaving out correlating factors · 3) Lack of communication...
Read more >
Unexpected disk space consumption - ArcGIS Monitor
ArcGIS Monitor is exhibiting some odd behaviour I don't understand. MongoDB runs on the server D drive which was recently running out of ......
Read more >
Avoid running out of Disk Space ever again using SQL Monitor
By monitoring each of these metrics you will, firstly, cut out all the unplanned downtime caused by 'unexpectedly' running out of disk space ......
Read more >
disk usage from the monitoring console does NOT ma...
I am experiencing an unexpected behavior when trying to monitor disk usage. Hopefully you can explain why this is happening.
Read more >
The Benefits of Logging Disk Space Warnings or Errors
Regardless of what operating system or device, if it's possible to monitor the amount of free disk space and log the event, it...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found