Incorrect log ID formatting?

[1000TurquoisePogs]

I've noticed that some or all of our servers have messages with program IDs that don't match the name of the process or job.

Consider, in v2 the default job ID for the gateway is ZWE1AG. Yet in the logs, I see timestamp <ZWEAGW1:main:pid> Our users cannot be expected to remember the mappings of these things. This is also a problem with the app-server, but I think we should all come together on revising the IDs to match the jobnames as the jobnames appear to follow the format of $ZWE_zowe_job_prefix+<some 2 letter suffix>

[balhar-jakub]

This does sound like a good thing. We agreed that definitely the result should be the job id one.

The only concern is that some users may be depending on this behavior for automation and as such we would probably wait till V3 and do it on major version boundary to limit the impact of potentially breaking change.

What is your opinion?

[1000TurquoisePogs]

Can we satisfy both old and new behavior with configuration, so that it isn't a breaking change? It's true, I don't even know if our testing automation expects a certain format today so it could break things if it were a new default.

[balhar-jakub]

Yes, I believe we should implement it sooner and hide behind the configuration. Let the people know that it's there and then later on with V3 change the default. That's what we've done with the routes.

[github-actions[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.

[github-actions[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.