#96 (logs): store the resource attributes separately Issue created by srikanthccv I believe this is already done for logs. Verify once and close. SigNoz/signoz-otel-collector

#97 (traces): store the resource attributes separately Issue created by srikanthccv SigNoz/signoz-otel-collector

#98 (metrics): store the resource attributes separately Issue created by srikanthccv SigNoz/signoz-otel-collector

3 new commits pushed to

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

by ankitnayan

<https://github.com/SigNoz/signoz/commit/c8a1a8600e387532d0164c92fb765e22c05164ce|c8a1a860>

- chore: 📌 pin version: SigNoz 0.16.1

<https://github.com/SigNoz/signoz/commit/7c8afc2e1cef5b7c31655ba971504eaf1fb73a67|7c8afc2e>

- Merge pull request #2258 from SigNoz/release/v0.16.1

<https://github.com/SigNoz/signoz/commit/8965b9b503c6fc5ce49e8030f27e4cec5d703edc|8965b9b5>

- Merge branch 'main' into develop SigNoz/signoz

Deployment to staging by ankitnayan SigNoz/signoz

1 new commit pushed to

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

by palashgdev

<https://github.com/SigNoz/signoz/commit/bad80def907186b7cf67c9bb070dd24f24e9d15c|bad80def>

- feat: add list and table views for logs (#2163) SigNoz/signoz

Deployment to staging by palashgdev SigNoz/signoz

#1848 Compact and/or customisable log view layout Issue created by wfhartford Is your feature request related to a problem? I would like to be able to read application log messages in a format similar to a typical log file. Describe the solution you'd like An option on the view log events screen which displays one log event per line showing just the most vital information, such as timestamp, log level, logger name, and message text. Ideally there should be a way to customize the fields shown; for example, there may be cases where host name is important, but logger name is not. Describe alternatives you've considered The current log view, which shows the message and timestamp in a JSON format is usable, but each log message takes up a lot of screen space, making it harder on the eyes to scan log messages. Additional context Attached image shows the current log view, this large image shows only three log entries. Compare the above to a comparable screen in Elastic Kibana, where a much smaller area displays far more information: SigNoz/signoz

#2266 fix: onSearch callback is updated Pull request opened by palashgdev Close #2259 SigNoz/signoz GitHub Actions: build-query-service GitHub Actions: Codeball GitHub Actions: Ensure Pull Request has a linked issue. GitHub Actions: update_release_draft GitHub Actions: build-frontend GitHub Actions: dependency-review GitHub Actions: playwright GitHub Actions: lint-commits GitHub Actions: build-ee-query-service ✅ No checks have passed 0/9 successful checks

#2267 fix: onDrag is updated Pull request opened by palashgdev Close #2194 SigNoz/signoz GitHub Actions: build-query-service GitHub Actions: build-frontend GitHub Actions: remove GitHub Actions: Codeball GitHub Actions: playwright GitHub Actions: update_release_draft GitHub Actions: lint-commits GitHub Actions: build-ee-query-service GitHub Actions: Ensure Pull Request has a linked issue. GitHub Actions: dependency-review ✅ No checks have passed 0/10 successful checks

1 new commit pushed to

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

by palashgdev

<https://github.com/SigNoz/signoz/commit/dca0b11acdd62cc02d454ab8cd0d2e67fc2898a2|dca0b11a>

- fix: onSearch callback is updated (#2266) 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/2fa265ff2e8ccfac60aeec41db150705615b6e1f|2fa265ff>

- fix: onDrag is updated (#2267) SigNoz/signoz

Deployment to staging by palashgdev SigNoz/signoz

#2268 Dependency graph for dependent services on service page Issue created by makeavish In a large microservices architecture, it becomes difficult to understand which services are affected by outage at one service. And also it isn't easy to know if a service is experiencing outage because of other services. Possible Solution: Show the services on which service is directly dependent in service view page on SigNoz. SigNoz/signoz

#2269 FE(Test): no test matches in the windows Issue created by palashgdev Bug description Please describe. If this affects the front end, screenshots would be of great help. no test found Expected behavior jest should be able to run the test How to reproduce yarn jest SigNoz/signoz

#2270 test: testMatch is updated in jest Pull request opened by palashgdev Close #2269 SigNoz/signoz GitHub Actions: Ensure Pull Request has a linked issue. GitHub Actions: playwright GitHub Actions: lint-commits GitHub Actions: Ensure Pull Request has a linked issue. ✅ 9 other checks have passed 9/13 successful checks

1 new commit pushed to

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

by palashgdev

<https://github.com/SigNoz/signoz/commit/28142764af35a85233aa147a358a35ccd1f4bd9b|28142764>

- chore: testMatch is updated (#2270) SigNoz/signoz

Deployment to staging by palashgdev SigNoz/signoz

#2271 FIX: The last timestamp label overflows in the flamegraph of trace detail page Pull request opened by gitstart Fixes #865 Demo SigNoz/signoz GitHub Actions: Codeball GitHub Actions: playwright GitHub Actions: lint-commits ✅ 10 other checks have passed 10/13 successful checks

#2272 S3 Retention Testing Issue created by SenorMooMoo When S3 retention is enabled but the cluster fails to get the bucket will it continue to use the volumes? SigNoz/signoz

#2273 Span in trace page not showing properly Issue created by abhinavramana Bug description How to reproduce 1. Create a scenario where child spans have 1 ms while the parent levels spans will have 600x of the same duration. 2. Open the trace detail page Version information • Signoz version: 0.16.1 • Browser version: Firefox • Your OS and version: Ubuntu 22.04 • *Your CPU Architecture*(ARM/Intel): Additional context Thank you for your bug report – we love squashing them! SigNoz/signoz

#2274 FE: remove @types/redux Pull request opened by gitstart Fixes #2081 SigNoz/signoz GitHub Actions: playwright GitHub Actions: lint-commits ✅ 10 other checks have passed 10/12 successful checks

#2275 chore: health endpoint related changes Pull request opened by prashant-shahi • use

RespondError

for /health route handler • ignore /health endpoint for telemetry • use /health endpoint for health check Signed-off-by: Prashant Shahi prashant@signoz.io SigNoz/signoz GitHub Actions: playwright GitHub Actions: Codeball GitHub Actions: build-ee-query-service GitHub Actions: dependency-review GitHub Actions: Ensure Pull Request has a linked issue. ✅ No checks have passed 0/5 successful checks

#2276 FE: line break is not consistence in windows Issue created by palashgdev Bug description Please describe. If this affects the front-end, screenshots would be of great help. Expected behavior there should not be any extra eslint issues regarding the line breaks SigNoz/signoz

#2277 chore: linebreak style is updated Pull request opened by palashgdev Close #2276 SigNoz/signoz GitHub Actions: lint-commits GitHub Actions: Ensure Pull Request has a linked issue. GitHub Actions: playwright ✅ 9 other checks have passed 9/12 successful checks

#174 replace deprecated pod_association from K8sattribute Processor Issue created by prashant-shahi

k8sattributesprocessor@v0.66.0/factory.go:292	Deprecated pod_association configuration detected. Please replace:

pod_association:
- from: resource_attribute
  name: k8s.pod.ip
- from: resource_attribute
  name: k8s.pod.uid
- from: connection

with

pod_association:
- sources:
  - from: resource_attribute
    name: k8s.pod.ip
- sources:
  - from: resource_attribute
    name: k8s.pod.uid
- sources:
  - from: connection

SigNoz/charts

#2278 [Alerts] Webhook Server for alert routing Issue created by mindhash Currently, the webhooks enable external integrations with systems like ms teams, google chat etc. but requires development skills to parse webhook response and transform to the third-party system requests. Solution: Build an example webhook server will help community build their own integrations. SigNoz/signoz

#2279 [Alerts] Email Integration for sending alerts Issue created by mindhash Alerts have a good potential creating engagement within product. An email integration would help users setup alerting to send messages to google groups / email groups. This will help integrating alerts in current flow of user teams. SigNoz/signoz

#2280 Import JSON File New discussion created by rboada04 We have serveral microservices running on servers that don't have network access. The microservices are wired up to send trace data to a collector which is then written to JSON files using the OTel File Exporter. We would like to be able to import the JSON trace files into Signoz running on our local machines; however, the UI doesn't seem to support importing of JSON files. Can you point me in the correct direction? I'm thinking we need to send the JSON data over OTLP/HTTP. Are there plans to support the import of JSON trace, metrics, and log files in the UI? SigNoz/signoz