1 new commit pushed to

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

by palashgdev

<https://github.com/SigNoz/signoz/commit/8bfb0b5088e1a8c9fe8108ef7e2a30f66d92a70d|8bfb0b50>

- QueryBuilder filters for log pipelines (#3587) SigNoz/signoz

Deployment to staging by palashgdev SigNoz/signoz

Release - v0.29.3 New release published by prashant-shahi What's Changed • update webpack config to add segment ID (#3599) @YounixM • ci(frontend): 👷 update CI job for frontend EE build (#3596) @prashant-shahi • [Refactor]: polished the log UI (#3591) @Rajat-Dabade • Add support in query service for querybuilder filterset based log pipelines (#3560) @rkssisodiya • [Snyk] Security upgrade nginx from 1.24.0-alpine to 1.25.2-alpine (#3589) @YounixM • feat: onboarding flow - add analytics - update webpack config (#3597) @YounixM • feat: onboarding flow - add analytics (#3594) @YounixM Full Changelog: v0.29.2...v0.29.3 SigNoz/signoz

1 new commit pushed to

<https://github.com/SigNoz/charts/tree/main|main>

by prashant-shahi

<https://github.com/SigNoz/charts/commit/02eb7dc4ecea92bad42121e346b87d2729ffe2b0|02eb7dc4>

- Release/signoz 0.25.3 (#293) SigNoz/charts

Release - signoz-0.25.3 New release published by github-actions[bot] SigNoz Observability Platform Helm Chart SigNoz/charts

Deployment to github-pages by github-pages[bot] SigNoz/charts

#3601 FE(LOGS): Logs Explorer page is not active in the sidenav Issue created by palashgdev SigNoz/signoz

#3603 We should use a clickable chip with color codes for different `severity_text`. Clicking a chip should add the filter automatically. Issue created by palashgdev

We should use a clickable chip with color codes for different `severity_text`. Clicking a chip should add the filter automatically.

Originally posted by @Ankit Nayan in #3303 (comment) SigNoz/signoz

1 new commit pushed to

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

by palashgdev

<https://github.com/SigNoz/signoz/commit/31b898b2c60d740e8ac39822cee35ed6249d9737|31b898b2>

- fix: active menu logic is updated (#3602) SigNoz/signoz

#3602 fix: active menu logic is updated Pull request merged by palashgdev SigNoz/signoz

Deployment to staging by palashgdev SigNoz/signoz

#3605 [Fix]: copy to clipboard without quotes Pull request opened by Rajat-Dabade Fix the copy to the clipboard without quotes. SigNoz/signoz GitHub Actions: Ensure Pull Request has a linked issue. ✅ 7 other checks have passed 7/8 successful checks

#178 Use logical name 'peer.service' for the service map Issue created by jdehaan We noticed that with several redis services setup (session tokens, cache, ...), the service map displayed only displays a single "redis" bubble in signoz UI. According to the opentelemetry spec, a way to specify the logical instances of a service from the client perspective (application being instrumented) is to use `peer.service`. As far as I understand the code the service map is built from information which comes from the query service which in turn becomes its information from the clickhouse database. Then I drilled down to the code here: `tagMap['db.system'] as dest,` Shouldn't this use primarily the

peer.service

attribute instead of

db.system

? IMHO

dest

should be changed to be •

peer.service

if set •

db.system

otherwise (fallback) Tested changes working:

-- in dependency_graph_minutes_db_calls_mv_v2
  coalesce(tagMap['peer.service'], tagMap['db.system']) as dest,

-- in dependency_graph_minutes_messaging_calls_mv_v2
  coalesce(tagMap['peer.service'], tagMap['messaging.system']) as dest,

What is your opinion? PS: I tried the above code change and matching migrations added. I did a brute force replacement of the materialized view, maybe there is a more subtle way by updating.... SigNoz/signoz-otel-collector

1 new commit pushed to

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

by palashgdev

<https://github.com/SigNoz/signoz/commit/5c437dd8f99a87661253c3a2d7366c888ab29567|5c437dd8>

- fix: the scroll issue and name issue in save view (#3604) SigNoz/signoz

#3604 [Fix]: the scroll issue and name issue in save view Pull request merged by palashgdev SigNoz/signoz

Deployment to staging by palashgdev SigNoz/signoz

#3606 feat: severityText is added Pull request opened by palashgdev Close #3303 SigNoz/signoz GitHub Actions: build-frontend GitHub Actions: build-frontend-ee ✅ 6 other checks have passed 6/8 successful checks

#3607 feat: default options is updated Pull request opened by palashgdev Close #2361 please delete

metricsTimeDurations

key from local storage to test this PR if any SigNoz/signoz GitHub Actions: Deploy PR branch to testing GitHub Actions: e2e-k3s ✅ 9 other checks have passed 9/11 successful checks

#3608 [Fix]: Using exported dashboards as input to dashboard provisioning Pull request opened by Haavasma There is a mismatch between exporting dashboard and using them to auto provision dashboards when instantiating signoz. #3595 This PR includes the "uuid" as part of the

data

field in dashboards when exporting, such that when the exported file is used for automatic provisioning in

pkg/query-service/app/dashboards/provision.go

the "uuid" is present, prohibiting issue with

[interface is nil](panic: interface conversion: interface {} is nil, not string)

when using the raw exported json during provisioning, as the missing "uuid" field will be present. SigNoz/signoz ✅ All checks have passed 1/1 successful checks

1 new commit pushed to

<https://github.com/SigNoz/charts/tree/main|main>

by prashant-shahi

<https://github.com/SigNoz/charts/commit/d0eca18dd32dd2ae668126b163d4120d9ed543f9|d0eca18d>

- FIX: Alertmanager - Add arg cluster.advertise-address at all times (#285) SigNoz/charts

Release - signoz-0.25.4 New release published by github-actions[bot] SigNoz Observability Platform Helm Chart SigNoz/charts

Deployment to github-pages by github-pages[bot] SigNoz/charts

#179 span metrics scraping broken pipe error Issue created by srikanthccv

2023-09-22T13:55:50+05:30 | <http://go.opentelemetry.io/contrib/instrumentation/net/http/otelhttp.(*Handler).ServeHTTP|go.opentelemetry.io/contrib/instrumentation/net/http/otelhttp.(*Handler).ServeHTTP>
2023-09-22T13:55:50+05:30 | /home/runner/go/pkg/mod/github.com/prometheus/client_golang@v1.15.1/prometheus/promhttp/http.go:187
2023-09-22T13:55:50+05:30 | <http://github.com/prometheus/client_golang/prometheus/promhttp.HandlerForTransactional.func1.2|github.com/prometheus/client_golang/prometheus/promhttp.HandlerForTransactional.func1.2>
2023-09-22T13:55:50+05:30 | /home/runner/go/pkg/mod/github.com/open-telemetry/opentelemetry-collector-contrib/exporter/prometheusexporter@v0.79.0/log.go:23
2023-09-22T13:55:50+05:30 | <http://github.com/open-telemetry/opentelemetry-collector-contrib/exporter/prometheusexporter.(*promLogger).Println|github.com/open-telemetry/opentelemetry-collector-contrib/exporter/prometheusexporter.(*promLogger).Println>
2023-09-22T13:55:50+05:30 | {"kind": "exporter", "data_type": "metrics", "name": "prometheus"}
2023-09-22T13:55:50+05:30 | 2023-09-22T08:25:49.996Z error prometheusexporter@v0.79.0/log.go:23 error encoding and sending metric family: write tcp -> : write: broken pipe

SigNoz/signoz-otel-collector

1 new commit pushed to

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

by srikanthccv

<https://github.com/SigNoz/signoz/commit/043e5ca880a9a16e8461ab12f00bcafba98263c6|043e5ca8>

- fix: skip first record only for rate metrics (#3609) SigNoz/signoz

#3609 fix: skip first record only for rate metrics Pull request opened by srikanthccv Currently, the threshold rule logic skips the first sample of the result regardless of the type of operator and source. The original intention was to skip the rate queries only as the first sample rate is incorrect. This commit updates the logic to skip only when the data source is metric and the operator is rate kind. if the sample shouldn't be skipped

!r.shouldSkipFirstRecord()

then the first sample is directly added to

resultMap

. SigNoz/signoz GitHub Actions: Ensure Pull Request has a linked issue. ✅ 8 other checks have passed 8/9 successful checks

Deployment to staging by srikanthccv SigNoz/signoz

#3097 Dashboard-Plot Distinct by tag Issue created by sharpSteff It would be great to be able to distinct metrics values in the Query Builder by tag. Alternativly I can also use the ClickHouse Query, but in the docs I could not find any examples to query metrics values SigNoz/signoz

#3610 Value Widget with ClickHouse Query New discussion created by sharpSteff I have a query which creates a time series:

SELECT
        interval,
        COUNT(*) as countValue
    FROM (
        SELECT 
            toStartOfInterval(timestamp, toIntervalMinute(1)) AS interval,
            t1.tagMap['service.instance.id'] as instance,
            t1.tagMap['service.version'] AS version
        FROM signoz_traces.signoz_index_v2 t1
        WHERE t1.serviceName == 'myservice'
        AND t1.name == 'mytrace'
        AND t1.hasError == true
        AND t1.timestamp BETWEEN {{.start_datetime}} AND {{.end_datetime}}
    ) AS subquery 
    GROUP BY
        interval
    ORDER BY interval ASC

I like to have a Value-Widget which sums all the values in the timeframe via ClickHouse Query: However I do not find any docs what query the Value-Widget expects: I tried following:

SELECT SUM(countValue) as value 
FROM (
    SELECT
        interval,
        COUNT(*) as countValue
    FROM (
        SELECT 
            toStartOfInterval(timestamp, toIntervalMinute(1)) AS interval,
            t1.tagMap['service.instance.id'] as instance,
            t1.tagMap['service.version'] AS version
        FROM signoz_traces.signoz_index_v2 t1
        WHERE t1.serviceName == 'myservice'
        AND t1.name == 'mytrace'
        AND t1.hasError == true
        AND t1.timestamp BETWEEN {{.start_datetime}} AND {{.end_datetime}}
    ) AS subquery 
    GROUP BY
        interval
    ORDER BY interval ASC
)

However its always "0" :( SigNoz/signoz

#3611 Dropdown floating as we scroll the screen Issue created by Calm-Rock Bug description The dropdown menu are floating with the screens when I scroll down on the cloud screen and the cloud Dashboard Here are a couple of Videos : Video1, Video2 How to reproduce 1. Instrument any app on SigNoz cloud UI or Try demo website Version information • Signoz version: SigNoz Cloud • Browser version: • Your OS and version: MacOs; Ventura • *Your CPU Architecture*(ARM/Intel): ARM Additional context Thank you for your bug report – we love squashing them! SigNoz/signoz

#3612 feat: make identity call if user is logs in for first time or if identity call was not registered Pull request opened by YounixM make identity call if user is logs in for first time or if identity call was not registered SigNoz/signoz ✅ All checks have passed 8/8 successful checks