github.com/IBM-Blockchain/fabric-operator@v1.0.4/testdata/init/peer/core.yaml (about) 1 # 2 # Copyright contributors to the Hyperledger Fabric Operator project 3 # 4 # SPDX-License-Identifier: Apache-2.0 5 # 6 # Licensed under the Apache License, Version 2.0 (the "License"); 7 # you may not use this file except in compliance with the License. 8 # You may obtain a copy of the License at: 9 # 10 # http://www.apache.org/licenses/LICENSE-2.0 11 # 12 # Unless required by applicable law or agreed to in writing, software 13 # distributed under the License is distributed on an "AS IS" BASIS, 14 # WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. 15 # See the License for the specific language governing permissions and 16 # limitations under the License. 17 # 18 19 20 ############################################################################### 21 # 22 # Peer section 23 # 24 ############################################################################### 25 peer: 26 27 # The peer id provides a name for this peer instance and is used when 28 # naming docker resources. 29 id: jdoe 30 31 # The networkId allows for logical separation of networks and is used when 32 # naming docker resources. 33 networkId: dev 34 35 # The Address at local network interface this Peer will listen on. 36 # By default, it will listen on all network interfaces 37 listenAddress: 0.0.0.0:7051 38 39 # The endpoint this peer uses to listen for inbound chaincode connections. 40 # If this is commented-out, the listen address is selected to be 41 # the peer's address (see below) with port 7052 42 chaincodeListenAddress: 0.0.0.0:7052 43 44 # The endpoint the chaincode for this peer uses to connect to the peer. 45 # If this is not specified, the chaincodeListenAddress address is selected. 46 # And if chaincodeListenAddress is not specified, address is selected from 47 # peer listenAddress. 48 chaincodeAddress: 0.0.0.0:7053 49 50 # When used as peer config, this represents the endpoint to other peers 51 # in the same organization. For peers in other organization, see 52 # gossip.externalEndpoint for more info. 53 # When used as CLI config, this means the peer's endpoint to interact with 54 address: 0.0.0.0:7054 55 56 # Whether the Peer should programmatically determine its address 57 # This case is useful for docker containers. 58 addressAutoDetect: true 59 60 # Keepalive settings for peer server and clients 61 keepalive: 62 # Interval is the duration after which if the server does not see 63 # any activity from the client it pings the client to see if it's alive 64 interval: 7200s 65 # Timeout is the duration the server waits for a response 66 # from the client after sending a ping before closing the connection 67 timeout: 20s 68 # MinInterval is the minimum permitted time between client pings. 69 # If clients send pings more frequently, the peer server will 70 # disconnect them 71 minInterval: 60s 72 # Client keepalive settings for communicating with other peer nodes 73 client: 74 # Interval is the time between pings to peer nodes. This must 75 # greater than or equal to the minInterval specified by peer 76 # nodes 77 interval: 60s 78 # Timeout is the duration the client waits for a response from 79 # peer nodes before closing the connection 80 timeout: 20s 81 # DeliveryClient keepalive settings for communication with ordering 82 # nodes. 83 deliveryClient: 84 # Interval is the time between pings to ordering nodes. This must 85 # greater than or equal to the minInterval specified by ordering 86 # nodes. 87 interval: 60s 88 # Timeout is the duration the client waits for a response from 89 # ordering nodes before closing the connection 90 timeout: 20s 91 92 # Gossip related configuration 93 gossip: 94 # Bootstrap set to initialize gossip with. 95 # This is a list of other peers that this peer reaches out to at startup. 96 # Important: The endpoints here have to be endpoints of peers in the same 97 # organization, because the peer would refuse connecting to these endpoints 98 # unless they are in the same organization as the peer. 99 bootstrap: 100 - 127.0.0.1:7051 101 - 127.0.0.1:7052 102 103 # NOTE: orgLeader and useLeaderElection parameters are mutual exclusive. 104 # Setting both to true would result in the termination of the peer 105 # since this is undefined state. If the peers are configured with 106 # useLeaderElection=false, make sure there is at least 1 peer in the 107 # organization that its orgLeader is set to true. 108 109 # Defines whenever peer will initialize dynamic algorithm for 110 # "leader" selection, where leader is the peer to establish 111 # connection with ordering service and use delivery protocol 112 # to pull ledger blocks from ordering service. It is recommended to 113 # use leader election for large networks of peers. 114 useLeaderElection: true 115 # Statically defines peer to be an organization "leader", 116 # where this means that current peer will maintain connection 117 # with ordering service and disseminate block across peers in 118 # its own organization 119 orgLeader: true 120 121 # Interval for membershipTracker polling 122 membershipTrackerInterval: 5s 123 124 # Overrides the endpoint that the peer publishes to peers 125 # in its organization. For peers in foreign organizations 126 # see 'externalEndpoint' 127 endpoint: "endpoint1" 128 # These need to be overridden with the FQDN of the peer 129 address: "address1" 130 externaladdress: "externaladdress1" 131 # Maximum count of blocks stored in memory 132 maxBlockCountToStore: 10 133 # Max time between consecutive message pushes(unit: millisecond) 134 maxPropagationBurstLatency: 10ms 135 # Max number of messages stored until a push is triggered to remote peers 136 maxPropagationBurstSize: 10 137 # Number of times a message is pushed to remote peers 138 propagateIterations: 1 139 # Number of peers selected to push messages to 140 propagatePeerNum: 3 141 # Determines frequency of pull phases(unit: second) 142 # Must be greater than digestWaitTime + responseWaitTime 143 pullInterval: 4s 144 # Number of peers to pull from 145 pullPeerNum: 3 146 # Determines frequency of pulling state info messages from peers(unit: second) 147 requestStateInfoInterval: 4s 148 # Determines frequency of pushing state info messages to peers(unit: second) 149 publishStateInfoInterval: 4s 150 # Maximum time a stateInfo message is kept until expired 151 stateInfoRetentionInterval: 2s 152 # Time from startup certificates are included in Alive messages(unit: second) 153 publishCertPeriod: 10s 154 # Should we skip verifying block messages or not (currently not in use) 155 skipBlockVerification: true 156 # Dial timeout(unit: second) 157 dialTimeout: 3s 158 # Connection timeout(unit: second) 159 connTimeout: 2s 160 # Buffer size of received messages 161 recvBuffSize: 20 162 # Buffer size of sending messages 163 sendBuffSize: 200 164 # Time to wait before pull engine processes incoming digests (unit: second) 165 # Should be slightly smaller than requestWaitTime 166 digestWaitTime: 1s 167 # Time to wait before pull engine removes incoming nonce (unit: milliseconds) 168 # Should be slightly bigger than digestWaitTime 169 requestWaitTime: 1500ms 170 # Time to wait before pull engine ends pull (unit: second) 171 responseWaitTime: 2s 172 # Alive check interval(unit: second) 173 aliveTimeInterval: 5s 174 # Alive expiration timeout(unit: second) 175 aliveExpirationTimeout: 25s 176 # Reconnect interval(unit: second) 177 reconnectInterval: 25s 178 # This is an endpoint that is published to peers outside of the organization. 179 # If this isn't set, the peer will not be known to other organizations. 180 externalEndpoint: "externalEndpoint1" 181 # Leader election service configuration 182 election: 183 # Longest time peer waits for stable membership during leader election startup (unit: second) 184 startupGracePeriod: 15s 185 # Interval gossip membership samples to check its stability (unit: second) 186 membershipSampleInterval: 1s 187 # Time passes since last declaration message before peer decides to perform leader election (unit: second) 188 leaderAliveThreshold: 10s 189 # Time between peer sends propose message and declares itself as a leader (sends declaration message) (unit: second) 190 leaderElectionDuration: 5s 191 192 pvtData: 193 # pullRetryThreshold determines the maximum duration of time private data corresponding for a given block 194 # would be attempted to be pulled from peers until the block would be committed without the private data 195 pullRetryThreshold: 60s 196 # As private data enters the transient store, it is associated with the peer's ledger's height at that time. 197 # transientstoreMaxBlockRetention defines the maximum difference between the current ledger's height upon commit, 198 # and the private data residing inside the transient store that is guaranteed not to be purged. 199 # Private data is purged from the transient store when blocks with sequences that are multiples 200 # of transientstoreMaxBlockRetention are committed. 201 transientstoreMaxBlockRetention: 1000 202 # pushAckTimeout is the maximum time to wait for an acknowledgement from each peer 203 # at private data push at endorsement time. 204 pushAckTimeout: 3s 205 # Block to live pulling margin, used as a buffer 206 # to prevent peer from trying to pull private data 207 # from peers that is soon to be purged in next N blocks. 208 # This helps a newly joined peer catch up to current 209 # blockchain height quicker. 210 btlPullMargin: 10 211 # the process of reconciliation is done in an endless loop, while in each iteration reconciler tries to 212 # pull from the other peers the most recent missing blocks with a maximum batch size limitation. 213 # reconcileBatchSize determines the maximum batch size of missing private data that will be reconciled in a 214 # single iteration. 215 reconcileBatchSize: 10 216 # reconcileSleepInterval determines the time reconciler sleeps from end of an iteration until the beginning 217 # of the next reconciliation iteration. 218 reconcileSleepInterval: 1m 219 # reconciliationEnabled is a flag that indicates whether private data reconciliation is enable or not. 220 reconciliationEnabled: true 221 # skipPullingInvalidTransactionsDuringCommit is a flag that indicates whether pulling of invalid 222 # transaction's private data from other peers need to be skipped during the commit time and pulled 223 # only through reconciler. 224 skipPullingInvalidTransactionsDuringCommit: false 225 226 # Gossip state transfer related configuration 227 state: 228 # indicates whenever state transfer is enabled or not 229 # default value is true, i.e. state transfer is active 230 # and takes care to sync up missing blocks allowing 231 # lagging peer to catch up to speed with rest network 232 enabled: true 233 # checkInterval interval to check whether peer is lagging behind enough to 234 # request blocks via state transfer from another peer. 235 checkInterval: 10s 236 # responseTimeout amount of time to wait for state transfer response from 237 # other peers 238 responseTimeout: 3s 239 # batchSize the number of blocks to request via state transfer from another peer 240 batchSize: 10 241 # blockBufferSize reflects the size of the re-ordering buffer 242 # which captures blocks and takes care to deliver them in order 243 # down to the ledger layer. The actually buffer size is bounded between 244 # 0 and 2*blockBufferSize, each channel maintains its own buffer 245 blockBufferSize: 20 246 # maxRetries maximum number of re-tries to ask 247 # for single state transfer request 248 maxRetries: 3 249 250 # TLS Settings 251 tls: 252 # Require server-side TLS 253 enabled: false 254 # Require client certificates / mutual TLS. 255 # Note that clients that are not configured to use a certificate will 256 # fail to connect to the peer. 257 clientAuthRequired: false 258 # X.509 certificate used for TLS server 259 cert: 260 file: tls/server.crt 261 # Private key used for TLS server (and client if clientAuthEnabled 262 # is set to true 263 key: 264 file: tls/server.key 265 # Trusted root certificate chain for tls.cert 266 rootcert: 267 file: tls/ca.crt 268 # Set of root certificate authorities used to verify client certificates 269 clientRootCAs: 270 files: 271 - tls/ca.crt 272 # Private key used for TLS when making client connections. If 273 # not set, peer.tls.key.file will be used instead 274 clientKey: 275 file: 276 # X.509 certificate used for TLS when making client connections. 277 # If not set, peer.tls.cert.file will be used instead 278 clientCert: 279 file: 280 281 # Authentication contains configuration parameters related to authenticating 282 # client messages 283 authentication: 284 # the acceptable difference between the current server time and the 285 # client's time as specified in a client request message 286 timewindow: 15m 287 288 # Path on the file system where peer will store data (eg ledger). This 289 # location must be access control protected to prevent unintended 290 # modification that might corrupt the peer operations. 291 fileSystemPath: /var/hyperledger/production 292 293 # BCCSP (Blockchain crypto provider): Select which crypto implementation or 294 # library to use 295 BCCSP: 296 Default: SW 297 # Settings for the SW crypto provider (i.e. when DEFAULT: SW) 298 SW: 299 # TODO: The default Hash and Security level needs refactoring to be 300 # fully configurable. Changing these defaults requires coordination 301 # SHA2 is hardcoded in several places, not only BCCSP 302 Hash: SHA2 303 Security: 256 304 # Location of Key Store 305 FileKeyStore: 306 # If "", defaults to 'mspConfigPath'/keystore 307 KeyStore: "keystore1" 308 # Settings for the PKCS#11 crypto provider (i.e. when DEFAULT: PKCS11) 309 PKCS11: 310 # Location of the PKCS11 module library 311 Library: "library1" 312 # Token Label 313 Label: "label1" 314 # User PIN 315 Pin: "1234" 316 Hash: SHA2 317 Security: 256 318 FileKeyStore: 319 KeyStore: "keystore2" 320 321 # Path on the file system where peer will find MSP local configurations 322 mspConfigPath: msp 323 324 # Identifier of the local MSP 325 # ----!!!!IMPORTANT!!!-!!!IMPORTANT!!!-!!!IMPORTANT!!!!---- 326 # Deployers need to change the value of the localMspId string. 327 # In particular, the name of the local MSP ID of a peer needs 328 # to match the name of one of the MSPs in each of the channel 329 # that this peer is a member of. Otherwise this peer's messages 330 # will not be identified as valid by other nodes. 331 localMspId: SampleOrg 332 333 # CLI common client config options 334 client: 335 # connection timeout 336 connTimeout: 3s 337 338 # Delivery service related config 339 deliveryclient: 340 # It sets the total time the delivery service may spend in reconnection 341 # attempts until its retry logic gives up and returns an error 342 reconnectTotalTimeThreshold: 3600s 343 344 # It sets the delivery service <-> ordering service node connection timeout 345 connTimeout: 3s 346 347 # It sets the delivery service maximal delay between consecutive retries 348 reConnectBackoffThreshold: 3600s 349 350 # Type for the local MSP - by default it's of type bccsp 351 localMspType: bccsp 352 353 # Used with Go profiling tools only in none production environment. In 354 # production, it should be disabled (eg enabled: false) 355 profile: 356 enabled: false 357 listenAddress: 0.0.0.0:6060 358 359 # Handlers defines custom handlers that can filter and mutate 360 # objects passing within the peer, such as: 361 # Auth filter - reject or forward proposals from clients 362 # Decorators - append or mutate the chaincode input passed to the chaincode 363 # Endorsers - Custom signing over proposal response payload and its mutation 364 # Valid handler definition contains: 365 # - A name which is a factory method name defined in 366 # core/handlers/library/library.go for statically compiled handlers 367 # - library path to shared object binary for pluggable filters 368 # Auth filters and decorators are chained and executed in the order that 369 # they are defined. For example: 370 # authFilters: 371 # - 372 # name: FilterOne 373 # library: /opt/lib/filter.so 374 # - 375 # name: FilterTwo 376 # decorators: 377 # - 378 # name: DecoratorOne 379 # - 380 # name: DecoratorTwo 381 # library: /opt/lib/decorator.so 382 # Endorsers are configured as a map that its keys are the endorsement system chaincodes that are being overridden. 383 # Below is an example that overrides the default ESCC and uses an endorsement plugin that has the same functionality 384 # as the default ESCC. 385 # If the 'library' property is missing, the name is used as the constructor method in the builtin library similar 386 # to auth filters and decorators. 387 # endorsers: 388 # escc: 389 # name: DefaultESCC 390 # library: /etc/hyperledger/fabric/plugin/escc.so 391 handlers: 392 authFilters: 393 - 394 name: DefaultAuth 395 - 396 name: ExpirationCheck # This filter checks identity x509 certificate expiration 397 decorators: 398 - 399 name: DefaultDecorator 400 endorsers: 401 escc: 402 name: DefaultEndorsement 403 library: 404 validators: 405 vscc: 406 name: DefaultValidation 407 library: 408 409 # library: /etc/hyperledger/fabric/plugin/escc.so 410 # Number of goroutines that will execute transaction validation in parallel. 411 # By default, the peer chooses the number of CPUs on the machine. Set this 412 # variable to override that choice. 413 # NOTE: overriding this value might negatively influence the performance of 414 # the peer so please change this value only if you know what you're doing 415 validatorPoolSize: 5 416 417 # The discovery service is used by clients to query information about peers, 418 # such as - which peers have joined a certain channel, what is the latest 419 # channel config, and most importantly - given a chaincode and a channel, 420 # what possible sets of peers satisfy the endorsement policy. 421 discovery: 422 enabled: true 423 # Whether the authentication cache is enabled or not. 424 authCacheEnabled: true 425 # The maximum size of the cache, after which a purge takes place 426 authCacheMaxSize: 1000 427 # The proportion (0 to 1) of entries that remain in the cache after the cache is purged due to overpopulation 428 authCachePurgeRetentionRatio: 0.75 429 # Whether to allow non-admins to perform non channel scoped queries. 430 # When this is false, it means that only peer admins can perform non channel scoped queries. 431 orgMembersAllowedAccess: true 432 433 # Limits is used to configure some internal resource limits. 434 limits: 435 # Concurrency limits the number of concurrently running system chaincode requests. 436 # This option is only supported for qscc at this time. 437 concurrency: 438 qscc: 5000 439 440 ############################################################################### 441 # 442 # VM section 443 # 444 ############################################################################### 445 vm: 446 447 # Endpoint of the vm management system. For docker can be one of the following in general 448 # unix:///var/run/docker.sock 449 # http://localhost:2375 450 # https://localhost:2376 451 endpoint: unix:///var/run/docker.sock 452 453 # settings for docker vms 454 docker: 455 tls: 456 enabled: false 457 ca: 458 file: docker/ca.crt 459 cert: 460 file: docker/tls.crt 461 key: 462 file: docker/tls.key 463 464 # Enables/disables the standard out/err from chaincode containers for 465 # debugging purposes 466 attachStdout: false 467 468 # Parameters on creating docker container. 469 # Container may be efficiently created using ipam & dns-server for cluster 470 # NetworkMode - sets the networking mode for the container. Supported 471 # standard values are: `host`(default),`bridge`,`ipvlan`,`none`. 472 # Dns - a list of DNS servers for the container to use. 473 # Note: `Privileged` `Binds` `Links` and `PortBindings` properties of 474 # Docker Host Config are not supported and will not be used if set. 475 # LogConfig - sets the logging driver (Type) and related options 476 # (Config) for Docker. For more info, 477 # https://docs.docker.com/engine/admin/logging/overview/ 478 # Note: Set LogConfig using Environment Variables is not supported. 479 hostConfig: 480 NetworkMode: host 481 Dns: 482 # - 192.168.0.1 483 # NEVER UNCOMMENT THIS 484 # LogConfig: 485 # Type: json-file 486 # Config: 487 # max-size: "50m" 488 # max-file: "5" 489 Memory: 2147483648 490 491 ############################################################################### 492 # 493 # Chaincode section 494 # 495 ############################################################################### 496 chaincode: 497 498 # The id is used by the Chaincode stub to register the executing Chaincode 499 # ID with the Peer and is generally supplied through ENV variables 500 # the `path` form of ID is provided when installing the chaincode. 501 # The `name` is used for all other requests and can be any string. 502 id: 503 path: 504 name: 505 506 # Generic builder environment, suitable for most chaincode types 507 builder: $(DOCKER_NS)/fabric-ccenv:$(PROJECT_VERSION) 508 509 # Enables/disables force pulling of the base docker images (listed below) 510 # during user chaincode instantiation. 511 # Useful when using moving image tags (such as :latest) 512 pull: false 513 514 golang: 515 # golang will never need more than baseos 516 runtime: $(DOCKER_NS)/fabric-baseos:$(PROJECT_VERSION) 517 518 # whether or not golang chaincode should be linked dynamically 519 dynamicLink: false 520 521 java: 522 # This is an image based on java:openjdk-8 with addition compiler 523 # tools added for java shim layer packaging. 524 # This image is packed with shim layer libraries that are necessary 525 # for Java chaincode runtime. 526 runtime: $(DOCKER_NS)/fabric-javaenv:latest 527 528 node: 529 # This is an image based on node:$(NODE_VER)-alpine 530 runtime: $(DOCKER_NS)/fabric-nodeenv:latest 531 532 # List of directories to treat as external builders and launchers for 533 # chaincode. The external builder detection processing will iterate over the 534 # builders in the order specified below. 535 externalBuilders: [] 536 537 # Timeout duration for starting up a container and waiting for Register 538 # to come through. 1sec should be plenty for chaincode unit tests 539 startuptimeout: 300s 540 541 # Timeout duration for Invoke and Init calls to prevent runaway. 542 # This timeout is used by all chaincodes in all the channels, including 543 # system chaincodes. 544 # Note that during Invoke, if the image is not available (e.g. being 545 # cleaned up when in development environment), the peer will automatically 546 # build the image, which might take more time. In production environment, 547 # the chaincode image is unlikely to be deleted, so the timeout could be 548 # reduced accordingly. 549 executetimeout: 30s 550 551 # There are 2 modes: "dev" and "net". 552 # In dev mode, user runs the chaincode after starting peer from 553 # command line on local machine. 554 # In net mode, peer will run chaincode in a docker container. 555 mode: net 556 557 # keepalive in seconds. In situations where the communiction goes through a 558 # proxy that does not support keep-alive, this parameter will maintain connection 559 # between peer and chaincode. 560 # A value <= 0 turns keepalive off 561 keepalive: 0 562 563 # system chaincodes whitelist. To add system chaincode "myscc" to the 564 # whitelist, add "myscc: enable" to the list below, and register in 565 # chaincode/importsysccs.go 566 system: 567 _lifecycle: enable 568 cscc: enable 569 lscc: enable 570 escc: enable 571 vscc: enable 572 qscc: enable 573 574 # Logging section for the chaincode container 575 logging: 576 # Default level for all loggers within the chaincode container 577 level: info 578 # Override default level for the 'shim' logger 579 shim: warning 580 # Format for the chaincode container logs 581 format: '%{color}%{time:2006-01-02 15:04:05.000 MST} [%{module}] %{shortfunc} -> %{level:.4s} %{id:03x}%{color:reset} %{message}' 582 583 ############################################################################### 584 # 585 # Ledger section - ledger configuration encompasses both the blockchain 586 # and the state 587 # 588 ############################################################################### 589 ledger: 590 591 blockchain: 592 593 state: 594 # stateDatabase - options are "goleveldb", "CouchDB" 595 # goleveldb - default state database stored in goleveldb. 596 # CouchDB - store state database in CouchDB 597 stateDatabase: goleveldb 598 # Limit on the number of records to return per query 599 totalQueryLimit: 100000 600 couchDBConfig: 601 # It is recommended to run CouchDB on the same server as the peer, and 602 # not map the CouchDB container port to a server port in docker-compose. 603 # Otherwise proper security must be provided on the connection between 604 # CouchDB client (on the peer) and server. 605 couchDBAddress: 127.0.0.1:5984 606 # This username must have read and write authority on CouchDB 607 username: 608 # The password is recommended to pass as an environment variable 609 # during start up (eg CORE_LEDGER_STATE_COUCHDBCONFIG_PASSWORD). 610 # If it is stored here, the file must be access control protected 611 # to prevent unintended users from discovering the password. 612 password: 613 # Number of retries for CouchDB errors 614 maxRetries: 3 615 # Number of retries for CouchDB errors during peer startup 616 maxRetriesOnStartup: 12 617 # CouchDB request timeout (unit: duration, e.g. 20s) 618 requestTimeout: 35s 619 # Limit on the number of records per each CouchDB query 620 # Note that chaincode queries are only bound by totalQueryLimit. 621 # Internally the chaincode may execute multiple CouchDB queries, 622 # each of size internalQueryLimit. 623 internalQueryLimit: 1000 624 # Limit on the number of records per CouchDB bulk update batch 625 maxBatchUpdateSize: 1000 626 # Warm indexes after every N blocks. 627 # This option warms any indexes that have been 628 # deployed to CouchDB after every N blocks. 629 # A value of 1 will warm indexes after every block commit, 630 # to ensure fast selector queries. 631 # Increasing the value may improve write efficiency of peer and CouchDB, 632 # but may degrade query response time. 633 warmIndexesAfterNBlocks: 1 634 # Create the _global_changes system database 635 # This is optional. Creating the global changes database will require 636 # additional system resources to track changes and maintain the database 637 createGlobalChangesDB: false 638 639 history: 640 # enableHistoryDatabase - options are true or false 641 # Indicates if the history of key updates should be stored. 642 # All history 'index' will be stored in goleveldb, regardless if using 643 # CouchDB or alternate database for the state. 644 enableHistoryDatabase: true 645 646 pvtdataStore: 647 # the maximum db batch size for converting 648 # the ineligible missing data entries to eligible missing data entries 649 collElgProcMaxDbBatchSize: 5000 650 # the minimum duration (in milliseconds) between writing 651 # two consecutive db batches for converting the ineligible missing data entries to eligible missing data entries 652 collElgProcDbBatchesInterval: 1000 653 654 ############################################################################### 655 # 656 # Operations section 657 # 658 ############################################################################### 659 operations: 660 # host and port for the operations server 661 listenAddress: 127.0.0.1:9443 662 663 # TLS configuration for the operations endpoint 664 tls: 665 # TLS enabled 666 enabled: false 667 668 # path to PEM encoded server certificate for the operations server 669 cert: 670 file: "cert.pem" 671 672 # path to PEM encoded server key for the operations server 673 key: 674 file: "key.pem" 675 676 # most operations service endpoints require client authentication when TLS 677 # is enabled. clientAuthRequired requires client certificate authentication 678 # at the TLS layer to access all resources. 679 clientAuthRequired: false 680 681 # paths to PEM encoded ca certificates to trust for client authentication 682 clientRootCAs: 683 files: 684 - "rootcert.pem" 685 686 ############################################################################### 687 # 688 # Metrics section 689 # 690 ############################################################################### 691 metrics: 692 # metrics provider is one of statsd, prometheus, or disabled 693 provider: prometheus 694 695 # statsd configuration 696 statsd: 697 # network type: tcp or udp 698 network: udp 699 700 # statsd server address 701 address: 127.0.0.1:8125 702 703 # the interval at which locally cached counters and gauges are pushed 704 # to statsd; timings are pushed immediately 705 writeInterval: 10s 706 707 # prefix is prepended to all emitted statsd metrics 708 prefix: