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/d2cdf401b85fca7a07f94a6cff5bcf669b964e7d|d2cdf401>

- fix: alerts page threshold only number is allowed (#2816) SigNoz/signoz

Deployment to staging by palashgdev SigNoz/signoz

#2819 Alert threshold disappears on run query Issue created by makeavish Alert threshold disappears on run query or on any changes in query. And alert name missing error is thrown when creating the alert. Both issues seems related. Loom video explaining the issue live: https://www.loom.com/share/5dee90518656411fa1d8799ef213ad44 SigNoz/signoz

#2820 Org name missing and unable to signup using invite link Issue created by makeavish New users who signup with a valid org name don't see org name after refresh: Invited users can't signup as org name is missing: SigNoz/signoz

#138 Add http.status_code to default external call dimensions Pull request opened by srikanthccv Dimension == attribute. We create external_call metrics based on the HTTP client's span data(i.e. span kind is CLIENT). These external metrics are helpful for users to see the outgoing calls from each service and their latencies and error percentages in the Services tab. Like any other metric data, a set of attributes are added by default, and the user can configure them under the spanmetrics processor config. This document gives a good idea about the component https://github.com/SigNoz/signoz-otel-collector/tree/main/processor/signozspanmetricsprocessor. The current issue is

http.status_code

is only added for the

signoz_calls

metrics but not for the external call metrics. For some users who rely on third-party APIs, it is also important to have the ability to filter by

http.status_code

instead of the span

status.code

. The reason is span

status.code

is an ERROR for 4XX from HTTP Client (OK for server) (read more here https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/trace/semantic_conventions/http.md#status), but this might not be the case for the user. By adding this dimension/attribute, we allow them to define what the error is for them. SigNoz/signoz-otel-collector ✅ All checks have passed 3/3 successful checks

1 new commit pushed to

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

by prashant-shahi

<https://github.com/SigNoz/signoz/commit/e73432df83be879e5ce5282748742c03ef1532ae|e73432df>

- fix: org name is fixed (#2810) SigNoz/signoz

Deployment to staging by prashant-shahi SigNoz/signoz

#2821 fix: add legend property to Queries Pull request opened by makeavish Legend param was not being saved to rules db when saving an alert. It was caused by missing legend property in Query structs. SigNoz/signoz GitHub Actions: Ensure Pull Request has a linked issue. GitHub Actions: e2e-k3s GitHub Actions: Deploy PR branch to testing GitHub Actions: playwright GitHub Actions: Codeball ✅ 7 other checks have passed 7/12 successful checks

#2822 [Logs] Live view with new explorer page. Issue created by nityanandagohain PRD on live view with new logs explorer page SigNoz/signoz

#2823 Show all the operations in `Key Operations` table Issue created by srikanthccv The list of operations we currently show are top 10 by P99. Top P99 doesn't always mean they are interested in it because it could be that by nature, the P99 for the service is high, which is not very useful. SigNoz/signoz

#2826 Issues with legends in dashboards Issue created by pranay01 On hover ☐ Legend keys are not really readable ☐ They are still not providing a lot of useful info, but now they are also blocking the view on the data: https://signoz-team.slack.com/archives/C05AKFYUB0B/p1685723650170439 SigNoz/signoz

#2825 Round the start and end to the nearest interval timestamp Issue created by srikanthccv Assume the current timestamp is 41551, and we want to see data for the last five minutes. The first point will start at 41051. This only includes the last 2 seconds of data, while the other points show data for full granularity interval duration. This causes the inconsistent data graph at the edges(start and end). We should round it to the nearest interval timestamps in all the places. If the start time >= 41051, there is only one record for the 30s aggregation interval, while other points have 3 records. This rounding used to be there for earlier records. More clear example SigNoz/signoz

#2827 More helpful auto completion in logs query builder Issue created by pranay01 • In the Log Query Builder, it would be helpful to have auto completion, e.g. for the severity_text field, it should show all available severity_texts • some coloring in the list based on the severity https://signoz-team.slack.com/archives/C05AKFYUB0B/p1685723650170439 SigNoz/signoz

#2828 Size of the service map control is too big, it creates unnecessary scroll bars Issue created by pranay01 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/fff2a1ae8572cc3d560d92f31fa9a71a865722dd|fff2a1ae>

- Add http.status_code to default external call dimensions (#138) SigNoz/signoz-otel-collector

#2829 allow parsing at query time for logs Issue created by pranay01 If the log lines have json as attributes, can we allow users to only query based on a key in the json - even when it was not separated into different attributes during ingestion. The use case is that many times developers send log lines which are not parsed during ingestion (as it may need communication with devops/platform team) SigNoz/signoz

#2830 DRAFT: feat: add test for groupBy Pull request opened by yeshev SigNoz/signoz GitHub Actions: create_issue_on_merge GitHub Actions: Deploy PR branch to testing GitHub Actions: e2e-k3s GitHub Actions: build-frontend GitHub Actions: playwright GitHub Actions: Ensure Pull Request has a linked issue. ✅ 6 other checks have passed 6/12 successful checks

#2832 feat: add the options menu Pull request opened by dnazarenkosignoz part of #2332 SigNoz/signoz GitHub Actions: Codeball GitHub Actions: playwright ✅ 7 other checks have passed 7/9 successful checks

#2824 fix: remove the top 10 limit on key operations table Pull request opened by srikanthccv Fixes #2823 SigNoz/signoz GitHub Actions: playwright ✅ 8 other checks have passed 8/9 successful checks

1 new commit pushed to

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

by srikanthccv

<https://github.com/SigNoz/signoz/commit/a3c917cca0b1c54e0f52cc1fc1440bc721c4e611|a3c917cc>

- fix: add legend property to Queries (#2821) SigNoz/signoz

#2576 legend formatting in alert is not saved b/w edits Issue created by srikanthccv Bug description 1. Create an alert 2. Use legend formatting to see the data properly 3. Save the alert 4. Try to edit the alert 5. Now, the legend formatting is gone, making it hard for the user to reason about the line Expected behavior The format should be saved SigNoz/signoz

Deployment to staging by srikanthccv SigNoz/signoz

#2833 query-service powered pagination in table components Issue created by srikanthccv The pagination in many parts of the product is antd powered pagination (10 records per page). We can make the search, limit, and offset a part of the API query. • Service list page • Service overview page • Trace filters page • Dashboards SigNoz/signoz

#2834 Where clause is not applied when aggregation operator is updated Issue created by makeavish Loom video: https://www.loom.com/share/a0f4b655151c4ee6bb0fb755a7abac1c SigNoz/signoz

1 new commit pushed to

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

by srikanthccv

<https://github.com/SigNoz/signoz/commit/a52c104562b8c0988e28544949db5c6b71327d17|a52c1045>

- fix: remove the top 10 limit on key operations table (#2824) SigNoz/signoz

Deployment to staging by srikanthccv SigNoz/signoz

#2835 chore: update .github/CODEOWNERS Pull request opened by srikanthccv Change some top-level file ownership that doesn't need to be blocked on for review, such as changes to Makefile etc., while also making sure the other directory owner's behaviour continues to work as it is. SigNoz/signoz GitHub Actions: build-query-service GitHub Actions: build-frontend GitHub Actions: playwright GitHub Actions: update_release_draft GitHub Actions: remove GitHub Actions: dependency-review GitHub Actions: build-ee-query-service GitHub Actions: lint-commits GitHub Actions: Codeball ✅ No checks have passed 0/9 successful checks

#2836 Traces & logs in S3 Cold Storage New discussion created by Flooze-IT Hi everyone, I actually use Signoz in my company to exploit logs and traces. Recently we have setup a cold storage with S3 buckets. The question is: Traces and logs moved in S3 are always available for requesting from the UI ? And another question: It's possible to backup the data (in S3) in another signoz instance in another Kubernetes cluster ? Many thanks SigNoz/signoz

#2837 (exceptions): errors/exceptions from the logs are missing Issue created by srikanthccv At the time of writing, the

Exceptions

tab only shows the exceptions from the span events. As an end user, I would expect the errors/exceptions from the logs to also appear in the

Exceptions

tab listing and be able to search/filter. This might be easier to do if the logs come from the logs SDK since the attributes on the log record and span event are the same for an exception. We might have to use multi-line parsing for the logs collected via traditional means such as files. SigNoz/signoz