1 new commit pushed to

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

by ankitnayan

<https://github.com/SigNoz/signoz/commit/9aff047da4746e7109de58f875115b0f70ec1b8b|9aff047d>

- chore: 🔧 remove resource requests/limits from sample apps (#2288) SigNoz/signoz

#2288 chore: :wrench: remove resource requests/limits from sample apps Pull request opened by prashant-shahi Hotrod consumes only very little resources. Hence by not setting any resource requests/limits, we should be able to deploy sample apps in environment with limited resources.

NAME                             CPU(cores)   MEMORY(bytes)   
hotrod-5cd54cc8cf-bd596          58m          7Mi             
locust-master-576777b878-59lkl   2m           29Mi            
locust-slave-7f897fb6c6-vsnld    10m          29Mi

Signed-off-by: Prashant Shahi prashant@signoz.io SigNoz/signoz GitHub Actions: playwright GitHub Actions: lint-commits GitHub Actions: Ensure Pull Request has a linked issue. ✅ 8 other checks have passed 8/11 successful checks

Deployment to staging by ankitnayan SigNoz/signoz

1 new commit pushed to

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

by ankitnayan

<https://github.com/SigNoz/signoz/commit/041d347d50e5e56753dea0f4a7e8c1eca8debcc5|041d347d>

- chore: 🔧 update install and troubleshooting guide url (#2451) SigNoz/signoz

#2451 chore: :wrench: update install and troubleshooting guide url Pull request opened by prashant-shahi Signed-off-by: Prashant Shahi prashant@signoz.io SigNoz/signoz GitHub Actions: playwright GitHub Actions: lint-commits GitHub Actions: Ensure Pull Request has a linked issue. ✅ 8 other checks have passed 8/11 successful checks

Deployment to staging by ankitnayan SigNoz/signoz

#2583 Pagination in Signoz logs not working properly Issue created by pruthvi-itribe Bug description Pagination in logs is not working expected when filters are applied, the next and previous button gets disabled sometimes mostly when going to last page. And also logs per page doesn't work as intended https://www.loom.com/share/13730c38930e4827bc909813dcad1376 If this affects the front-end, screenshots would be of great help. Expected behavior Pagination to work as expected How to reproduce 1. Shared the video link Version information • Signoz version: • Browser version: • Your OS and version: • *Your CPU Architecture*(ARM/Intel): Additional context Thank you for your bug report – we love squashing them! SigNoz/signoz

1 new commit pushed to

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

by palashgdev

<https://github.com/SigNoz/signoz/commit/502b8b1ba8e9387ba2a1b86585370a40afd9b7ed|502b8b1b>

- fix: tag filters query missing on page reload (#2580) SigNoz/signoz

#2121 bug(FE):Tag filters query missing on page reload Issue created by makeavish Loom video explaining the bug: https://www.loom.com/share/beffdd75906d47a286768d4639e4c164 SigNoz/signoz

Deployment to staging by palashgdev SigNoz/signoz

1 new commit pushed to

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

by palashgdev

<https://github.com/SigNoz/signoz/commit/51f1d0fd05a057cd347b049f5d39b8b836f491a3|51f1d0fd>

- feat: added aggregate every filter (#2581) SigNoz/signoz

#2313 FE(QB): Adding AGGREGATE EVERY filter Issue created by palashgdev This is part of the collapsable window in the query. It is a number input provided by the user. However, we have logic that sets the default value for the aggregation interval on the client side. So the default value will be based on the time range and the value return from the step size calculator function, which the user can change. Make sure to show that the seconds precision with (30 s) SigNoz/signoz

Deployment to staging by palashgdev SigNoz/signoz

1 new commit pushed to

<https://github.com/SigNoz/signoz-otel-collector/tree/main|main>

by srikanthccv

<https://github.com/SigNoz/signoz-otel-collector/commit/d90bdcbc48cb448661aa9db85b7d6cf043134817|d90bdcbc>

- introduce span attributes keys table (#126) SigNoz/signoz-otel-collector

#2584 fix: add support for count aggregate attribute Pull request opened by makeavish SigNoz/signoz GitHub Actions: e2e-k3s GitHub Actions: Deploy PR branch to testing GitHub Actions: Ensure Pull Request has a linked issue. GitHub Actions: playwright GitHub Actions: lint-commits ✅ 7 other checks have passed 7/12 successful checks

1 new commit pushed to

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

by srikanthccv

<https://github.com/SigNoz/signoz/commit/60b78e94d84b8e0c837002448b1ca031869ddeaf|60b78e94>

- fix: add support for count aggregate attribute (#2584) SigNoz/signoz

Deployment to staging by srikanthccv SigNoz/signoz

#2585 feat: added configuration via env for context timeout Pull request opened by daniel-t4e Added a solution for #2582 SigNoz/signoz GitHub Actions: build-frontend GitHub Actions: Ensure Pull Request has a linked issue. GitHub Actions: build-query-service GitHub Actions: lint-commits GitHub Actions: update_release_draft GitHub Actions: playwright GitHub Actions: build-ee-query-service GitHub Actions: dependency-review GitHub Actions: remove GitHub Actions: Codeball ✅ No checks have passed 0/10 successful checks

#2586 feat: add context cancellation env var Pull request opened by makeavish fixes: #2582 SigNoz/signoz GitHub Actions: create_issue_on_merge GitHub Actions: playwright GitHub Actions: Ensure Pull Request has a linked issue. GitHub Actions: lint-commits ✅ 6 other checks have passed 6/10 successful checks

1 new commit pushed to

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

by palashgdev

<https://github.com/SigNoz/signoz/commit/63570c847a5fdbea5792c3eaa94c5e3cf93cc9bb|63570c84>

- feat: added Order By filter (#2551) SigNoz/signoz

#2308 FE(QB): Create Order by Filter Issue created by palashgdev 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 should show the attributes from the group by clause and the aggregation applied on. • Where there is no aggregation of the data, the order by clause needs to fetch the attributes from the attribute keys suggestion API and show the options. 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 options for the user will be • 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, so the client needs to fetch keys from the backend as the user type in the text for the key, and the options will follow for user selection. Say the user enters the text

http_

and the backend (attribute keys suggestion API i.e

api/v3/autocomplete/attribute_keys

) responds with the option [

http_url

,

http_status_code

,

http_method

], and the client needs to show • http_url asc • http_url desc • http_status_code asc • http_status_code desc • http_mehod asc • http_method desc SigNoz/signoz

Deployment to staging by palashgdev SigNoz/signoz

#127 chore: merge tagKeyBatch and tagBatch writer funcs Pull request opened by makeavish SigNoz/signoz-otel-collector GitHub Actions: lint-and-test ✅ 2 other checks have passed 2/3 successful checks

1 new commit pushed to

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

by palashgdev

<https://github.com/SigNoz/signoz/commit/dd25ad95c77df8089aeaa9025dafc54b30eea3a0|dd25ad95>

- feat(builder): add having filter (#2567) SigNoz/signoz

#2309 FE(QB): Add Having Filter Issue created by palashgdev The having filter will always work on the aggregation data i.e it will show the option when there is some aggregation performed. Say the user does

MAX

(selected aggregate operation of the query) of

span.credit_limit

(selected aggregate attribute of the query); then we need to show all the options for this i.e

MAX(span.credit_limit)

< (the user will enter this input. there is no API call involved here)

MAX(span.credit_limit)

> (...)

MAX(span.credit_limit)

= (...)

MAX(span.credit_limit)

!= (...) ... This is not a signal-specific component functionality. This can be done once and used everywhere. SigNoz/signoz

Deployment to staging by palashgdev SigNoz/signoz

#2587 FE(QB): Edit on where clause tag Issue created by techchintan Is your feature request related to a problem? The user should able to edit the new query builder's search filter chip SigNoz/signoz

#2588 Allow fixed columns of signoz_index_v2 of trace db to be nullable Issue created by makeavish Nullable columns will allow filtering operators like exists/not exists. #2571 (comment) Some issues with allowing nullable columns: 1. Poor performance up to 2x: https://groups.google.com/g/clickhouse/c/AP2FbQ-uoj8/m/lBDiSmeIFQAJ 2. Sorting key cannot contain nullable columns SigNoz/signoz

#2589 test: added useIsValidTag.test Pull request opened by palashgdev added test SigNoz/signoz GitHub Actions: build-query-service GitHub Actions: Ensure Pull Request has a linked issue. GitHub Actions: build-frontend GitHub Actions: playwright GitHub Actions: build-ee-query-service GitHub Actions: dependency-review GitHub Actions: Codeball GitHub Actions: remove GitHub Actions: lint-commits ✅ No checks have passed 0/9 successful checks

#2590 fix: edit tag chip for WHERE clause updated logic Pull request opened by techchintan Close: #2587 SigNoz/signoz GitHub Actions: playwright GitHub Actions: Ensure Pull Request has a linked issue. GitHub Actions: lint-commits ✅ 7 other checks have passed 7/10 successful checks