#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

#2336 Table view tab for in traces explorer Issue created by srikanthccv The table is a tabular representation of the aggregation data from the traces. Both the time series graph and table view will have the same response data under the hood, but the user will decide the visual representation they desire. • User may want to see the

COUNT

of spans in a table format in the last 30 minutes with error status by service. Example:

---------------------------
| ts  | service_name | count |
| t1  |  frontend | 20|
| t1  |  route  | 15 |
| t2 |  frontend | 25|
| t2 | route | 12 |
---------------------------

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

#2338 Ability to create an alert from the traces explorer page. Issue created by srikanthccv component: button with dropdown menu The user should be able to create an alert from the traces explorer page. The implementation detail will be as follows. The client will save the query using the explorer save queries API

/api/v1/explorer/queries

. The API will respond with the queryId which the client uses to redirect the user to the alert page. The redirected page will contain the queryId in the URL params. This queryId will be used to fetch the composite query data and pre-populate the query builder using the selection made by users in the explorer page. SigNoz/signoz

#2339 Ability to save the explorer query for the later use in trace explorer Issue created by srikanthccv This is not in the scope of the v1 query builder, but keep it in mind when building the component arch to easily extend support if the queries need to be saved for later use. SigNoz/signoz

Deployment to github-pages by prashant-shahi SigNoz/charts

#2340 [EPIC]FE(Logs)Query Builder Issue created by srikanthccv ☐ #2322 ☐ #2306 ☐ #2307 ☐ #2312 ☐ #2308 ☐ #2309 ☐ #2310 ☐ #2313 ☐ #2341 ☐ #2342 ☐ #2343 ☐ #2344 ☐ #2345 ☐ #2346 ☐ #2347 SigNoz/signoz

#2341 Multiple query management in the logs explorer Issue created by srikanthccv Note: This is not different from traces/metrics regarding the expectation in behaviour and functionality. So this can be built as a parent component to avoid code repetition. Following is the more detailed description. 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

#2342 Timeline view for the logs explorer Issue created by srikanthccv This is a graph specific to the logs explorer. The goal of this timeline is the same as the current logs explorer timeline view graph. It shows the count of logs matching the selection criteria over the period of time. The result of this will come from the first query, where there are multiple queries. cc @nityanandagohain SigNoz/signoz

#2343 List view tab in the logs explorer Issue created by srikanthccv The list view in the logs query builder differs from the list in the traces builder. The list view in the logs builder must support the various formats. The backend will include the top-level columns (including the selected fields). In any view, users should be able to additionally add the column they want to see in the UI. This should be searchable and uses the same API as the attribute keys API with data source as logs and the selected criteria. This selection will be sent to the backend (see the query_range v3 request payload), and the response will include the additional columns the user picks. They can also deselect the previously selected columns. The pagination functionality will not contain the total number of pages. The client will send the offset and the pageSize as long the response from the query service includes the data. When there is no data for the next from the backend, the button will be disabled. There are three formats • Row • Default • Column The default format The row format The column format: TODO(@Srikanth Chekuri ): Add column format image 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

#2345 Table view tab in the logs explorer Issue created by srikanthccv Note: this will be a shareable component that can be built once and used everywhere. The table is a tabular representation of the aggregation data from the logs. The time series graph and table view will have the same response data under the hood, but the user will decide on their desired visual representation. • User may want to see the

SUM

of bytes of logs in a table format in the last 30 minutes by service. Example:

---------------------------
| ts  | service_name | bytes |
| t1  |  frontend | 2000000|
| t1  |  route  | 1500000 |
| t2 |  frontend | 2500000|
| t2 | route | 1000002 |
---------------------------

SigNoz/signoz

#2346 Ability to save the logs explorer page query result to dashboard Issue created by srikanthccv Nore: this functionality is shared b/w the multiple explore pages. This will be a shareable component that can be built once and used everywhere. 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

#2347 Ability to create an alert from the logs explorer page Issue created by srikanthccv Note: The actions component is a shareable component that will be placed differently in the explorer pages, but the functionality is the same. The effort shouldn't be repeated here. component: button with dropdown menu The user should be able to create an alert from the traces explorer page. The implementation detail will be as follows. The client will save the query using the explorer save queries API

/api/v1/explorer/queries

. The API will respond with the queryId which the client uses to redirect the user to the alert page. The redirected page will contain the queryId in the URL params. This queryId will be used to fetch the composite query data and pre-populate the query builder using the selection made by users in the explorer page. SigNoz/signoz

#2348 Create release.md Issue created by srikanthccv Write down the step-by-step process, including instructions such as git commands and scripts to run etc... Ideally, anyone in the team should be able to do the release just by following the instructions. Some inspiration https://github.com/open-telemetry/opentelemetry-java/blob/main/RELEASING.md SigNoz/signoz

