[Question] Job metrics cannot be found.

### Search before asking

- [x] I had searched in the [issues](https://github.com/apache/seatunnel/issues?q=is%3Aissue+label%3A%22bug%22) and found no similar issues.

### What happened

I want to check the statistical metrics of the stream jobs submitted to the cluster, but I cannot find them in the log files. Such information includes the number of read data records, the number of written data records, and so on.

Separated Cluster Mode.

Configure to output separate log files for jobs.

### SeaTunnel Version

2.3.12

### SeaTunnel Config

```conf
seatunnel:
engine:
classloader-cache-mode: true
history-job-expire-minutes: 4320
backup-count: 1
queue-type: blockingqueue
print-execution-info-interval: 60
print-job-metrics-info-interval: 60
slot-service:
dynamic-slot: true
checkpoint:
interval: 300000
timeout: 60000
storage:
type: hdfs
max-retained: 5
plugin-config:
storage.type: s3
fs.s3a.access.key: admin
fs.s3a.secret.key: ******
fs.s3a.endpoint: http://10.*.*.*:9000
s3.bucket: s3a://jxglas
fs.s3a.aws.credentials.provider: org.apache.hadoop.fs.s3a.SimpleAWSCredentialsProvider
telemetry:
metric:
enabled: true
logs:
scheduled-deletion-enable: true
http:
enable-http: true
port: 8080
enable-dynamic-port: false
# Uncomment the following lines to enable basic authentication for web UI
# enable-basic-auth: true
# basic-auth-username: admin
# basic-auth-password: admin
```

### Running Command

```shell
seatunnel.sh --config job.config --async
```

### Error Exception

```log
No errors reported.
```

### Zeta or Flink or Spark Version

zeta

### Java or Scala Version

1.8

### Screenshots

_No response_

### Are you willing to submit PR?

- [ ] Yes I am willing to submit a PR!

### Code of Conduct

- [x] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct)

Reproduce the report with seatunnel.sh --config job.config --async in Separated Cluster Mode, using the supplied metrics and separate-log settings, then inspect the resulting job log files. Determine whether read and written record metrics are emitted; done means those metrics are discoverable in the configured logs or the missing behavior is clearly diagnosed.

Written by the indexing model from the issue text.