GitHub
04/05/2023, 5:51 PMGitHub
04/05/2023, 6:45 PMGitHub
04/06/2023, 8:02 AM<https://github.com/SigNoz/signoz/tree/develop|develop>
by nityanandagohain
<https://github.com/SigNoz/signoz/commit/d09290528f7ae9659f99c06bc32df3ff3bca8c44|d0929052>
- feat(logs): add tag attribute autocomplete for logs (#2404)
SigNoz/signozGitHub
04/06/2023, 8:02 AMGitHub
04/06/2023, 8:02 AMGitHub
04/06/2023, 12:04 PMGitHub
04/06/2023, 12:14 PMGitHub
04/07/2023, 4:16 AM<https://github.com/SigNoz/signoz/tree/develop|develop>
by nityanandagohain
<https://github.com/SigNoz/signoz/commit/4db109cbad5117c380a0cc90f7a5434860469c73|4db109cb>
- fix: minor issues found in development and enhancements (#2542)
SigNoz/signozGitHub
04/07/2023, 4:16 AMGitHub
04/07/2023, 4:55 AMGitHub
04/07/2023, 6:17 AM<https://github.com/SigNoz/signoz/tree/develop|develop>
by ankitnayan
<https://github.com/SigNoz/signoz/commit/776aa3471ffaa1b6cefd3130e22762a13a26b46d|776aa347>
- fix: remove frontend code owner
<https://github.com/SigNoz/signoz/commit/c9db4c90518b1c0e2223e4d251a5f553fd895b6a|c9db4c90>
- Merge branch 'develop' into fix/remove-fe-owner
<https://github.com/SigNoz/signoz/commit/a5e4336e1857611aee508a939bef3fb4ef5d21e1|a5e4336e>
- Merge branch 'develop' into fix/remove-fe-owner
<https://github.com/SigNoz/signoz/commit/0e8f09632ffea8b5fe335509aface855486b08f7|0e8f0963>
- Merge branch 'develop' into fix/remove-fe-owner
<https://github.com/SigNoz/signoz/commit/0b3e8d797be2af00ec39db9375365c6461fd7fad|0b3e8d79>
- Merge branch 'develop' into fix/remove-fe-owner
<https://github.com/SigNoz/signoz/commit/c92493904b93a57a943ab3b60722fbf9fc1d88df|c9249390>
- Merge branch 'develop' into fix/remove-fe-owner
<https://github.com/SigNoz/signoz/commit/7dd09129aa4225877e99f5094c524d63a41a94d7|7dd09129>
- Merge branch 'develop' into fix/remove-fe-owner
<https://github.com/SigNoz/signoz/commit/5b72919a555bcbfc7ee382c538b715a7945f660e|5b72919a>
- Merge branch 'develop' into fix/remove-fe-owner
<https://github.com/SigNoz/signoz/commit/81beaffa3dd04142291f671aae80c9f74716ec61|81beaffa>
- Merge branch 'develop' into fix/remove-fe-owner
<https://github.com/SigNoz/signoz/commit/9ac2308b896badebf56afa8e450923ddccf91631|9ac2308b>
- Merge pull request #2528 from techchintan/fix/remove-fe-owner
SigNoz/signozGitHub
04/07/2023, 6:17 AMGitHub
04/07/2023, 12:58 PMGitHub
04/10/2023, 5:11 AMGitHub
04/10/2023, 7:07 AMsignoz_traces
.top_level_operations
from metadata file /var/lib/clickhouse/store/b8f/b8fde4fc-bb6f-4b0e-8917-49c7a90bc6f4/top_level_operations.sql from query ATTACH TABLE signoz_traces.top_level_operations UUID 'f7c8a8d9-db55-4086-8d2f-ce7852c72790' (name
LowCardinality(String) CODEC(ZSTD(1)), serviceName
LowCardinality(String) CODEC(ZSTD(1))) ENGINE = ReplacingMergeTree ORDER BY (serviceName, name) SETTINGS index_granularity = 8192
2. {} Application: DB:Exception Suspiciously many (11 parts, 0.00 B in total) broken parts to remove while maximum allowed broken parts count is 10. You can change the maximum value with merge tree setting 'max_suspicious_broken_parts' in <merge_tree> configuration section or in table settings in .sql file (don't forget to return setting back to default value): Cannot attach table signoz_traces
.dependency_graph_minutes
from metadata file /var/lib/clickhouse/store/c1a/c1a64bd6-789f-4539-8542-15aa1eb29d06/dependency_graph_minutes.sql from query ATTACH TABLE signoz_traces.dependency_graph_minutes UUID 'cdbf4368-4dfd-41b2-a552-b02aa85903f5' (src
LowCardinality(String) CODEC(ZSTD(1)), dest
LowCardinality(String) CODEC(ZSTD(1)), duration_quantiles_state
AggregateFunction(quantiles(0.5, 0.75, 0.9, 0.95, 0.99), Float64) CODEC(Default), error_count
SimpleAggregateFunction(sum, UInt64) CODEC(T64, ZSTD(1)), total_count
SimpleAggregateFunction(sum, UInt64) CODEC(T64, ZSTD(1)), timestamp
DateTime CODEC(DoubleDelta, LZ4)) ENGINE = AggregatingMergeTree PARTITION BY toDate(timestamp) ORDER BY (timestamp, src, dest) TTL toDateTime(timestamp) + toIntervalSecond(604800) SETTINGS index_granularity = 8192, ttl_only_drop_parts = 1
3. {} Application: DB:Exception Suspiciously many (13 parts, 0.00 B in total) broken parts to remove while maximum allowed broken parts count is 10. You can change the maximum value with merge tree setting 'max_suspicious_broken_parts' in <merge_tree> configuration section or in table settings in .sql file (don't forget to return setting back to default value): Cannot attach table signoz_metrics
.samples_v2
from metadata file /var/lib/clickhouse/store/90f/90fde3c5-a131-4fd9-a85a-51a5cab5517e/samples_v2.sql from query ATTACH TABLE signoz_metrics.samples_v2 UUID '01c3f5a7-9d8b-45dc-9903-c11b8ae3bdd2' (metric_name
LowCardinality(String), fingerprint
UInt64 CODEC(DoubleDelta, LZ4), timestamp_ms
Int64 CODEC(DoubleDelta, LZ4), value
Float64 CODEC(Gorilla, LZ4)) ENGINE = MergeTree PARTITION BY toDate(timestamp_ms / 1000) ORDER BY (metric_name, fingerprint, timestamp_ms) TTL toDateTime(timestamp_ms / 1000) + toIntervalSecond(2592000) SETTINGS index_granularity = 8192, ttl_only_drop_parts = 1
How to fix:
• Docker deployment
In the SigNoz docker(swarm) set up, the ClickHouse data resides in the data folder. Please find an appropriate folder. For swarm, it would be deploy/docker-swarm/clickhouse-setup/data/
otherwise deploy/docker/clickhouse-setup/data/
Run touch /deploy/docker/clickhouse-setup/data/clickhouse/flags/force_restore_data
• k8s deployment
Use the init containers for running the command.
And for the longterm, adjusting the max allowed broken parts could also be the solution.
• Docker deployment.
Edit the clickhouse-config.xml
(maintained differently for docker-swarm) file.
• k8s deployement
Use the files options in the charts https://github.com/SigNoz/charts/blob/main/charts/signoz/values.yaml#L306
Please share the circumstances that led to this error in your case.
SigNoz/signozGitHub
04/10/2023, 12:02 PM<https://github.com/SigNoz/signoz/tree/develop|develop>
by palashgdev
<https://github.com/SigNoz/signoz/commit/7c952fd9cda0b1658285c6a1333b234320c40af8|7c952fd9>
- feat(builder): add additional filter toggler (#2549)
SigNoz/signozGitHub
04/10/2023, 12:02 PMScreenshot 2023-02-22 at 9 19 02 AM▾
Screenshot 2023-02-22 at 12 08 40 PM▾
GitHub
04/10/2023, 12:02 PMGitHub
04/10/2023, 1:27 PMGitHub
04/10/2023, 2:06 PM<https://github.com/SigNoz/signoz/tree/develop|develop>
by srikanthccv
<https://github.com/SigNoz/signoz/commit/0c2574cef8a27eea992c90a08fb3202c3a94e0df|0c2574ce>
- (logs): Query range v3 (#2518)
SigNoz/signozGitHub
04/10/2023, 2:06 PMGitHub
04/10/2023, 8:45 PMGitHub
04/11/2023, 1:31 AMGitHub
04/11/2023, 1:31 AMHaving
clause will only contain the data when aggregation is involved. For example, having SUM(bytes)
> 100 etc.. The key part will be constant for each, which the the aggregationOp(aggregateAttribute)
. There can be multiple having items in the request payload i.e SUM(bytes)
> 10 and SUM(bytes)
< 100.
SigNoz/signozGitHub
04/11/2023, 1:33 AMSUM
on the bytes
of the logs data source and group by clause selected with k8s_cluster_name
, service_name
. In this scenario, the expected list of order by items
• SUM(bytes) asc
• SUM(bytes) desc
• k8s_cluster_name asc
• k8s_cluster_name desc
• service_name asc
• service_name desc
Where there is no aggregation performed, the order can be on any attribute.
• http_url asc
• http_url desc
• http_status_code asc
• http_status_code desc
• http_mehod asc
• http_method desc
SigNoz/signozGitHub
04/11/2023, 1:33 AMGitHub
04/11/2023, 1:34 AMGitHub
04/11/2023, 1:35 AMGitHub
04/11/2023, 1:36 AMGitHub
04/11/2023, 1:38 AMqueryName
is the same as the Expression
, it is a direct query; otherwise, it is a formula.
SigNoz/signoz