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 in metrics.txt summary of available metrics from mq-golang
* JSON exporter - consistent objecttype for qmgr, merge published and
polled metrics (#188)
* JSON exporter - allow configuration (`recordmax`) for number of objects
printed in a single JSON record (also #188)
* AWS exporter -correct interval processing (#192)
* Simplified build/run in a single Dockerfile (#194)
Copy file name to clipboardExpand all lines: README.md
+23-12Lines changed: 23 additions & 12 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -48,7 +48,7 @@ any privileges to install:
48
48
See the README file in the mq-golang repository for more information about any environment variables that may
49
49
be required to point at non-default directories for the MQ C SDK.
50
50
51
-
### Building a component
51
+
### Building a component on your system directly
52
52
53
53
* You need to have the MQ client libraries installed first.
54
54
* Create a directory where you want to work with the programs.
@@ -78,14 +78,24 @@ with getting the agent running in your specific environment.
78
78
The `-mod=vendor` option is important so that the build process does not need to
79
79
download additional files from external repositories.
80
80
81
-
## Using a Docker container to build the programs
82
-
You can use the `buildMonitors.sh` script in the `scripts` subdirectory to build a Docker container that
83
-
in turn will build all the binary programs and copy them to a local directory. That script also
84
-
sets some extra version-related flags that will be shown when the program starts. The container will
85
-
automatically download and install the MQ client runtime files needed for compilation.
81
+
## Using containers to build the programs
82
+
The `Dockerfile` in the root directory gives a simple way to both build and run a collector program through
83
+
containers. You still need to provide the configuration file at runtime, perhaps as a mounted volume. For example:
86
84
87
-
## Building on Windows
88
-
There is a `buildMonitors.bat` file that may help with building on Windows. It assumes you have
85
+
```
86
+
docker build -t mqprom:1.0 .
87
+
docker run -v <directory>/mq_prometheus.yaml:/opt/config/mq_prometheus.yaml mqprom:1.0
88
+
```
89
+
90
+
As a more flexible example, you can use the `buildMonitors.sh` script in the `scripts` subdirectory to
91
+
build a Docker container that in turn will build all the binary programs and copy them to a local directory.
92
+
That script also sets some extra version-related flags that will be shown when the program starts. The container will
93
+
automatically download and install the MQ client runtime files needed for compilation. This might be a preferred approach when you want to run a collector program alongside
94
+
a queue manager (perhaps as an MQ SERVICE) and you need to copy the binaries to the
95
+
target system.
96
+
97
+
## Building to run on Windows
98
+
There is a `buildMonitors.bat` file to help with building on Windows. It assumes you have
89
99
the [tdm-gcc-64](https://jmeubank.github.io/tdm-gcc/download/) 64-bit compiler suite installed. It
90
100
builds all the collectors and corresponding YAML configuration files into %GOPATH%/bin
91
101
@@ -111,7 +121,7 @@ An alternative collection mechanism uses durable subscriptions for the queue met
111
121
the MAXHANDS attribute on a queue manager. (Queue manager-level metrics are still collected using non-durable subscriptions.)
112
122
113
123
To set it up, you must provide suitable configuration options. In the
114
-
YAML configuration, these are the attributes (command line or environment variable equivalents exist):
124
+
YAML configuration, these are the attributes (command line or environment variable equivalents also exist):
115
125
-`replyQueue` must refer to a local queue (not a model queue)
116
126
-`replyQueue2` must also be set, referring to a different local queue
117
127
-`durableSubPrefix` is a string that is unique across any collectors that might be connected to this queue manager
@@ -237,7 +247,7 @@ That allows it to be piped from an external stash file or some other
237
247
mechanism. Using the command line flags for controlling passwords is not
238
248
recommended for security-sensitive environments.
239
249
240
-
Where authentication is needed for access to the database, passwords for those can
250
+
Where authentication is needed for access to a database, passwords for those can
241
251
also be passed via stdin.
242
252
243
253
## YAML configuration for all exporters
@@ -272,7 +282,8 @@ The command line flags are highest precedence. Environment variables override se
272
282
273
283
## More information
274
284
Each of the sample monitor programs has its own README file describing any particular
275
-
considerations.
285
+
considerations. The metrics.txt file in this directory has a summary of the available
0 commit comments