You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: src/guide/advanced/metrics.md
+65-15Lines changed: 65 additions & 15 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -21,6 +21,8 @@ The progress on the configuration reference can be tracked in the following GitH
21
21
22
22
After the above is configured, you can use the IP address set in the `"TORII_TELEMETRY_URL"` variable to access the metrics data from within a running Iroha instance.
23
23
24
+
<!-- FIXME: irrelevant information about configuration above -->
Copy file name to clipboardExpand all lines: src/reference/torii-endpoints.md
+84-99Lines changed: 84 additions & 99 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -43,7 +43,6 @@ To establish two-way communication with the `TORII` endpoints, the following add
43
43
This address is the same as the `TORII_API_URL` address in the `configs/client_cli/config.json` client configuration file.
44
44
- `TELEMETRY_URL` — connects to the [Prometheus](https://prometheus.io/) endpoint address that is used as a [metrics](../guide/advanced/metrics.md) tool to monitor the network performance.
45
45
46
-
47
46
-->
48
47
49
48
[[toc]]
@@ -252,6 +251,33 @@ request, after which the server sends an
| 200 | OK |[`Status`](/reference/data-model-schema#status)| Returns the Iroha network status report encoded as specified in the header of the request. |
531
512
532
513
::: details Examples
533
514
@@ -539,7 +520,9 @@ The following examples represent the same data:
539
520
{
540
521
"peers": 4,
541
522
"blocks": 5,
542
-
"txs_accepted": 31,
523
+
"blocks_non_empty": 3,
524
+
"commit_time_ms": 130,
525
+
"txs_approved": 31,
543
526
"txs_rejected": 3,
544
527
"uptime": {
545
528
"secs": 5,
@@ -551,7 +534,7 @@ The following examples represent the same data:
551
534
```
552
535
553
536
```[SCALE]
554
-
10 14 7C 0C 14 40 7C D9 37 08 48
537
+
10 14 0C 09 02 7C 0C 14 40 7C D9 37 08 48
555
538
```
556
539
557
540
:::
@@ -590,7 +573,9 @@ values are only returned in the JSON format.
590
573
{
591
574
"peers": 4,
592
575
"blocks": 5,
593
-
"txs_accepted": 31,
576
+
"blocks_non_empty": 3,
577
+
"commit_time_ms": 130,
578
+
"txs_approved": 31,
594
579
"txs_rejected": 3,
595
580
"uptime": {
596
581
"secs": 5,
@@ -634,8 +619,8 @@ This endpoint expects the following data:
0 commit comments