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/e0bd5cc4f9877f6d9cdd635a0aefc377576ad017|e0bd5cc4>

- fix: on cluster command added to migration (#104) SigNoz/signoz-otel-collector

#2362 Menu antd depreciation warning Issue created by palashgdev There are few places which are listed below needs to be updated ☐ frontend/src/components/TimePreferenceDropDown/index.tsx ☐ frontend/src/container/ConfigDropdown/index.tsx ☐ frontend/src/container/ListOfDashboard/index.tsx ☐ frontend/src/container/SideNav/index.tsx:100 SigNoz/signoz

1 new commit pushed to

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

by palashgdev

<https://github.com/SigNoz/signoz/commit/06a55ccdd64364f61a887220578c32d8edc6f3b6|06a55ccd>

- chore: linebreak style is updated (#2277) SigNoz/signoz

Deployment to staging by palashgdev SigNoz/signoz

#1780 Enable pre-built dashboards for opentelemetry collectors Issue created by ankitnayan Below charts for metrics, logs and traces would give a lot of visibility into opentelemetry collectors deployed at SigNoz. ☑︎ Receiver Acceptance Rate ☑︎ Receiver Rejection Rate ☑︎ Exporter Sending Rate ☑︎ Exporter Failing Rate ☑︎ Dropping Rate ☐ Export new metrics on avg export latency SigNoz/signoz

#1773 Kubernetes installation fails Issue created by sjcotto Bug description Kubernetse instalation fails Following the docs https://signoz.io/docs/install/kubernetes/others/ after execution the helm install

helm --namespace platform install my-release signoz/signoz

returns an error

Error: template: signoz/charts/k8s-infra/templates/otel-deployment/deployment.yaml:64:24: executing "signoz/charts/k8s-infra/templates/otel-deployment/deployment.yaml" at <include "otel.endpoint" .>: error calling include: template: signoz/charts/k8s-infra/templates/_helpers.tpl:249:22: executing "otel.endpoint" at <.Chart.IsRoot>: can't evaluate field IsRoot in type interface {}

SigNoz/signoz

#2363 (traces): column suggestions API Issue created by makeavish API which fetches suggestions for columns in list view SigNoz/signoz

#2364 (logs): column suggestions API Issue created by nityanandagohain This will be used in the list view to show/hide columns SigNoz/signoz

#2365 feat: multiple values can be selected Pull request opened by palashgdev Close #2300 SigNoz/signoz GitHub Actions: playwright GitHub Actions: build-query-service GitHub Actions: Ensure Pull Request has a linked issue. GitHub Actions: Codeball GitHub Actions: dependency-review GitHub Actions: update_release_draft GitHub Actions: lint-commits GitHub Actions: build-frontend ✅ No checks have passed 0/8 successful checks

1 new commit pushed to

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

by palashgdev

<https://github.com/SigNoz/signoz/commit/174fc107c22fc60969222771bda9cf0e4c58d026|174fc107>

- fix: scrollbar issue on widget (#2359) SigNoz/signoz

Deployment to staging by palashgdev SigNoz/signoz

#2366 Highlight searched value in logs Issue created by nityanandagohain When something is searched, it should be highlighted in the logs. SigNoz/signoz

#180 Nginx-ingress error when installing or upgrading helm chart according to documentation Issue created by nicot4e When enabling the Nginx Ingress controller according to https://signoz.io/docs/tutorial/setting-up-tls-for-signoz/#enable-nginx-ingress-controller I get the following message:

post-upgrade hooks failed: unable to build kubernetes object for post-upgrade hook signoz/templates/cert-issuer.yaml: error validating "": error validating data: ValidationError(ClusterIssuer.spec.acme.solvers[0]): unknown field "ingress" in io.cert-manager.v1.ClusterIssuer.spec.acme.solvers

Is this a compatibility issue? Is there any workaround? I've tried multiple combinations of override-values.yaml configuration to no avail. Some details about my setup: A fresh and pretty standard Google GKE Kubernetes cluster version 1.24.9-gke.2000 (I switched back to a standard cluster because Helm install on a GKE autopilot cluster didn't work, I guess I'm waiting for #175 ) SigNoz/charts

#2358 feat: allow selection of multiple tag values Pull request opened by makeavish on <!date^1677129464^{date_short}|2023-02-23T05:17:44Z> SigNoz/signoz GitHub Actions: Ensure Pull Request has a linked issue. GitHub Actions: playwright GitHub Actions: lint-commits ✅ 9 other checks have passed 9/12 successful checks

1 new commit pushed to

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

by makeavish

<https://github.com/SigNoz/signoz/commit/1f44f089e02733d14b5dba3ed413e3a58cbed002|1f44f089>

- feat: multiple values can be selected (#2365) SigNoz/signoz

Deployment to staging by makeavish SigNoz/signoz

#2367 Investigate http.method tag issues with SigNoz UI Issue created by SenorMooMoo When using net/http Client any outgoing request is recorded as an external span and the span kind is client. This will result in http.method not being recorded as normal and not showing in the SigNoz UI. SigNoz/signoz

#2368 Show available metrics in SigNoz which can help users in choosing right metrics for dashboard Issue created by pranay01 Request from Slack community so like for the dashboard, I get auto fill for the metrics but I can't like get a table to see all the attributes etc. So its hard to discover the data I want to put in my dashboard. If I know exactly what I want its pretty good currently. Something like the grafana explore tab would be great. Slack Message SigNoz/signoz

#2369 (logs): Parse and convert filters to the clickhouse where ( columns, attributes ) Issue created by nityanandagohain 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

#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

#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

#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

#2374 (logs): limit, offset and pagesize Issue created by nityanandagohain • Pagination in list view without aggregation. - 0.5D • Id for timestamp • limit offset for others • Pagination with aggregation - 0.5D • ID for timestamp • limit offset for others 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

#2376 (common): Formula support in query builder, same and across db's Issue created by nityanandagohain • containing queries in the same data source • containing queries across different data source SigNoz/signoz

#2377 fix: resolves alert charts issue with 1 hr timerame Pull request opened by mindhash This PR resolves #2295 SigNoz/signoz GitHub Actions: lint-commits GitHub Actions: Ensure Pull Request has a linked issue. GitHub Actions: playwright ✅ 10 other checks have passed 10/13 successful checks

1 new commit pushed to

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

by srikanthccv

<https://github.com/SigNoz/signoz/commit/ab514cc0f2baf47eb88890e3a11e5674acfc887d|ab514cc0>

- fix: changed ask admin message (#2215) SigNoz/signoz

Deployment to staging by srikanthccv SigNoz/signoz

1 new commit pushed to

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

by srikanthccv

<https://github.com/SigNoz/signoz/commit/9d1305f174618f1fb25d08c453b292b68c9c854e|9d1305f1>

- fix: resolves alert charts issue with 1 hr timerame (#2377) SigNoz/signoz