#2349 [EPIC]FE(Metrics)Query Builder Issue created by srikanthccv ☐ #2319 ☐ #2314 ☐ #2286 ☐ #2306 ☐ #2307 ☐ #2312 ☐ #2309 ☐ #2313 ☐ #2350 ☐ Time series view tab in the metrics explorer ☐ #2351 ☐ #2352 • [ ] SigNoz/signoz

#2350 Multiple query management in the metrics explorer Issue created by srikanthccv Unlike the traces and logs explorer, the metrics explore will only support the aggregation and produce the time series data. There is also no restriction on the datasource i.e in the traces/logs explorer pages the datasource is fixed, however, this metrics explorer page on should be able to query on any datasource. The UX experience for the difference source will vary for example the where clause in metrics will show up as Search bar for the logs datasource. Make sure the change the UI appearance based on the selected data source. The result will be a timeseries data. User has the option to plot result of each query in a separate widget. When they plot the result in independent widget there should be two widgets in a row. SigNoz/signoz

#2351 Ability to create a dashboard or a panel in the existing dashboard in metrics explorer page Issue created by srikanthccv This functionality is same in explorer page. The idea is to save the current explorer result to dashboard or create a new dashboard out of it. This should be a shareable component. 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

#2352 Ability to create an alert from the metrics explorer page Issue created by srikanthccv Common functionality. The component can just be shared here. The user should be able to create an alert from the metrics explorer page. The implementation detail will be as follows. The client will save the query using the explorer save queries API /api/v1/explorer/queries. The API will respond with the queryId which the client uses to redirect the user to the alert page. The redirected page will contain the queryId in the URL params. This queryId will be used to fetch the composite query data and pre-populate the query builder using the selection made by users in the explorer page SigNoz/signoz

#2353 [EPIC]FE(Dashboards)Query Builder Issue created by srikanthccv ☐ #2314 ☐ #2286 ☐ #2306 ☐ #2307 ☐ #2312 ☐ #2308 ☐ #2309 ☐ #2310 ☐ #2313 ☐ #2354 ☐ #2355 ☐ #2356 ☐ #2357 ☐ #2410 SigNoz/signoz

#2354 Replace the existing query builder with new query builder Issue created by srikanthccv The existing query builder only supports the metrics data source. With the new integrated query builder user should be able work with any data source i.e add support for logs and traces. When the data source is selected the UI for the individual query will change. And the other collapsible filters section is also different for different data sources. SigNoz/signoz

#2355 Create alerts from the dashboard panel Issue created by srikanthccv This button will appear in the right bottom corner of the dashboard edit mode just below the panel settings section. A user should be able to create an alert from the dashboard panel. Since the dashboard panel already has the queryId the implementation just needs to redirect the user from the panel to alerts page using the queryId in the URL params. SigNoz/signoz

#2356 Remove the `Stage` part of the dashboards query builder Issue created by srikanthccv This was some implementation detailed that have added the complexity to the query builder codebase. Change this to just

Run Query

which will not save the state when user moves from one query type to another. SigNoz/signoz

#2357 Add view only component for table and list panel types Issue created by srikanthccv These two are the new panel types in the dashboards. The difference b/w the list view and table view that list view used for the raw data and the table view is used for the aggregation data to show in tabular format. SigNoz/signoz

#2359 fix: scrollbar issue on widget Pull request opened by techchintan Close: #2321 SigNoz/signoz GitHub Actions: Codeball GitHub Actions: lint-commits GitHub Actions: playwright GitHub Actions: Ensure Pull Request has a linked issue. ✅ 8 other checks have passed 8/12 successful checks

1 new commit pushed to

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

by srikanthccv

<https://github.com/SigNoz/signoz/commit/a3731e4c4e50a8a17520c34124b4dd02ea17f47c|a3731e4c>

- fix: error rate as a percentage of range 0-100% (#2311) SigNoz/signoz

Deployment to staging by srikanthccv SigNoz/signoz

#104 fix: on cluster command added to migration Pull request opened by nityanandagohain On cluster command was missed in the migration file, this fix adds the on cluster command #94 SigNoz/signoz-otel-collector ✅ All checks have passed 3/3 successful checks

#2360 Dropdown antd depreciation warning Issue created by palashgdev There are a few places in which dropdown components need to be updated ☑︎ frontend/src/components/TimePreferenceDropDown/index.tsx ☑︎ frontend/src/container/ConfigDropdown/index.tsx ☑︎ frontend/src/container/Header/index.tsx:100 ☑︎ frontend/src/container/ListOfDashboard/index.tsx:233 SigNoz/signoz

#2361 Set common default time period across different pages on SigNoz Issue created by makeavish Currently, services and service-map page has a default time period of last 5mins and other pages like exceptions, traces and logs have a default time period of last 30mins. This causes confusion for new users when they try to test instrumented services. They might see traces/exceptions in last 30mins but won't see any services in last 5mins as there was no traffic in last 5mins. So setting a standard default timestamp across different pages can avoid this confusion. SigNoz/signoz