Skip to content

Commit 27da803

Browse files
committed
Fix links
Signed-off-by: AkramBitar <akram@il.ibm.com>
1 parent a752363 commit 27da803

2 files changed

Lines changed: 4 additions & 3 deletions

File tree

docs/development/metrics.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -289,7 +289,8 @@ panurus_services_network_fabricx_finality_queue_finality_queue_pending_events
289289
## Not covered here
290290

291291
- **FSC platform metrics** — view executions, sessions, gRPC, database and process metrics come from
292-
Fabric Smart Client and are documented [there](https://github.com/hyperledger-labs/fabric-smart-client/blob/main/docs/platform/view/monitoring.md).
292+
Fabric Smart Client and are documented in its [Monitoring](https://github.com/hyperledger-labs/fabric-smart-client/blob/main/docs/platform/view/services/monitoring.md)
293+
page and [Metrics Catalog](https://github.com/hyperledger-labs/fabric-smart-client/blob/main/docs/platform/view/services/monitoring_metrics.md).
293294
View-level timing in particular is already instrumented by FSC, so the SDK does not duplicate it.
294295
- **Load-generator metrics**`integration/nwo/txgen/service/metrics/` and `integration/nwo/runner/`
295296
instrument the test harness, not the SDK, and are not exported by a Panurus node.

docs/development/monitoring.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
# Monitoring
22

3-
We adopt the monitoring infrastructure provided by the [`Fabric Smart Client`](https://github.com/hyperledger-labs/fabric-smart-client/blob/main/docs/platform/view/monitoring.md).
3+
We adopt the monitoring infrastructure provided by the [`Fabric Smart Client`](https://github.com/hyperledger-labs/fabric-smart-client/blob/main/docs/platform/view/services/monitoring.md).
44

55
We use the following two methods to monitor the performance of the application:
66
* **Metrics** provide an overview of the overall system performance using aggregated results, e.g. total requests, requests per second, current state of a variable, average duration, percentile of duration
@@ -12,6 +12,6 @@ We use the following two methods to monitor the performance of the application:
1212
serves it, plus how those names are derived, example queries, and the current coverage gaps.
1313
* [Driver Metrics](../drivers/metrics.md) — how the driver service wrappers are built and which
1414
methods they instrument.
15-
* [Fabric Smart Client monitoring](https://github.com/hyperledger-labs/fabric-smart-client/blob/main/docs/platform/view/monitoring.md)
15+
* [Fabric Smart Client monitoring](https://github.com/hyperledger-labs/fabric-smart-client/blob/main/docs/platform/view/services/monitoring.md)
1616
— the platform metrics and traces Panurus inherits (views, sessions, gRPC, process), and how to
1717
enable the Prometheus endpoint and the tracing exporter.

0 commit comments

Comments
 (0)