Cacti Monitoring

#cacti #networkmonitoring #college

This final project had actually nothing special to say. I just wanted to thank Bening and Shofi for being a good team during this semester and finally we could finish the Network Management subject with this final subject. It was basically codes using Cacti. To be honest I almost didn't understand anything since I usually helped on the documentations instead of trying Cacti by myself. Bening was a student with Computer Network as her interest and she was our team's big help to understand this thing. I felt lucky that I chose this subject as my minor subject this semester because I felt no worries on my final score.

To get a look on my final project, you can visit this repository in my Github. Hope it will be helpful for anyone too.

Top comments (0)

5 Playwright CLI Flags That Will Transform Your Testing Workflow

0:56 --last-failed: Zero in on just the tests that failed in your previous run

2:34 --only-changed: Test only the spec files you've modified in git

4:27 --repeat-each: Run tests multiple times to catch flaky behavior before it reaches production

5:15 --forbid-only: Prevent accidental test.only commits from breaking your CI pipeline

5:51 --ui --headed --workers 1: Debug visually with browser windows and sequential test execution

Learn how these powerful command-line options can save you time, strengthen your test suite, and streamline your Playwright testing experience. Click on any timestamp above to jump directly to that section in the tutorial!

0:56 --last-failed: Zero in on just the tests that failed in your previous run
2:34 --only-changed: Test only the spec files you've modified in git
4:27 --repeat-each: Run tests multiple times to catch flaky behavior before it reaches production
5:15 --forbid-only: Prevent accidental test.only commits from breaking your CI pipeline
5:51 --ui --headed --workers 1: Debug visually with browser windows and sequential test execution

Watch Full Video 📹️