-
Notifications
You must be signed in to change notification settings - Fork 38
Foremanct - Log levels for Foreman & Proxy #640
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
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -72,6 +72,21 @@ There are multiple use cases from the users perspective that dictate what parame | |
| | foreman-installer Parameter | Description | Reason | | ||
| | --------------------------- | ----------- | ------ | | ||
|
|
||
| #### Logging | ||
|
|
||
| ##### New | ||
|
|
||
| | Parameter | Description | | ||
| | ----------| ----------- | | ||
| | `--log-level` | Default log level for all services. Accepted values: `debug`, `info`, `warn`, `error`, `fatal`. Defaults to `info`. | | ||
|
|
||
| ##### Mapped | ||
|
|
||
| | Parameter | Description | foreman-installer Parameters | | ||
| | ----------| ----------- | ---------------------------- | | ||
| | `--foreman-log-level` | Log level for Foreman. Overrides `--log-level` for Foreman only. | `--foreman-logging-level` | | ||
| | `--foreman-proxy-log-level` | Log level for Foreman Proxy. Overrides `--log-level` for Foreman Proxy only. | `--foreman-proxy-log-level` | | ||
|
|
||
| #### Undetermined | ||
|
|
||
| | foreman-installer Parameter | Description | Module | Puppet Parameter | Keep | | ||
|
|
@@ -95,7 +110,6 @@ There are multiple use cases from the users perspective that dictate what parame | |
| | `--foreman-keycloak-app-name` | | | | ||
| | `--foreman-keycloak-realm` | | | | ||
| | `--foreman-logging-layout` | | | | ||
| | `--foreman-logging-level` | | | | ||
| | `--foreman-logging-type` | | | | ||
| | `--foreman-oauth-map-users` | | | | ||
| | `--foreman-plugin-remote-execution-cockpit-ensure` | | | | ||
|
|
@@ -165,7 +179,6 @@ There are multiple use cases from the users perspective that dictate what parame | |
| | `--foreman-proxy-content-enable-ostree` | | | | | ||
| | `--foreman-proxy-http` | | | | | ||
| | `--foreman-proxy-log` | | | | | ||
|
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Similar to above. This controls where the proxy logs to (stdout, syslog, journal). I think in a containerized world we won't make that configurable so move this to the Unmapped section? |
||
| | `--foreman-proxy-log-level` | | | | | ||
| | `--foreman-proxy-plugin-ansible-working-dir` | | | | | ||
| | `--foreman-proxy-plugin-dhcp-infoblox-dns-view` | | | | | ||
| | `--foreman-proxy-plugin-dhcp-infoblox-network-view` | | | | | ||
|
|
||
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,4 +1,5 @@ | ||
| --- | ||
| include: | ||
| - _logging | ||
| - _pulp | ||
| - _foreman_proxy |
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -26,5 +26,6 @@ include: | |
| - _database_connection | ||
| - _foreman | ||
| - _foreman_proxy | ||
| - _logging | ||
| - _pulp | ||
| - _tuning | ||
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,19 @@ | ||
| --- | ||
| variables: | ||
| log_level: | ||
| help: Default log level for all services. | ||
| parameter: --log-level | ||
| choices: | ||
| - debug | ||
| - info | ||
| - warn | ||
| - error | ||
| - fatal | ||
| foreman_proxy_log_level: | ||
|
arvind4501 marked this conversation as resolved.
|
||
| help: Log level for Foreman Proxy. Defaults to the global log level. | ||
| choices: | ||
| - debug | ||
| - info | ||
| - warn | ||
| - error | ||
| - fatal | ||
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -128,6 +128,7 @@ | |
| FOREMAN_PUMA_THREADS_MAX: "{{ foreman_puma_threads_max }}" | ||
| FOREMAN_PUMA_WORKERS: "{{ foreman_puma_workers }}" | ||
| FOREMAN_ENABLED_PLUGINS: "{{ foreman_plugins | join(' ') }}" | ||
| FOREMAN_LOGGING_LEVEL: "{{ foreman_log_level }}" | ||
|
stejskalleos marked this conversation as resolved.
|
||
| quadlet_options: | ||
| - | | ||
| [Install] | ||
|
|
@@ -165,6 +166,7 @@ | |
| DYNFLOW_REDIS_URL: "redis://localhost:6379/6" | ||
| REDIS_PROVIDER: "DYNFLOW_REDIS_URL" | ||
| FOREMAN_ENABLED_PLUGINS: "{{ foreman_plugins | join(' ') }}" | ||
| FOREMAN_LOGGING_LEVEL: "{{ foreman_log_level }}" | ||
| command: "/usr/libexec/foreman/sidekiq-selinux -e production -r ./extras/dynflow-sidekiq.rb -C /etc/foreman/dynflow/%i.yml" | ||
| quadlet_options: | ||
| - | | ||
|
|
@@ -222,6 +224,7 @@ | |
| env: | ||
| SEED_ORGANIZATION: "{{ foreman_initial_organization }}" | ||
| SEED_LOCATION: "{{ foreman_initial_location }}" | ||
| FOREMAN_LOGGING_LEVEL: "{{ foreman_log_level }}" | ||
|
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. not directly related to the PR here, but we have a set of env vars we pass to all foreman containers. time to consolidate them into a variable so we don't have to edit them in multuple places? same for secrets, I guess? the
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. |
||
| quadlet_options: | ||
| - | | ||
| [Unit] | ||
|
|
||
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,5 @@ | ||
| --- | ||
| log_level: info | ||
|
|
||
| foreman_log_level: "{{ log_level }}" | ||
| foreman_proxy_log_level: "{{ log_level }}" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not a blocker, but I think I think we can say that layout and type will likely not be supported.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Given the author of this PR won't get to fix it quickly, I propose you track this as a separate work item