zaproxy / zaproxy/zaproxy

Heartbeat/periodic logging in the console to indicate long-running process has not hung

Open
#1,270 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement Priority-Medium
Dominant language
Java
Stars
15.8k
Forks
2.6k
Avg merge
13h 16m
Merged PRs (30d)
17

Description

On a -cmd mode run, a heartbeat log in the console every 5, 10 to 30 minutes could indicate
that a long-running process has not hung. In (ie: ci) cases where the user/initiator
can only access log output, it would be very useful.

Original issue reported on code.google.com by mhuckaby on 2014-07-17 03:02:02

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by locating the -cmd mode entry point and the console/log output path. Check how long-running processes are currently reported, then define the heartbeat interval behavior and verify that periodic output appears for a long-running -cmd run, including in CI-style log-only usage.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
cli
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.