-
Notifications
You must be signed in to change notification settings - Fork 133
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
Issue WTO message on API Mediation Layer startup #3894
Conversation
Signed-off-by: Jakub Balhar <jakub.balhar@broadcom.com>
Signed-off-by: Jakub Balhar <jakub.balhar@broadcom.com>
😺 Thank you for creating this PR! To publish your content to Zowe Docs, follow these required steps.
Need help? Contact the Doc Squad in the #zowe-doc Slack channel. |
Signed-off-by: Andrew Jandacek <andrew.jandacek@broadcom.com>
`2024-09-30 10:17:53.814 <ZWEAGW1:DiscoveryClient-InstanceInfoReplicator-%d:3335> jb892003 INFO ((o.z.a.g.c.GatewayHealthIndicator)) ZWEAM001I API Mediation Layer started` | ||
|
||
2. Prepare custom logging configuration. | ||
The current default logging implementation starts with information about the current time. This message content is unlike the message id which is typical in z/OS. To change this message behavior, configure the logging configuration. For details about how to configure API Mediation logging, see [Customizing Zowe API Mediation Layer logging](./configuration-logging.md). |
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.
I don't understand the meaning of this and why this is essential information in the instructions. Can you please modify or explain the reason this information is useful?
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.
The article is more of a use case and how to achieve this. This part explains how to provide the custom configuration in general.
The article below explains how does it need to look like for this specific requirements e.g. Syslog message issued with message id in the beginning.
|
||
2. Prepare custom logging configuration. | ||
The current default logging implementation starts with information about the current time. This message content is unlike the message id which is typical in z/OS. To change this message behavior, configure the logging configuration. For details about how to configure API Mediation logging, see [Customizing Zowe API Mediation Layer logging](./configuration-logging.md). | ||
|
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.
Can you please provide a single line description of what this configuration is? Is this an example?
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.
I tried to change it.
</root> | ||
</configuration> | ||
``` | ||
3. Change the structure of the log messages for the Gateway within the API Mediation Layer: |
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.
Can you please explain what this change of structure achieves?
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.
I tried in the change
Signed-off-by: Andrew Jandacek <andrew.jandacek@broadcom.com>
Signed-off-by: Jakub Balhar <jakub.balhar@broadcom.com>
|
||
This functionality requires the following changes to the zowe.yaml: | ||
|
||
1. Change the property `zowe.sysMessages` by adding the value `- "ZWWEAM001I""` |
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.
ZWWEAM001I -> ZWEAM001I
It looks like ZWEAM001I is a new message that is better than ZWEAM000I for detecting readiness. That's great! Please see the PRs I made to implement this. |
It's been implemented only for V2 by now I believe. It should be in 2.x documentation. As for v3 we originally intended something better, but it's probably good enough and we should bring it to the v3 as well at least. |
Signed-off-by: Andrew Jandacek <andrew.jandacek@broadcom.com>
|
||
This functionality requires the following changes to the zowe.yaml: | ||
|
||
1. Change the property `zowe.sysMessages` by adding the value `- "ZWEAM001I""` |
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.
Should there be two quotation marks at the end of "ZWEAM001I""` ?
Signed-off-by: Jakub Balhar <jakub.balhar@broadcom.com>
Signed-off-by: Andrew Jandacek <andrew.jandacek@broadcom.com>
Signed-off-by: Andrew Jandacek <andrew.jandacek@broadcom.com>
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.
Reviewed and edited by doc squad
Signed-off-by: Andrew Jandacek <andrew.jandacek@broadcom.com>
Describe your pull request here:
One of the common requests is issuing the specific message when the API Mediation Layer properly starts in the Syslog. This article explains all the configuration and pieces needed to achieve this goal with the current functionality.
List the file(s) included in this PR:
wto-message-on-startup.md
After creating the PR, follow the instructions in the comments.