Skip to content
This repository has been archived by the owner on Jan 15, 2019. It is now read-only.

[dev.icinga.com #2204] new cgi.cfg option "display_status_totals" #272

Closed
icinga-migration opened this issue Dec 16, 2011 · 3 comments
Closed
Milestone

Comments

@icinga-migration
Copy link

This issue has been migrated from Redmine: https://dev.icinga.com/issues/2204

Created by ricardo on 2011-12-16 22:27:57 +00:00

Assignee: Wolfgang
Status: Resolved (closed on 2012-02-05 19:42:10 +00:00)
Target Version: 1.7
Last Update: 2012-03-13 05:48:25 +00:00 (in Redmine)


please add this option to the docs

# DISPLAY STATUS TOTAL
# This option allows you to specify if the
# Host Status Totals and Service Status Totals
# should be displayed.
# Default value is 1.

display_status_totals=0

thank you


Relations:

@icinga-migration
Copy link
Author

Updated by Wolfgang on 2012-02-05 19:42:10 +00:00

  • Status changed from New to Resolved
  • Assigned to set to Wolfgang
  • Done % changed from 0 to 100

fixed in r1.7

@icinga-migration
Copy link
Author

Updated by ddegois on 2012-03-13 00:46:23 +00:00

Hello,

While debugging an aNag issue against 1.7-dev, I've noticed that the display_status_totals is overridden in the default config (icinga-code/sample-config/cgi.cfg.in)

Shouldn't the directive being commented ?
If the default change to not display headers, would it be possible to have a statusheader or showstatusheader argument to force it (opposite of nostatusheader) ?
This way, I could use it in aNag and keep reverse compatibility :)

Regards,
Damien

# DISPLAY STATUS TOTAL
# This option allows you to specify if the
# Host Status Totals and Service Status Totals
# should be displayed.
# Default value is 1.

#display_status_totals=0

@icinga-migration
Copy link
Author

Updated by Wolfgang on 2012-03-13 05:48:25 +00:00

Looking at r1.7 in git it IS documented already. You are right that it ISN'T in latest but that reflects the current version, not the upcoming ;-)

@icinga-migration icinga-migration added this to the 1.7 milestone Jan 17, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant