external builders (again, if you intend to employ external chaincodes). These include Operations and metrics, which allow you to set up methods for monitoring the health and performance of your peer through addresses where the ordering node itself can be found by other components as well as Operations and metrics, which allow you to set up methods for monitoring the health and performance of your ordering node fileSystemPath peer.gossip.* peer.tls.* peer.bccsp.* chaincode.externalBuilders.* ledger.* operations.* metrics.* peer.id # The peer id provides a name for this peer instance and is used when # naming docker

external builders (again, if you intend to employ external chaincodes). These include Operations and metrics, which allow you to set up methods for monitoring the health and performance of your peer through gossip.* • peer.tls.* • peer.bccsp.* • chaincode.externalBuilders.* • ledger.* • operations.* • metrics.* peer.id # The peer id provides a name for this peer instance and is used when # naming docker certificate on the requests. See The Operations Service to learn more. If you plan to use Prometheus metrics to monitor your peer, you must configure the operations service here. In the unlikely case where

Fabric v1.4 takes a giant leap forward with logging improvements, health checks, and operational metrics. As such, Fabric v1.4 is the recommended release for production operations. • The Operations Service: orderer node liveness and health. – The /metrics endpoint allows operators to utilize Prometheus to pull operational metrics from peer and orderer nodes. Metrics can also be pushed to StatsD. – As of v1 following capabilities: • Log level management • Health checks • Prometheus target for operational metrics (when configured) • Version information 8.13.1 Configuring the Operations Service The operations

Fabric v1.4 takes a giant leap forward with logging improvements, health checks, and operational metrics. As such, Fabric v1.4 is the recommended release for production operations. • The Operations Service: orderer node liveness and health. – The /metrics endpoint allows operators to utilize Prometheus to pull operational metrics from peer and orderer nodes. Metrics can also be pushed to StatsD. – As of v1 following capabilities: • Log level management • Health checks • Prometheus target for operational metrics (when configured) • Version information 8.13.1 Configuring the Operations Service The operations

Fabric v1.4 takes a giant leap forward with logging improvements, health checks, and operational metrics. As such, Fabric v1.4 is the recommended release for production operations. • The Operations Service: orderer node liveness and health. – The /metrics endpoint allows operators to utilize Prometheus to pull operational metrics from peer and orderer nodes. Metrics can also be pushed to StatsD. – As of v1 following capabilities: • Log level management • Health checks • Prometheus target for operational metrics (when configured) • Version information 8.13.1 Configuring the Operations Service The operations

external builders (again, if you intend to employ external chaincodes). These include Operations and metrics, which allow you to set up methods for monitoring the health and performance of your peer through gossip.* • peer.tls.* • peer.bccsp.* • chaincode.externalBuilders.* • ledger.* • operations.* • metrics.* peer.id # The peer id provides a name for this peer instance and is used when # naming docker certificate on the requests. See The Operations Service to learn more. If you plan to use Prometheus metrics to monitor your peer, you must configure the operations service here. In the unlikely case where

Fabric v1.4 takes a giant leap forward with logging improvements, health checks, and operational metrics. As such, Fabric v1.4 is the recommended release for production operations. The Operations Service: and orderer node liveness and health. The /metrics endpoint allows operators to utilize Prometheus to pull operational metrics from peer and orderer nodes. Metrics can also be pushed to StatsD. As of v1.4 with Identity Mixer Identity Mixer MSP configuration generator (idemixgen) The Operations Service Metrics Reference Error handling Logging Control Securing Communication With Transport Layer Security (TLS)

Fabric v1.4 takes a giant leap forward with logging improvements, health checks, and operational metrics. As such, Fabric v1.4 is the recommended release for production operations. The Operations Service: and orderer node liveness and health. The /metrics endpoint allows operators to utilize Prometheus to pull operational metrics from peer and orderer nodes. Metrics can also be pushed to StatsD. As of v1.4 with Identity Mixer Identity Mixer MSP configuration generator (idemixgen) The Operations Service Metrics Reference Error handling Logging Control Securing Communication With Transport Layer Security (TLS)

Fabric v1.4 takes a giant leap forward with logging improvements, health checks, and operational metrics. As such, Fabric v1.4 is the recommended release for production operations. The Operations Service: and orderer node liveness and health. The /metrics endpoint allows operators to utilize Prometheus to pull operational metrics from peer and orderer nodes. Metrics can also be pushed to StatsD. As of v1.4 with Identity Mixer Identity Mixer MSP configuration generator (idemixgen) The Operations Service Metrics Reference Error handling Logging Control Securing Communication With Transport Layer Security (TLS)

Fabric v1.4 takes a giant leap forward with logging improvements, health checks, and operational metrics. As such, Fabric v1.4 is the recommended release for production operations. • The Operations Service: orderer node liveness and health. – The /metrics endpoint allows operators to utilize Prometheus to pull operational metrics from peer and orderer nodes. Metrics can also be pushed to StatsD. 2.4 Improved following capabilities: • Log level management • Health checks • Prometheus target for operational metrics (when configured) 8.11.1 Configuring the Operations Service The operations service requires two