#2554 test: metrics table test case is added Pull request opened by palashgdev SigNoz/signoz GitHub Actions: playwright GitHub Actions: lint-commits GitHub Actions: Ensure Pull Request has a linked issue. ✅ 7 other checks have passed 7/10 successful checks

#2555 Easy select of timeline in logs like we have in Services dashboard Issue created by pruthvi-itribe Is your feature request related to a problem? Please describe. It would be great if we have select an area in the timeline above to zoom into the logs and dig deeper faster Describe the solution you'd like Have shared in this loom video https://www.loom.com/share/7bb254bc5f46431494e714feef97cab4 Describe alternatives you've considered This is there in datadog which helps to navitage to errors or any spikes of logs etc Additional context Add any other context or screenshots about the feature request here. Thank you for your feature request – we love each and every one! SigNoz/signoz

1 new commit pushed to

<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/signoz

#2248 (logs): tag filters suggestion API for explorer Issue created by srikanthccv We decided to use the materialised table to show the attribute key-value pairs seen in the past 24 hours for v1. This API should return the matching attributes and their types. ☐ #2540 SigNoz/signoz

Deployment to staging by nityanandagohain SigNoz/signoz

#2518 (logs): Query range v3 Pull request opened by nityanandagohain Part of #2250 Examples are present in postman`Query Range v3 logs` folder SigNoz/signoz GitHub Actions: playwright GitHub Actions: lint-commits ✅ 8 other checks have passed 8/10 successful checks

#2542 fix: minor issues found in development and enhancements Pull request opened by srikanthccv • 0.5 -> 0.05 • explicitly mention when a key is a column • add the filter operator symbols suggested by frontend • add the label for hist_quantile if the user didn't provide it already. SigNoz/signoz GitHub Actions: playwright GitHub Actions: lint-commits GitHub Actions: Ensure Pull Request has a linked issue. ✅ 7 other checks have passed 7/10 successful checks

1 new commit pushed to

<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/signoz

Deployment to staging by nityanandagohain SigNoz/signoz

#2556 RBAC control on Clickhouse Issue created by RealHarshThakur Is your feature request related to a problem? It would be nice if each Signoz component had fine-grained RBAC for the operations it needs to perform. Describe the solution you'd like • OTel collector: Currently, each exporter runs its own migrations at startup. Migrations could be run in a different process with credentials that have only DDL permissions and no DML permissions and have the collector use only DML permissions. This change can be backward-compatible. • Log exporter: A sample PR for logs: • Trace exporter: Similar to logs, this could be solved for traces as well • Metric exporter: We'll need to first create a migration directory for metrics to have a solution like above. I have not dug much into query-service/UI to comment on it but hoping this issue serves as an umbrella issue as fine-grained RBAC would reduce the attack surface. SigNoz/signoz

10 new commits pushed to

<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/signoz

Deployment to staging by ankitnayan SigNoz/signoz

#2557 Signoz UI bug in choosing custom timeframe Issue created by pruthvi-itribe Bug description When choosing custom timeframe value sometimes it does not work, attached a video Expected behavior Works as usual How to reproduce 1. Choose a custom timeframe and select timeA to timeB and filter logs 2. Next time change the custom time and this happens as per video https://www.loom.com/share/f1eb87309cbc4216b3fec63125ba1530 Version information • Signoz version: v0.17.0 • Browser version: Chrome Version 111.0.5563.146 (Official Build) (arm64) • Your OS and version: Mac OS Ventura 13.2.1 (22D68) • *Your CPU Architecture*(ARM/Intel): ARM Additional context Thank you for your bug report – we love squashing them! SigNoz/signoz

#203 clickhouse: custom init containers support Pull request opened by prashant-shahi Fixes #201 Signed-off-by: Prashant Shahi prashant@signoz.io SigNoz/charts ✅ All checks have passed 2/2 successful checks

#2558 ClickHouse: Suspiciously many broken parts Issue created by srikanthccv Several instances of may broken parts issue 1. {} 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

.

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/signoz

1 new commit pushed to

<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/signoz

#2312 FE(QB)(Trace/Logs): Other Filters Toggler Issue created by palashgdev Other Filters In Query Builder Collapsed Version In this filter we should register of filters as this is different in many place (ORDER_BY, LIMIT, HAVING) Expanded Version Only Aggregate Filter is added #2313 SigNoz/signoz

Deployment to staging by palashgdev SigNoz/signoz

#2559 Reporting a vulnerability Issue created by igibek Hello! I hope you are doing well! We are a security research team. Our tool automatically detected a vulnerability in this repository. We want to disclose it responsibly. GitHub has a feature called Private vulnerability reporting, which enables security research to privately disclose a vulnerability. Unfortunately, it is not enabled for this repository. Can you enable it, so that we can report it? Thanks in advance! PS: you can read about how to enable private vulnerability reporting here: https://docs.github.com/en/code-security/security-advisories/repository-security-advisories/configuring-private-vulnerability-reporting-for-a-repository SigNoz/signoz

1 new commit pushed to

<https://github.com/SigNoz/signoz/tree/develop|develop>

by srikanthccv

<https://github.com/SigNoz/signoz/commit/0c2574cef8a27eea992c90a08fb3202c3a94e0df|0c2574ce>

- (logs): Query range v3 (#2518) SigNoz/signoz

Deployment to staging by srikanthccv SigNoz/signoz

#2560 feat: signoz ui color hex support is added Pull request opened by palashgdev Close #2460 SigNoz/signoz GitHub Actions: playwright GitHub Actions: lint-commits GitHub Actions: Ensure Pull Request has a linked issue. ✅ 6 other checks have passed 6/9 successful checks

#2371 (logs): validate and add logic for Group By to add in final query Issue created by nityanandagohain Make sure to validate panel type SigNoz/signoz

#2373 (logs): Validate and add logic for Having Issue created by nityanandagohain The

Having

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/signoz

#2372 (logs): Validate and add logic for order by Issue created by nityanandagohain The order by behaviour will be different when there is an aggregation vs no aggregation (ie. NOOP). • When there is an aggregation of the data, the order by clause must contain the attributes from the group by clause and the aggregation applied on. • Where there is no aggregation of the data, the order by clause may contain the attributes from the attribute keys suggestion API. More details with examples: Say there is aggregation

SUM

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/signoz

#2370 (logs): Create a list of aggregation operators, parse validate and add it to the final query Issue created by nityanandagohain Make sure to validate panel type SigNoz/signoz

#2369 (logs): Parse and convert filters to the clickhouse where ( columns, attributes ) Issue created by nityanandagohain SigNoz/signoz

#2082 Signoz to interpret colors Issue created by shrbb Some loggers are colored and this is causing junk characters in signoz Need a way to make signoz interpret colors. SigNoz/signoz

#2246 (logs): attribute suggestion API for the aggregation type Issue created by srikanthccv Unlike traces, there are no events or exceptions in the logs model. This should only take the aggregator type (i.e "min", "max", "count", etc...) etc into account when responding with suggestions. SigNoz/signoz

#2375 (logs): support for multiple queries Issue created by nityanandagohain The user has the ability to write multiple queries using the builder. The data source is fixed in the explorer page for logs; however, in the metrics and dashboards page, that doesn't necessarily have to be true. A query can be disabled. A query can be a direct query or a formula. When the

queryName

is the same as the

Expression

, it is a direct query; otherwise, it is a formula. SigNoz/signoz