Skip to content

Commit 33ad617

Browse files
authored
Merge pull request #118 from Cinimex-Informatica/feature/issue49_comment_using_wildcards
add extended explanation for using wildcards
2 parents 7a6a509 + 658da0d commit 33ad617

File tree

2 files changed

+12
-4
lines changed

2 files changed

+12
-4
lines changed

README.md

Lines changed: 6 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -111,8 +111,12 @@ PCFParameters:
111111
# Collect additional metrics? If false, all settings in this section below are ignored.
112112
# If yes, additional metrics will be collected for all queues, channels and listeners listed below.
113113
sendPCFCommands: true
114-
# Use wildcards? If yes, only one PCF command will be send, matching all objects on queue manager. Otherwise, each
115-
# object will be monitored by separate PCF command.
114+
# If usePCFWildcards equals "true", then all monitored objects will be grouped by object type: QUEUE, CHANNEL and LISTENER. Only one PCF command will be sent for each object type.
115+
# If usePCFWildcards equals "false", then PCF command will be send for each object.
116+
# Each PCF command uses a separate connection, so sending a large number of PCF commands will create a large number of connections to MQ queue manager.
117+
# For example, for 100 monitoring queues will be opened 100 connections to MQ queue manager, if usePCFwildcard equals "false".
118+
# On the other hand, for usePCFwildcard equals "true", if there are 10.000 queues in the queue manager and just a few queues is need to be monitored,
119+
# only one PCF command will be sent. But response will contain metrics for all 10.000 queues and that will lead to performance problems.
116120
usePCFWildcards: true
117121
# Interval in seconds between sending PCF commands.
118122
scrapeInterval: 10

src/main/resources/exporter_config.yaml

Lines changed: 6 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -36,8 +36,12 @@ PCFParameters:
3636
# Collect additional metrics? If false, all settings in this section below are ignored.
3737
# If yes, additional metrics will be collected for all queues, channels and listeners listed below.
3838
sendPCFCommands: true
39-
# Use wildcards? If yes, only one PCF command will be send, matching all objects on queue manager. Otherwise, each
40-
# object will be monitored by separate PCF command.
39+
# If usePCFWildcards equals "true", then all monitored objects will be grouped by object type: QUEUE, CHANNEL and LISTENER. Only one PCF command will be sent for each object type.
40+
# If usePCFWildcards equals "false", then PCF command will be send for each object.
41+
# Each PCF command uses a separate connection, so sending a large number of PCF commands will create a large number of connections to MQ queue manager.
42+
# For example, for 100 monitoring queues will be opened 100 connections to MQ queue manager, if usePCFwildcard equals "false".
43+
# On the other hand, for usePCFwildcard equals "true", if there are 10.000 queues in the queue manager and just a few queues is need to be monitored,
44+
# only one PCF command will be sent. But response will contain metrics for all 10.000 queues and that will lead to performance problems.
4145
usePCFWildcards: true
4246
# Interval in seconds between sending PCF commands.
4347
scrapeInterval: 10

0 commit comments

Comments
 (0)