Bug 36032 - Make service_check_timeout configurable via UCR
Make service_check_timeout configurable via UCR
Status: RESOLVED WONTFIX
Product: UCS
Classification: Unclassified
Component: Monitoring (Prometheus or Nagios)
UCS 4.2
Other Linux
: P5 enhancement (vote)
: ---
Assigned To: UCS maintainers
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2014-10-01 08:58 CEST by Tim Petersen
Modified: 2022-06-27 17:49 CEST (History)
2 users (show)

See Also:
What kind of report is it?: ---
What type of bug is this?: ---
Who will be affected by this bug?: ---
How will those affected feel about the bug?: ---
User Pain:
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional):
Max CVSS v3 score:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Tim Petersen univentionstaff 2014-10-01 08:58:07 CEST
Requested at #2014093021000086:
"service_check_timeout" in /etc/nagios3/nagios.cfg should be made configurable via UCR.
Comment 1 Janis Meybohm univentionstaff 2014-10-06 08:22:18 CEST
(In reply to Tim Petersen from comment #0)
> Requested at #2014093021000086:
> "service_check_timeout" in /etc/nagios3/nagios.cfg should be made
> configurable via UCR.

This is needed for long running service checks via NRPE. Nagios server will kill the "external command" (check_nrpe) after service_check_timeout seconds (default 60).
Comment 2 Stefan Gohmann univentionstaff 2017-06-16 20:40:05 CEST
This issue has been filed against UCS 3. UCS 3 is out of the normal maintenance and many UCS components have vastly changed in UCS 4.

If this issue is still valid, please change the version to a newer UCS version otherwise this issue will be automatically closed in the next weeks.
Comment 3 Stephan Hendl 2017-06-19 09:40:59 CEST
Please change the version to either 4.1 or 4.2 since the feature still required.
Comment 4 Ingo Steuwer univentionstaff 2020-07-03 20:54:09 CEST
This issue has been filed against UCS 4.2.

UCS 4.2 is out of maintenance and many UCS components have changed in later releases. Thus, this issue is now being closed.

If this issue still occurs in newer UCS versions, please use "Clone this bug" or reopen it and update the UCS version. In this case please provide detailed information on how this issue is affecting you.