[Bug] Have the client_identifier, model and action attributes logged on the `dbt.log` enabling maintenance of the respective sessions

[sathishsri88]

Is there an existing issue for this?

• I have searched the existing issues

Current Behavior

We don't have the client_identifier being logged onto the dbt.log file, which makes the maintenance of sessions created during the execution very difficult and we have to do filtering on the execution time to filter down the appropriate session which is again an approximate filter

Expected Behavior

If the client_identifier, model and action are logged we can use the same information for accessing the session in contention

Steps To Reproduce

dbt run
for version 1.5.3 and above

Relevant log output using --debug flag enabled

No response

Environment

- OS: linux
- Python: 3.8
- dbt: 1.5.3

What Oracle database version are you using dbt with?

No response

Additional Context

No response