TEN-framework / TEN-framework/ten-framework
[FEATURE] Add runtime toggle to disable [instance] prefix on console log output
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 11.1k
- Forks
- 1.4k
- Avg merge
- 2d 15m
- Merged PRs (30d)
- 22
Description
Description
When TEN apps run in cloud environments (e.g. GKE on GCP), the console logs produced by the runtime include a leading tag such as [agora_1xaiem] ahead of the JSON payload.
The property.json log formatter is already set to json, so the payload is valid JSON, but Google Cloud Logging rejects it as structured data because the first character is [ rather than {. As a result, all lines are ingested as plain text and downstream alerts/queries fail.
Please expose an environment variable or property setting that disables this prefix (or otherwise emits pure JSON) so that operators can keep using console logging while maintaining structured logging support in cloud platforms.
Severity
Critical
Additional Information
Example log line showing the non-JSON prefix:
[agora_1xaiem] {"timestamp":"2025-10-21T11:14:39.001813424+00:00","level":"INFO",...}
required output:
{"channel": "agora_1xaiem", "timestamp":"2025-10-21T11:14:39.001813424+00:00","level":"INFO",...}
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No file, test, or entry point is identified; start by locating the runtime console-log formatter and its property.json configuration handling. Done means a runtime setting can suppress the [instance] prefix while emitting the channel and remaining fields as structured JSON, with coverage for prefixed and pure-JSON output.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- google-cloud, kubernetes, python
- Domain
- cloud, observability-sre
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100