Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[dev.icinga.com #6129] Add wizard step for the logging configuration #620

Closed
icinga-migration opened this issue May 6, 2014 · 7 comments
Labels
area/installation Affects the installation enhancement New feature or improvement
Milestone

Comments

@icinga-migration
Copy link

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

Created by jmeyer on 2014-05-06 11:48:55 +00:00

Assignee: jmeyer
Status: Resolved (closed on 2014-05-14 11:20:39 +00:00)
Target Version: 2.0-4
Last Update: 2014-05-14 11:20:39 +00:00 (in Redmine)


As a user, I want to configure the logging during the installation.

Acceptance criteria:

  • Should be structured similar to the already existing configuration form (Can probably be sub-classed!)
    • Should change its elements based on the chosen logging type
    • Should validate it's values when submitted
    • Default loglevel is ERROR
    • Default application is "icingaweb", if syslog
    • Default facility is "LOG_USR", if syslog
    • Default logpath is "{application}/var/log", if file

Changesets

2014-05-12 13:40:59 +00:00 by mjentsch 793a0a0

Add validation for application name.

refs #6129

2014-05-14 11:20:21 +00:00 by jmeyer 709146d

Add wizard page for the logging configuration

resolves #6129

Parent Task: #6136

@icinga-migration
Copy link
Author

Updated by jmeyer on 2014-05-06 14:12:34 +00:00

  • Parent Id set to 6136

@icinga-migration
Copy link
Author

Updated by elippmann on 2014-05-09 10:09:30 +00:00

Hi Johannes,

The form here used to configure logging must be the same as the configuration form. Im not aware of anything special which is valid for the installer's form only.
Further, "Should validate it's values when submitted" should be specified: When submitted, the form must validate that

  • loglevel is a valid logging level
  • facility is a valid syslog facility
  • logpath is writable by the webserver user. If not we should give a hint how to setup the path properly
    In addition the form should warn when application contains spaces or other characters not suitable for syslog output.

Johannes wrote:

As a user, I want to configure the logging during the installation.

Acceptance criteria:
* Should be structured similar to the already existing configuration form (Can probably be sub-classed!)
**** Should change its elements based on the chosen logging type
**** Should validate it's values when submitted
**** Default loglevel is ERROR
**** Default application is "icingaweb", if syslog
**** Default facility is "LOG_USR", if syslog
**** Default logpath is "{application}/var/log", if file

@icinga-migration
Copy link
Author

Updated by mjentsch on 2014-05-12 08:41:39 +00:00

  • Assigned to set to mjentsch

@icinga-migration
Copy link
Author

Updated by mjentsch on 2014-05-12 13:57:06 +00:00

  • Done % changed from 0 to 80

@icinga-migration
Copy link
Author

Updated by mjentsch on 2014-05-12 14:06:06 +00:00

  • Status changed from New to Assigned
  • Assigned to deleted mjentsch

@icinga-migration
Copy link
Author

Updated by jmeyer on 2014-05-13 13:36:18 +00:00

  • Assigned to set to jmeyer

@icinga-migration
Copy link
Author

Updated by jmeyer on 2014-05-14 11:20:39 +00:00

  • Status changed from Assigned to Resolved
  • Done % changed from 80 to 100

Applied in changeset icingaweb2|709146d49f18e92973189c985862083c0acec0ac.

@icinga-migration icinga-migration added enhancement New feature or improvement area/installation Affects the installation labels Jan 17, 2017
@icinga-migration icinga-migration added this to the 2.0-4 milestone Jan 17, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/installation Affects the installation enhancement New feature or improvement
Projects
None yet
Development

No branches or pull requests

1 participant