GitHub
02/22/2023, 2:57 PMScreenshot 2023-02-22 at 8 55 59 PM▾
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/signozGitHub
02/22/2023, 2:57 PMCOUNT
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/signozGitHub
02/22/2023, 3:35 PMScreenshot 2023-02-22 at 9 07 39 PM▾
Screenshot 2023-02-22 at 9 07 50 PM▾
Screenshot 2023-02-22 at 9 08 05 PM▾
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/signozGitHub
02/22/2023, 3:35 PMScreenshot 2023-02-22 at 9 18 33 PM▾
/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/signozGitHub
02/22/2023, 3:35 PMGitHub
02/22/2023, 5:28 PMGitHub
02/22/2023, 7:00 PMScreenshot 2023-02-22 at 8 27 48 PM▾
Screenshot 2023-02-22 at 8 27 54 PM▾
+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/signozGitHub
02/22/2023, 7:00 PMScreenshot 2023-02-23 at 12 33 54 AM▾
GitHub
02/22/2023, 7:00 PMScreenshot 2023-02-23 at 12 37 06 AM▾
Screenshot 2023-02-23 at 12 39 29 AM▾
Screenshot 2023-02-23 at 12 39 53 AM▾
GitHub
02/22/2023, 7:00 PMScreenshot 2023-02-22 at 8 55 59 PM▾
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/signozGitHub
02/22/2023, 7:00 PMSUM
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/signozGitHub
02/22/2023, 7:01 PMScreenshot 2023-02-22 at 9 07 39 PM▾
Screenshot 2023-02-22 at 9 07 50 PM▾
Screenshot 2023-02-22 at 9 08 05 PM▾
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/signozGitHub
02/22/2023, 7:01 PMScreenshot 2023-02-22 at 9 18 33 PM▾
/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/signozGitHub
02/23/2023, 2:11 AMGitHub
02/23/2023, 4:20 AMGitHub
02/23/2023, 4:21 AMImage▾
Image▾
GitHub
02/23/2023, 4:21 AMScreenshot 2023-02-22 at 9 07 39 PM▾
Screenshot 2023-02-22 at 9 07 50 PM▾
Screenshot 2023-02-22 at 9 08 05 PM▾
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/signozGitHub
02/23/2023, 4:21 AMImage▾
GitHub
02/23/2023, 4:23 AMImage▾
GitHub
02/23/2023, 4:23 AMImage▾
GitHub
02/23/2023, 4:23 AMRun Query
which will not save the state when user moves from one query type to another.
SigNoz/signozGitHub
02/23/2023, 4:23 AMImage▾
Image▾
GitHub
02/23/2023, 5:43 AMGitHub
02/23/2023, 5:45 AM<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/signozGitHub
02/23/2023, 5:45 AMGitHub
02/23/2023, 6:10 AMGitHub
02/23/2023, 6:16 AMScreenshot 2023-02-23 at 1 14 22 PM▾
Screenshot 2023-02-23 at 1 17 47 PM▾
GitHub
02/23/2023, 6:49 AM