Logs don't show the correct attributes
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 9.9k
- Forks
- 471
- Avg merge
- 2d 4h
- Merged PRs (30d)
- 117
Description
Let's use a small example:
INSERT INTO otel_logs ( Timestamp, TimestampTime, TraceId, SpanId, TraceFlags, SeverityText, SeverityNumber, ServiceName, Body, ResourceSchemaUrl, ResourceAttributes, ScopeSchemaUrl, ScopeName, ScopeVersion, ScopeAttributes, LogAttributes ) VALUES ('2026-02-19 11:56:25.573000000', '2026-02-19 11:56:25', 'b5f55ba908baa7c2ee542ea6b88e3abc', '3d6148b05c0c4b84', 1, 'info', 9, 'test', 'test', '', {'k8s.node.name':'31f87b44ce45','service.name':'test','service.version':'1.0.0'}, '', 'test.backend', '1.0.0', {}, {'value':'2'}), ('2026-02-19 11:56:25.573000000', '2026-02-19 11:56:25', 'b5f55ba908baa7c2ee542ea6b88e3abc', '3d6148b05c0c4b84', 1, 'info', 9, 'test', 'test', '', {'k8s.node.name':'31f87b44ce45','service.name':'test','service.version':'1.0.0'}, '', 'test.backend', '1.0.0', {}, {'value':'3'}), ('2026-02-19 11:56:25.573000000', '2026-02-19 11:56:25', 'b5f55ba908baa7c2ee542ea6b88e3abc', '3d6148b05c0c4b84', 1, 'info', 9, 'test', 'test', '', {'k8s.node.name':'31f87b44ce45','service.name':'test','service.version':'1.0.0'}, '', 'test.backend', '1.0.0', {}, {'value':'4'}), ('2026-02-19 11:56:25.573000000', '2026-02-19 11:56:25', 'b5f55ba908baa7c2ee542ea6b88e3abc', '3d6148b05c0c4b84', 1, 'info', 9, 'test', 'test', '', {'k8s.node.name':'31f87b44ce45','service.name':'test','service.version':'1.0.0'}, '', 'test.backend', '1.0.0', {}, {'value':'5'}), ('2026-02-19 11:56:25.573000000', '2026-02-19 11:56:25', 'b5f55ba908baa7c2ee542ea6b88e3abc', '3d6148b05c0c4b84', 1, 'info', 9, 'test', 'test', '', {'k8s.node.name':'31f87b44ce45','service.name':'test','service.version':'1.0.0'}, '', 'test.backend', '1.0.0', {}, {'value':'6'});
In traces and logs stream, these logs are "stacked vertically", and absolutely identical (showing the same LogAttributes), although their actual attributes values differ.
Thanks again for your amazing work 🥇
Contributor guide
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 or test is named. Reproduce the issue with the provided INSERT into otel_logs, then trace how LogAttributes are fetched and rendered in the traces and logs stream. Done means rows with different LogAttributes, such as value 2 through 6, are displayed with their individual values rather than the same stacked attributes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- clickhouse, typescript
- Domain
- data, observability
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100