Release - k8s-infra-0.4.1 New release published by github-actions[bot] Helm chart for collecting metrics and logs in K8s SigNoz/charts

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

#126 chore(signoz): pin charts: k8s-infra v0.4.1 and related changes Pull request opened by prashant-shahi Signed-off-by: Prashant Shahi prashant@signoz.io SigNoz/charts

#1946 fix: :bug: resolve redundant metrics issue in Docker and Swarm Pull request opened by prashant-shahi Signed-off-by: Prashant Shahi prashant@signoz.io SigNoz/signoz

4 new commits pushed to

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

by prashant-shahi

<https://github.com/SigNoz/charts/commit/c72bb26b3352ad58a60bfb9aee3cda75a64fdb72|c72bb26b>

- chore(signoz): 📌 pin charts: k8s-infra v0.4.1 and related changes

<https://github.com/SigNoz/charts/commit/3d0a5c98fbed6517a15d61ad68b35ccf11fb6d1f|3d0a5c98>

- chore: 📌 pin versions: SigNoz 0.13.0, SigNoz OtelCollector 0.66.1

<https://github.com/SigNoz/charts/commit/824d446561d7538d97c30a388e58b0a8b23d7529|824d4465>

- chore(release): 🔖 Bump up signoz to 0.7.0

<https://github.com/SigNoz/charts/commit/5167ecf062682f928c1d8c42c457d27396900cd9|5167ecf0>

- Merge pull request #126 from SigNoz/release/signoz-0.7.0 SigNoz/charts

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

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

#1947 fix: Logs double api is called Pull request opened by palashgdev close #1930 SigNoz/signoz

#1948 feat: react is updated to v18 Pull request opened by palashgdev Can be taken care after #1880 SigNoz/signoz

#71 Cache policy in grok parser. Issue created by nityanandagohain

Any reason why FIFO is used here instead of the LRU kind cache? Say there is an item which is added first to the queue, but it's also the most commonly used one for all the log messages, in that kicking that out in favour of some new item doesn't seem wise

. from Srikanth^ 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/27cd514fa599d69bf40ed2b1de634429e218988b|27cd514f>

