#2991 fix(FE): dashboard query stuck on disabled. Pull request opened by sachinmk27 Expectation: User can enable/disable a query irrespective of the number of queries and formulas. Current behaviour If there is only one disabled query and zero formulas, then user cannot enable the disabled query. Closes: #2980 I think this will be easier for the user. However, I am new to the project, I am not sure if this is how the feature should work. SigNoz/signoz GitHub Actions: sonar-analysis GitHub Actions: Codeball ✅ 7 other checks have passed 7/9 successful checks

1 new commit pushed to

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

by palashgdev

<https://github.com/SigNoz/signoz/commit/9b8f7a091c000794339cc1d3b596ca97aa9a5eda|9b8f7a09>

- fix: step size is made dynamic (#2903) SigNoz/signoz

Deployment to staging by palashgdev SigNoz/signoz

#2992 Feat/list infinity scroll Pull request opened by yeshev SigNoz/signoz GitHub Actions: lint-commits GitHub Actions: Codeball GitHub Actions: sonar-analysis ✅ 6 other checks have passed 6/9 successful checks

1 new commit pushed to

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

by palashgdev

<https://github.com/SigNoz/signoz/commit/1eabacbaf487c4b07eb9ffdd1364c7779debee2f|1eabacba>

- feat: add the export panel to the traces explorer (#2983) SigNoz/signoz

#2337 Ability to create a dashboard or a panel of the explorer result to the existing dashboard in traces explorer page. Issue created by srikanthccv Users can create a dashboard out of the explorer work. There will be an action item where the user can select the

Add to dashboards

. When they click on the add to the dashboard, they can create a new dashboard or add this explorer result as a panel to the existing dashboards. They can add this to one or more dashboards. The client is expected to save the query here with the API

/api/v1/explorer/queries

with the POST request containing the payload of the composite query. The API will respond with the query ID, which will be saved to the dashboard, and the dashboard will be updated with new JSON containing the query ID. If a user decides to save it to multiple dashboards, each dashboard should have its own reference for the query, i.e. editing in one dashboard doesn't introduce the changes to the other dashboard. The client should create a separate query for each dashboard to make this happen. The implementation will be roughly like calling the save query and getting the query ID from the response and then update the dashboard JSON and repeat this step for all the user selected dashboards. When user adds the explorer query result to dashboard it should just create a new panel to the existing dashboard and MUST not alter the existing widgets. SigNoz/signoz

Deployment to staging by palashgdev SigNoz/signoz

#2993 feat: export panel in logs explorer is added Pull request opened by palashgdev Close #2346 SigNoz/signoz GitHub Actions: sonar-analysis GitHub Actions: Codeball ✅ 7 other checks have passed 7/9 successful checks

#2995 feat: create alerts is updated from trace explorer Pull request opened by palashgdev Close #2338 SigNoz/signoz GitHub Actions: sonar-analysis GitHub Actions: Codeball ✅ 7 other checks have passed 7/9 successful checks

#2332 Multiple query management in the trace explorer Issue created by srikanthccv There should be a provision to add multiple queries. The

+Query

button will create an empty query with a new label following the prior label, i.e. if the previous query is

B

, the label for the new query will be

C

. Similarly, they can add formulas in the builder. The formula labelling starts with

F1

and increases. There is a limit on the number of queries and formulas one can create on the frontend. Please see the limit is the current dashboards. The limitations about the number of queries and the formulas will apply here. The formula is just an input text box where the user can write mathematical expressions. A user can get delete one or many queries using the 'X' button available on the right side of the query. They can't get rid of the query if there is only one. There will only be one

Run Query

button, which will be sticky with the last, i.e. the button will appear along the same x0axis as the last query, which helps the user quickly run the query. SigNoz/signoz

#2335 Time series view tab in the traces explorer Issue created by srikanthccv Users can perform different aggregations on the trace data and see the result in the graph. For instance, • They may want to look at the

P99

of the span duration for the last 30 minutes. • They may want to

COUNT

the total number of spans in the last 30 minutes with particular criteria. The response for this will a plotted in the time series chart. There will be an option to plot each query result in a different widget panel or everything in the same widget. When they are plotted with a separate widget for each query, there will be two widgets in the UI for a row. When they inspect the charts and move the mouse from one timestamp to another, there will be another line in each graph highlighting the value at that timestamp. There is only going to be one option in the header section of the widget, and that is

View

, which will expand the widget and show the graph in an expanded modal. SigNoz/signoz

#2996 TypeError: Cannot destructure property 'data' Issue created by Rajat-Dabade Bug description Getting Error

TypeError: Cannot destructure property 'data'

while loading the services matrics Expected behavior No error How to reproduce 1. Navigate to services. 2. Click on any services. 3. See the error in the console. Version information • Signoz version: v0.21.0-11-g1e • Browser version: Chrome / firefox • Your OS and version: any • *Your CPU Architecture*(ARM/Intel): SigNoz/signoz

#2997 refactor: added check for dashboard length Pull request opened by Rajat-Dabade Close #2996 SigNoz/signoz GitHub Actions: sonar-analysis GitHub Actions: Codeball ✅ 7 other checks have passed 7/9 successful checks

#2998 refactor: remove the dependency of services from redux Pull request opened by Rajat-Dabade • Removed the redux dependency to get the list of services. SigNoz/signoz GitHub Actions: create_issue_on_merge GitHub Actions: Codeball GitHub Actions: sonar-analysis ✅ 7 other checks have passed 7/10 successful checks

#154 fix: trace column attributes name Pull request opened by makeavish SigNoz/signoz-otel-collector ✅ All checks have passed 3/3 successful checks

#2999 Misspelled trace attribute keys being return Issue created by makeavish spanId should be spanID, traceId should be traceID, parentSpanId should be parentSpanID SigNoz/signoz

#3000 fix: trace column attributes Pull request opened by makeavish fix(#2999) SigNoz/signoz GitHub Actions: Codeball ✅ 7 other checks have passed 7/8 successful checks

#2978 feat: ability to configure noisy top level operations to discard Pull request opened by srikanthccv Adds a config option

--skip-top-level-ops

to skip certain top-level operations for each service. The sample config looks like the following.

services:
  - name: redis
    operations:
      - GetDriver

We need service wise config because what might be incorrect top-level operation options could be a correct top-level operation in another service. These are discarded from the call

GetTopLevelOperations

so that it reflects everywhere. SigNoz/signoz GitHub Actions: Codeball ✅ 7 other checks have passed 7/8 successful checks

1 new commit pushed to

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

by palashgdev

<https://github.com/SigNoz/signoz/commit/64d4532a6b02c085da7ded67db26a86186629bc3|64d4532a>

- feat: sort logs in ascending order (#2895) SigNoz/signoz

#2787 Sort logs in ascending order Issue created by ankitnayan It helps in seeing the chronological order of logs when debugging 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/3464b2a59c8a31b709ffea1e3f09be16efd9b6f9|3464b2a5>

- feat: added time series tab in logs explorer (#2982) SigNoz/signoz

#2344 Time series view tab in the logs explorer Issue created by srikanthccv Note: this will not be any different from the other signals. The response will be in the same format, and the expected UI is also in the same format. This can be done using some shareable components built once and used everywhere. More details about the UI are as follows. Users can perform different aggregations on the trace data and see the result in the graph. For instance, • They may want to look at the

P99

of the span duration for the last 30 minutes. • They may want to

COUNT

the total number of spans in the last 30 minutes with particular criteria. The response for this will a plotted in the time series chart. There will be an option to plot each query result in a different widget panel or everything in the same widget. When they are plotted with a separate widget for each query, there will be two widgets in the UI for a row. When they inspect the charts and move the mouse from one timestamp to another, there will be another line in each graph highlighting the value at that timestamp. There is only going to be one option in the header section of the widget, and that is

View

, which will expand the widget and show the graph in an expanded modal. SigNoz/signoz

Deployment to staging by palashgdev SigNoz/signoz

#3001 Let the user set the base path of signoz Issue created by svsk417 Is your feature request related to a problem? I am currently investigating whether we can use SigNoz for our solution. We have an architecture as follows: The problem is, that I do not know how I can change the base path with which the fronend contacts the backend. I.e. I want to prepend

/signoz-api/

. Describe the solution you'd like A hint on where I find the documentation or a hint on how to achieve this would be cool. Thank you in advance! Describe alternatives you've considered Cloning the repository and change it in the code rather than provide it as a docker environment variable or similar. Thank you for your feature request – we love each and every one! SigNoz/signoz

#3002 bug: orderBy initial value is not initialised from the url Issue created by palashgdev Screen.Recording.2023-06-29.at.4.58.50.PM.mov SigNoz/signoz

#3003 Feat/add control panel Pull request opened by yeshev SigNoz/signoz GitHub Actions: Codeball ✅ 4 other checks have passed 4/5 successful checks

1 new commit pushed to

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

by palashgdev

<https://github.com/SigNoz/signoz/commit/0f998a48450cf6ab3f56ed3a5e207de636743554|0f998a48>

- feat: add custom orderBy (#2975) SigNoz/signoz

Deployment to staging by palashgdev SigNoz/signoz

#3004 fix: formula for table Pull request opened by yeshev SigNoz/signoz GitHub Actions: sonar-analysis GitHub Actions: Codeball ✅ 7 other checks have passed 7/9 successful checks