Skip to content

Commit

Permalink
Duplicate log messages into syslog according to zowe.sysMessages (#3553)
Browse files Browse the repository at this point in the history
* Add zowe.sysMessages to schema

Signed-off-by: 1000TurquoisePogs <[email protected]>

* Added missing comma + CHANGELOG

Signed-off-by: Leanid Astrakou <[email protected]>

* Remove empty sysMessages from example-zowe.yaml

Signed-off-by: Leanid Astrakou <[email protected]>

* Added some message ID examples

Signed-off-by: Leanid Astrakou <[email protected]>

---------

Signed-off-by: 1000TurquoisePogs <[email protected]>
Signed-off-by: Leanid Astrakou <[email protected]>
Co-authored-by: Leanid Astrakou <[email protected]>
  • Loading branch information
1000TurquoisePogs and DivergentEuropeans authored Aug 29, 2023
1 parent 560bb97 commit fc860e2
Show file tree
Hide file tree
Showing 3 changed files with 41 additions and 2 deletions.
5 changes: 4 additions & 1 deletion CHANGELOG.md
Original file line number Diff line number Diff line change
Expand Up @@ -5,8 +5,11 @@ All notable changes to the Zowe Installer will be documented in this file.

## `2.11.0`

### New features and enhancements
- Enhancement: Duplicate log messages into syslog according to "zowe.sysMessages" array [#93](https://github.com/zowe/launcher/pull/93)

#### Minor enhancements/defect fixes
- `zowe-yaml-schema.json` validates unix directory path as `server-common#zowePath`
- Bugfix: `zowe-yaml-schema.json` validates unix directory path as `server-common#zowePath`
- Bugfix: Fixed that Zowe would allow newer Java versions to generate PKCS12 keystores that was not compatible with some components. Newer versions of Java by default create PKCS12 keystores that aren't compatible with GSK / SystemSSL which components such as ZSS use, but include flags to restore a compatibility mode, which Zowe now uses. (#3507)

## `2.10.0`
Expand Down
28 changes: 28 additions & 0 deletions example-zowe.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -350,6 +350,34 @@ zowe:
# ZWED_SSH_PORT: 22
# ZWED_TN3270_PORT: 23

# >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
# You can define any Zowe message portions to be checked for and the whole message added to the system log
sysMessages:
# # Zowe starting
- "ZWEL0021I"
# # Zowe started
- "ZWEL0018I"
- "ZWEL0006I"
# # Zowe ready to use
- "ZWES1601I"
# # Zowe stopping
- "ZWEL0008I"
# # Zowe stopped
- "ZWEL0022I"
# # Zowe components starting
- "ZWEL0001I"
# # Zowe components stopped
- "ZWEL0002I"
# # API ML components ready
- "ZWEAM000I"
# # App server ready
- "ZWED0031I"
# # ZSS ready
- "ZWES1013I"

# # Not limited to Zowe message ID's
# - "ERROR"

# >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
# Enable debug mode for zowe launch scripts
launchScript:
Expand Down
10 changes: 9 additions & 1 deletion schemas/zowe-yaml-schema.json
Original file line number Diff line number Diff line change
Expand Up @@ -478,7 +478,7 @@
},
"unsafeDisableZosVersionCheck": {
"type": "boolean",
"description": "Used to allow Zowe to warn, instead of error, when running on a version of zOS that this version of Zowe hasn't been verified as working with",
"description": "Used to allow Zowe to warn, instead of error, when running on a version of z/OS that this version of Zowe hasn't been verified as working with",
"default": false
}
}
Expand Down Expand Up @@ -534,6 +534,14 @@
"description": "Customize how Zowe should validate certificates used by components or other services.",
"enum": ["STRICT", "NONSTRICT", "DISABLED"]
},
"sysMessages": {
"type": "array",
"description": "List of Zowe message portions when matched will be additionally logged into the system's log (such as syslog on z/OS). Note: Some messages extremely early in the Zowe lifecycle may not be added to the system's log",
"uniqueItems": true,
"items": {
"type": "string"
}
},
"useConfigmgr": {
"type": "boolean",
"default": false,
Expand Down

0 comments on commit fc860e2

Please sign in to comment.