- fix: Logs double api is called (#1947) SigNoz/signoz

#1949 No logs found error due to same start and end timestamp Issue created by nityanandagohain Steps • Open a new browser (important) • Open Signoz logs • Press next -> previous -> previous • Results in no logs found Interestingly it doesn't happen all the time. SigNoz/signoz

#1950 fix: no found is updated Pull request opened by palashgdev Close #1949 SigNoz/signoz

1 new commit pushed to

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

by palashgdev

<https://github.com/SigNoz/signoz/commit/6ba5c0ecad125fdbef6026715a0849c83195d433|6ba5c0ec>

- fix: apply filters on count of exceptions (#1945) SigNoz/signoz

#1685 'Something went wrong' - invalid memory address or nil pointer dereference goroutine Issue created by geemark on <!date^1667503431^{date_short}|2022-11-03T19:23:51Z> Bug description "Something went wrong" message on Service dashboard in the "Rate (ops/s)" and "Error Percentage" chart panels. Expected behavior Expected the charts to show. How to reproduce Don't know. It happens to about half my services, but works on the others. Version information • Signoz version: 0.11.2 • Browser version: Firefox 106 • Your OS and version: Windows 11 Pro • *Your CPU Architecture*(ARM/Intel): Intel Core i7 64bit Additional context I tried digging in the pod logs, and found this in the query service around the time I reload the UI page: ``` *"http: panic serving 10.244.0.23646738 runtime error: invalid memory address or nil pointer dereference goroutine" * 2022-11-03T191730.730Z �[34mINFO�[0m app/server.go:221 /api/v1/service/top_level_operations timeTaken: 48.77619ms 2022-11-03T191730.770Z �[35mDEBUG�[0m clickhouseReader/reader.go:1663 SELECT quantile(0.5)(durationNano) as p50, quantile(0.95)(durationNano) as p95, quantile(0.99)(durationNano) as p99, COUNT(*) as numCalls, name FROM signoz_traces.signoz_index_v2 WHERE serviceName = @serviceName AND timestamp>= @start AND timestamp<= @end GROUP BY name ORDER BY p99 DESC LIMIT 10 2022-11-03T191730.771Z �[34mINFO�[0m app/server.go:221 /api/v1/service/top_operations timeTaken: 94.04537ms 2022-11-03T191730.776Z �[35mDEBUG�[0m clickhouseReader/reader.go:849 SELECT toStartOfInterval(timestamp, INTERVAL @interval minute) as time, quantile(0.99)(durationNano) as p99, quantile(0.95)(durationNano) as p95, quantile(0.50)(durationNano) as p50, count(*) as numCalls FROM signoz_traces.signoz_index_v2 WHERE serviceName = @serviceName AND name In [@names] AND timestamp>= @start AND timestamp<= @end GROUP BY time ORDER BY time DESC 2022-11-03T191730.808Z �[35mDEBUG�[0m clickhouseReader/reader.go:875 SELECT toStartOfInterval(timestamp, INTERVAL @interval minute) as time, count(*) as numErrors FROM signoz_traces.signoz_index_v2 WHERE serviceName = @serviceName AND name In [@names] AND timestamp>= @start AND timestamp<= @end AND statusCode=2 GROUP BY time ORDER BY time DESC 2022-11-03T191730.809Z �[34mINFO�[0m app/server.go:221 /api/v1/service/overview timeTaken: 132.539344ms 2022-11-03T191731.153Z �[31mERROR�[0m app/http_handler.go:1105 query was canceled in query queue go.signoz.io/signoz/pkg/query-service/app.(*APIHandler).queryRangeMetrics /go/src/github.com/signoz/signoz/pkg/query-service/app/http_handler.go:1105 go.signoz.io/signoz/pkg/query-service/app.ViewAccess.func1 /go/src/github.com/signoz/signoz/pkg/query-service/app/http_handler.go:248 net/http.HandlerFunc.ServeHTTP /usr/local/go/src/net/http/server.go:2047 go.signoz.io/signoz/ee/query-service/app.loggingMiddleware.func1 /go/src/github.com/signoz/signoz/ee/query-service/app/server.go:220 net/http.HandlerFunc.ServeHTTP /usr/local/go/src/net/http/server.go:2047 go.signoz.io/signoz/ee/query-service/app.(*Server).analyticsMiddleware.func1 /go/src/github.com/signoz/signoz/ee/query-service/app/server.go:264 net/http.HandlerFunc.ServeHTTP /usr/local/go/src/net/http/server.go:2047 go.signoz.io/signoz/ee/query-service/app.setTimeoutMiddleware.func1 /go/src/github.com/signoz/signoz/ee/query-service/app/server.go:287 net/http.HandlerFunc.ServeHTTP /usr/local/go/src/net/http/server.go:2047 github.com/gorilla/mux.(*Router).ServeHTTP /go/pkg/mod/github.com/gorilla/mux@v1.8.0/mux.go:210 github.com/rs/cors.(*Cors).Handler.func1 /go/pkg/mod/github.com/rs/cors@v1.7.0/cors.go:219 net/http.HandlerFunc.ServeHTTP /usr/local/go/src/net/http/server.go:2047 github.com/gorilla/handlers.CompressHandlerLevel.func1 /go/pkg/mod/github.com/gorilla/handlers@v1.5.1/compress.go:141 net/http.HandlerFunc.ServeHTTP /usr/local/go/src/net/http/server.go:2047 net/http.serverHandler.ServeHTTP /usr/local/go/src/net/http/server.go:2879 net/http.(*conn).serve /usr/local/go/src/net/http/server.go:1930 2022/11/03 191731 http: superfluous response.WriteHeader call from github.com/gorilla/handlers.(*compressResponseWriter).WriteHeader (compress.go:26) 2022/11/03 191731 http: panic serving 10.244.0.23646738 runtime error: invalid memory address or nil pointer dereference goroutine 347170 [running]: net/http.(*conn).serve.func1() /usr/local/go/src/net/http/server.go:1802 +0xb9 panic({0x1ae4fe0, 0x2dd2a70}) /usr/local/go/src/runtime/panic.go:1047 +0x266 go.signoz.io/signoz/pkg/query-service/app.(*APIHandler).queryRangeMetrics(0xc00015f010, {0x2100bb8, 0xc000688fc0}, 0xc000e22300) /go/src/github.com/signoz/signoz/pkg/query-service/app/http_handler.go:1119 +0x39c go.signoz.io/signoz/pkg/query-service/app.ViewAccess.func1({0x2100bb8, 0xc000688fc0}, 0x48cab7) /go/src/github.com/signoz/signoz/pkg/query-service/app/http_handler.go:248 +0x104 net/http.HandlerFunc.ServeHTTP(0x199a580, {0x2100bb8, 0xc000688fc0}, 0xc000e49458) /usr/local/go/src/net/http/server.go:2047 +0x2f go.signoz.io/signoz/ee/query-service/app.loggingMiddleware.func1({0x2100bb8, 0xc000688fc0}, 0x1eea701) /go/src/github.com/signoz/signoz/ee/query-service/app/server.go:220 +0xca net/http.HandlerFunc.ServeHTTP(0x0, {0x2100bb8, 0xc000688fc0}, 0xc0041dcaf0) /usr/local/go/src/net/http/server.go:2047 +0x2f go.signoz.io/signoz/ee/query-service/app.(*Server).analyticsMiddleware.func1({0x21091c8, 0xc0041dcaa0}, 0xdf8475801) /go/src/github.com/signoz/signoz/ee/query-service/app/server.go:264 +0xf3 net/http.HandlerFunc.ServeHTTP(0x2113480, {0x21091c8, 0xc0041dcaa0}, 0x13) /usr/local/go/src/net/http/server.go:2047 +0x2f go.signoz.io/signoz/ee/query-service/app.setTimeoutMiddleware.func1({0x21091c8, 0xc0041dcaa0}, 0xc000e22200) /go/src/github.com/signoz/signoz/ee/query-service/app/server.go:287 +0x2f6 net/http.HandlerFunc.ServeHTTP(0xc000e22100, {0x21091c8, 0xc0041dcaa0}, 0x71d801) /usr/local/go/src/net/http/server.go:2047 +0x2f github.com/gorilla/mux.(*Router).ServeHTTP(0xc0001ba240, {0x21091c8, 0xc0041dcaa0}, 0xc000e22000) /go/pkg/mod/github.com/gorilla/mux@v1.8.0/mux.go:210 +0x1cf github.com/rs/cors.(*Cors).Handler.func1({0x21091c8, 0xc0041dcaa0}, 0xc000e22000) /go/pkg/mod/github.com/rs/cors@v1.7.0/cors.go:219 +0x1bd net/http.HandlerFunc.ServeHTTP(0x0, {0x21091c8, 0xc0041dcaa0}, 0xc000b900d0) /usr/local/go/src/net/http/server.go:2047 +0x2f github.com/gorilla/handlers.CompressHandlerLevel.func1({0x21080e8, 0xc000818c40}, 0xc000e22000) /go/pkg/mod/github.com/gorilla/handlers@v1.5.1/compress.go:141 +0x666 net/http.HandlerFunc.ServeHTTP(0xc00025a418, {0x21080e8, 0xc000818c40}, 0x468e4e) /usr/local/go/src/net/http/server.go:2047 +0x2f net/http.serverHand… SigNoz/signoz

#1951 Remove `Beta` tag from logs in left side bar Issue created by pranay01 With v0.14.0 release, logs would be decently mature and stress tested. We should remove the

Beta

milestone SigNoz/signoz

#1952 Removing Beta tag from Logs Pull request opened by pranay01 SigNoz/signoz

1 new commit pushed to

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

by palashgdev

<https://github.com/SigNoz/signoz/commit/31a3bc09c89a5b514b135d1c4e9293a1f6c1a278|31a3bc09>

- Removing Beta tag from Logs (#1952) SigNoz/signoz

#72 clickhousetracesexporter fails to write data Issue created by srikanthccv The user faced an issue with getting traces ingested while there was no issue from the metrics/logs exporter.

<http://github.com/SigNoz/signoz-otel-collector/exporter/clickhousetracesexporter.(*SpanWriter).writeBatch|github.com/SigNoz/signoz-otel-collector/exporter/clickhousetracesexporter.(*SpanWriter).writeBatch>
	/src/exporter/clickhousetracesexporter/writer.go:129
<http://github.com/SigNoz/signoz-otel-collector/exporter/clickhousetracesexporter.(*SpanWriter).backgroundWriter|github.com/SigNoz/signoz-otel-collector/exporter/clickhousetracesexporter.(*SpanWriter).backgroundWriter>
	/src/exporter/clickhousetracesexporter/writer.go:108
2022-12-30T16:54:32.516Z	error	clickhousetracesexporter/writer.go:109	Could not write a batch of spans	{"kind": "exporter", "data_type": "traces", "name": "clickhousetraces", "error": "dial tcp 172.27.0.2:9000: connect: connection refused"}
<http://github.com/SigNoz/signoz-otel-collector/exporter/clickhousetracesexporter.(*SpanWriter).backgroundWriter|github.com/SigNoz/signoz-otel-collector/exporter/clickhousetracesexporter.(*SpanWriter).backgroundWriter>

Slack thread: https://signoz-community.slack.com/archives/C01HWQ1R0BC/p1672250812161599 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/126c9238bad388da2859d178352b9dd0dcf6da55|126c9238>

- feat: loading is added in the button (#1927) SigNoz/signoz

#1953 logs(UI): keep counter of current page for logs in logs reducer Issue created by palashgdev Is your feature request related to a problem? Please describe. for next set of enchantment for logs we need to keep the counter of the current page we are in so that we can disable the logs next and previous button and update next, prev button accordingly Describe the solution you'd like we can update the page number in the redux state when user press next or previous this will fix #1949 SigNoz/signoz

#1954 Flickering on Service map page on refresh Issue created by pranay01 https://www.loom.com/share/cc3b064650894f9baed59c379d9e0c21 SigNoz/signoz

#1955 Are the chaining in dashboard variables? Issue created by pranay01 are the dashboard variables dependent on previous variables? Say I have

App Name

and

Instance

, surely I don't want to show all instances of all apps! Slack Message SigNoz/signoz

#1956 Enable a way to compare 2 traces in SigNoz Issue created by pranay01 Example from Jaeger UI SigNoz/signoz

#1957 Enable a way to compare 2 sets of filtered spans Issue created by pranay01 Example Features to easily compare • deployment versions' RED metrics • baseline vs regression • time period comparison e.g. previous period/week SigNoz/signoz

#1785 Enable google auth sso Issue created by ankitnayan on <!date^1669756249^{date_short}|2022-11-29T21:10:49Z> SigNoz/signoz

1 new commit pushed to

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

by prashant-shahi

<https://github.com/SigNoz/signoz/commit/57d28be9f5ce8b8b1f8c1d8452f939c24a681251|57d28be9>

- fix: 🐛 resolve redundant metrics issue (#1946) SigNoz/signoz

#127 resolve service account create issue and other fixes Pull request opened by prashant-shahi Fixes #123 SigNoz/charts

#1958 Enable `Saved Views` with specific filters in logs search Issue created by pranay01 Is your feature request related to a problem? Users may want to save a particular filter which they commonly apply when they explore logs. Currently there is no way to save a filter or view in logs Describe the solution you'd like Provide provision to create

Saved Views

which has specific filters defined so that users can filter the results very easily, especially for queries which they use often Describe alternatives you've considered Typing the filter query in search bar everytime Additional context Intial Design on how this could look like Thank you for your feature request – we love each and every one! SigNoz/signoz

4 new commits pushed to

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

by prashant-shahi

<https://github.com/SigNoz/charts/commit/2586e9668052abadd0ecf8253b78aaed8f1c4449|2586e966>

- chore(k8s-infra): 🔧 create flag template for otelAgent service account

<https://github.com/SigNoz/charts/commit/8c30efb2440710d83eb434a0f23e1ad9dbdfd108|8c30efb2>

- fix(k8s-infra): 🐛 invalid configurations resolved

<https://github.com/SigNoz/charts/commit/3cd47facd8a0190ae7532b7c858b508d170c830c|3cd47fac>

- chore(release): 🔖 Bump up k8s-infra to 0.4.2

<https://github.com/SigNoz/charts/commit/2eaddd76ef0f84432bbcb4eaa5b682f1c440d357|2eaddd76>

- Merge pull request #127 from SigNoz/prashant/service-fix SigNoz/charts