o2webappizer 0.2.2 → 0.2.3
Sign up to get free protection for your applications and to get access to all the features.
- checksums.yaml +4 -4
- data/lib/o2webappizer/version.rb +1 -1
- data/templates/config/monitrc.erb +253 -0
- metadata +2 -1
checksums.yaml
CHANGED
@@ -1,7 +1,7 @@
|
|
1
1
|
---
|
2
2
|
SHA1:
|
3
|
-
metadata.gz:
|
4
|
-
data.tar.gz:
|
3
|
+
metadata.gz: 9539c730cde11c65b839c72c77492e398ec6f04f
|
4
|
+
data.tar.gz: 25d8604d7c477b2f757be323add62e75832cd045
|
5
5
|
SHA512:
|
6
|
-
metadata.gz:
|
7
|
-
data.tar.gz:
|
6
|
+
metadata.gz: 8936f9eea9a1fddc6753845f4616936d73072d876c477ecc1afa4beccc56ee818a0252137e158811f1547e8c71e4d55d4a8bca4aa7fc5ab5de673dee2c820541
|
7
|
+
data.tar.gz: bb1817bc7f851bc3d79d48cb125b40a5dfd6a66c391674eb661676c81b83d23c026abbfa3f5e89d17b96e09db8343f3ec7286a6beffc3d50b9b15caafd8ab2c7
|
data/lib/o2webappizer/version.rb
CHANGED
@@ -0,0 +1,253 @@
|
|
1
|
+
###############################################################################
|
2
|
+
## Monit control file
|
3
|
+
###############################################################################
|
4
|
+
##
|
5
|
+
## Comments begin with a '#' and extend through the end of the line. Keywords
|
6
|
+
## are case insensitive. All path's MUST BE FULLY QUALIFIED, starting with '/'.
|
7
|
+
##
|
8
|
+
## Below you will find examples of some frequently used statements. For
|
9
|
+
## information about the control file and a complete list of statements and
|
10
|
+
## options, please have a look in the Monit manual.
|
11
|
+
##
|
12
|
+
##
|
13
|
+
###############################################################################
|
14
|
+
## Global section
|
15
|
+
###############################################################################
|
16
|
+
##
|
17
|
+
## Start Monit in the background (run as a daemon):
|
18
|
+
#
|
19
|
+
set daemon 120 # check services at 2-minute intervals
|
20
|
+
# with start delay 240 # optional: delay the first check by 4-minutes (by
|
21
|
+
# # default Monit check immediately after Monit start)
|
22
|
+
#
|
23
|
+
#
|
24
|
+
## Set syslog logging with the 'daemon' facility. If the FACILITY option is
|
25
|
+
## omitted, Monit will use 'user' facility by default. If you want to log to
|
26
|
+
## a standalone log file instead, specify the full path to the log file
|
27
|
+
#
|
28
|
+
# set logfile syslog facility log_daemon
|
29
|
+
set logfile /var/log/monit.log
|
30
|
+
#
|
31
|
+
#
|
32
|
+
## Set the location of the Monit id file which stores the unique id for the
|
33
|
+
## Monit instance. The id is generated and stored on first Monit start. By
|
34
|
+
## default the file is placed in $HOME/.monit.id.
|
35
|
+
#
|
36
|
+
# set idfile /var/.monit.id
|
37
|
+
set idfile /var/lib/monit/id
|
38
|
+
#
|
39
|
+
## Set the location of the Monit state file which saves monitoring states
|
40
|
+
## on each cycle. By default the file is placed in $HOME/.monit.state. If
|
41
|
+
## the state file is stored on a persistent filesystem, Monit will recover
|
42
|
+
## the monitoring state across reboots. If it is on temporary filesystem, the
|
43
|
+
## state will be lost on reboot which may be convenient in some situations.
|
44
|
+
#
|
45
|
+
set statefile /var/lib/monit/state
|
46
|
+
#
|
47
|
+
## Set the list of mail servers for alert delivery. Multiple servers may be
|
48
|
+
## specified using a comma separator. If the first mail server fails, Monit
|
49
|
+
# will use the second mail server in the list and so on. By default Monit uses
|
50
|
+
# port 25 - it is possible to override this with the PORT option.
|
51
|
+
#
|
52
|
+
# set mailserver mail.bar.baz, # primary mailserver
|
53
|
+
# backup.bar.baz port 10025, # backup mailserver on port 10025
|
54
|
+
# localhost # fallback relay
|
55
|
+
#
|
56
|
+
#
|
57
|
+
## By default Monit will drop alert events if no mail servers are available.
|
58
|
+
## If you want to keep the alerts for later delivery retry, you can use the
|
59
|
+
## EVENTQUEUE statement. The base directory where undelivered alerts will be
|
60
|
+
## stored is specified by the BASEDIR option. You can limit the maximal queue
|
61
|
+
## size using the SLOTS option (if omitted, the queue is limited by space
|
62
|
+
## available in the back end filesystem).
|
63
|
+
#
|
64
|
+
set eventqueue
|
65
|
+
basedir /var/lib/monit/events # set the base directory where events will be stored
|
66
|
+
slots 100 # optionally limit the queue size
|
67
|
+
#
|
68
|
+
#
|
69
|
+
## Send status and events to M/Monit (for more informations about M/Monit
|
70
|
+
## see http://mmonit.com/). By default Monit registers credentials with
|
71
|
+
## M/Monit so M/Monit can smoothly communicate back to Monit and you don't
|
72
|
+
## have to register Monit credentials manually in M/Monit. It is possible to
|
73
|
+
## disable credential registration using the commented out option below.
|
74
|
+
## Though, if safety is a concern we recommend instead using https when
|
75
|
+
## communicating with M/Monit and send credentials encrypted.
|
76
|
+
#
|
77
|
+
# set mmonit http://monit:monit@192.168.1.10:8080/collector
|
78
|
+
# # and register without credentials # Don't register credentials
|
79
|
+
#
|
80
|
+
#
|
81
|
+
## Monit by default uses the following format for alerts if the the mail-format
|
82
|
+
## statement is missing::
|
83
|
+
## --8<--
|
84
|
+
## set mail-format {
|
85
|
+
## from: monit@$HOST
|
86
|
+
## subject: monit alert -- $EVENT $SERVICE
|
87
|
+
## message: $EVENT Service $SERVICE
|
88
|
+
## Date: $DATE
|
89
|
+
## Action: $ACTION
|
90
|
+
## Host: $HOST
|
91
|
+
## Description: $DESCRIPTION
|
92
|
+
##
|
93
|
+
## Your faithful employee,
|
94
|
+
## Monit
|
95
|
+
## }
|
96
|
+
## --8<--
|
97
|
+
##
|
98
|
+
## You can override this message format or parts of it, such as subject
|
99
|
+
## or sender using the MAIL-FORMAT statement. Macros such as $DATE, etc.
|
100
|
+
## are expanded at runtime. For example, to override the sender, use:
|
101
|
+
#
|
102
|
+
# set mail-format { from: monit@foo.bar }
|
103
|
+
#
|
104
|
+
#
|
105
|
+
## You can set alert recipients whom will receive alerts if/when a
|
106
|
+
## service defined in this file has errors. Alerts may be restricted on
|
107
|
+
## events by using a filter as in the second example below.
|
108
|
+
#
|
109
|
+
# set alert sysadm@foo.bar # receive all alerts
|
110
|
+
## Do not alert when Monit start,stop or perform a user initiated action
|
111
|
+
# set alert manager@foo.bar not on { instance, action }
|
112
|
+
#
|
113
|
+
#
|
114
|
+
## Monit has an embedded web server which can be used to view status of
|
115
|
+
## services monitored and manage services from a web interface. See the
|
116
|
+
## Monit Wiki if you want to enable SSL for the web server.
|
117
|
+
#
|
118
|
+
set httpd port 2812 and
|
119
|
+
use address localhost # only accept connection from localhost
|
120
|
+
allow localhost # allow localhost to connect to the server and
|
121
|
+
allow admin:monit # require user 'admin' with password 'monit'
|
122
|
+
allow @monit # allow users of group 'monit' to connect (rw)
|
123
|
+
allow @users readonly # allow users of group 'users' to connect readonly
|
124
|
+
#
|
125
|
+
###############################################################################
|
126
|
+
## Services
|
127
|
+
###############################################################################
|
128
|
+
##
|
129
|
+
## Check general system resources such as load average, cpu and memory
|
130
|
+
## usage. Each test specifies a resource, conditions and the action to be
|
131
|
+
## performed should a test fail.
|
132
|
+
#
|
133
|
+
# check system myhost.mydomain.tld
|
134
|
+
# if loadavg (1min) > 4 then alert
|
135
|
+
# if loadavg (5min) > 2 then alert
|
136
|
+
# if memory usage > 75% then alert
|
137
|
+
# if swap usage > 25% then alert
|
138
|
+
# if cpu usage (user) > 70% then alert
|
139
|
+
# if cpu usage (system) > 30% then alert
|
140
|
+
# if cpu usage (wait) > 20% then alert
|
141
|
+
#
|
142
|
+
#
|
143
|
+
## Check if a file exists, checksum, permissions, uid and gid. In addition
|
144
|
+
## to alert recipients in the global section, customized alert can be sent to
|
145
|
+
## additional recipients by specifying a local alert handler. The service may
|
146
|
+
## be grouped using the GROUP option. More than one group can be specified by
|
147
|
+
## repeating the 'group name' statement.
|
148
|
+
#
|
149
|
+
# check file apache_bin with path /usr/local/apache/bin/httpd
|
150
|
+
# if failed checksum and
|
151
|
+
# expect the sum 8f7f419955cefa0b33a2ba316cba3659 then unmonitor
|
152
|
+
# if failed permission 755 then unmonitor
|
153
|
+
# if failed uid root then unmonitor
|
154
|
+
# if failed gid root then unmonitor
|
155
|
+
# alert security@foo.bar on {
|
156
|
+
# checksum, permission, uid, gid, unmonitor
|
157
|
+
# } with the mail-format { subject: Alarm! }
|
158
|
+
# group server
|
159
|
+
#
|
160
|
+
#
|
161
|
+
## Check that a process is running, in this case Apache, and that it respond
|
162
|
+
## to HTTP and HTTPS requests. Check its resource usage such as cpu and memory,
|
163
|
+
## and number of children. If the process is not running, Monit will restart
|
164
|
+
## it by default. In case the service is restarted very often and the
|
165
|
+
## problem remains, it is possible to disable monitoring using the TIMEOUT
|
166
|
+
## statement. This service depends on another service (apache_bin) which
|
167
|
+
## is defined above.
|
168
|
+
#
|
169
|
+
# check process apache with pidfile /usr/local/apache/logs/httpd.pid
|
170
|
+
# start program = "/etc/init.d/httpd start" with timeout 60 seconds
|
171
|
+
# stop program = "/etc/init.d/httpd stop"
|
172
|
+
# if cpu > 60% for 2 cycles then alert
|
173
|
+
# if cpu > 80% for 5 cycles then restart
|
174
|
+
# if totalmem > 200.0 MB for 5 cycles then restart
|
175
|
+
# if children > 250 then restart
|
176
|
+
# if loadavg(5min) greater than 10 for 8 cycles then stop
|
177
|
+
# if failed host www.tildeslash.com port 80 protocol http
|
178
|
+
# and request "/somefile.html"
|
179
|
+
# then restart
|
180
|
+
# if failed port 443 type tcpssl protocol http
|
181
|
+
# with timeout 15 seconds
|
182
|
+
# then restart
|
183
|
+
# if 3 restarts within 5 cycles then timeout
|
184
|
+
# depends on apache_bin
|
185
|
+
# group server
|
186
|
+
#
|
187
|
+
#
|
188
|
+
## Check filesystem permissions, uid, gid, space and inode usage. Other services,
|
189
|
+
## such as databases, may depend on this resource and an automatically graceful
|
190
|
+
## stop may be cascaded to them before the filesystem will become full and data
|
191
|
+
## lost.
|
192
|
+
#
|
193
|
+
# check filesystem datafs with path /dev/sdb1
|
194
|
+
# start program = "/bin/mount /data"
|
195
|
+
# stop program = "/bin/umount /data"
|
196
|
+
# if failed permission 660 then unmonitor
|
197
|
+
# if failed uid root then unmonitor
|
198
|
+
# if failed gid disk then unmonitor
|
199
|
+
# if space usage > 80% for 5 times within 15 cycles then alert
|
200
|
+
# if space usage > 99% then stop
|
201
|
+
# if inode usage > 30000 then alert
|
202
|
+
# if inode usage > 99% then stop
|
203
|
+
# group server
|
204
|
+
#
|
205
|
+
#
|
206
|
+
## Check a file's timestamp. In this example, we test if a file is older
|
207
|
+
## than 15 minutes and assume something is wrong if its not updated. Also,
|
208
|
+
## if the file size exceed a given limit, execute a script
|
209
|
+
#
|
210
|
+
# check file database with path /data/mydatabase.db
|
211
|
+
# if failed permission 700 then alert
|
212
|
+
# if failed uid data then alert
|
213
|
+
# if failed gid data then alert
|
214
|
+
# if timestamp > 15 minutes then alert
|
215
|
+
# if size > 100 MB then exec "/my/cleanup/script" as uid dba and gid dba
|
216
|
+
#
|
217
|
+
#
|
218
|
+
## Check directory permission, uid and gid. An event is triggered if the
|
219
|
+
## directory does not belong to the user with uid 0 and gid 0. In addition,
|
220
|
+
## the permissions have to match the octal description of 755 (see chmod(1)).
|
221
|
+
#
|
222
|
+
# check directory bin with path /bin
|
223
|
+
# if failed permission 755 then unmonitor
|
224
|
+
# if failed uid 0 then unmonitor
|
225
|
+
# if failed gid 0 then unmonitor
|
226
|
+
#
|
227
|
+
#
|
228
|
+
## Check a remote host availability by issuing a ping test and check the
|
229
|
+
## content of a response from a web server. Up to three pings are sent and
|
230
|
+
## connection to a port and an application level network check is performed.
|
231
|
+
#
|
232
|
+
# check host myserver with address 192.168.1.1
|
233
|
+
# if failed icmp type echo count 3 with timeout 3 seconds then alert
|
234
|
+
# if failed port 3306 protocol mysql with timeout 15 seconds then alert
|
235
|
+
# if failed url http://user:password@www.foo.bar:8080/?querystring
|
236
|
+
# and content == 'action="j_security_check"'
|
237
|
+
# then alert
|
238
|
+
#
|
239
|
+
#
|
240
|
+
check process nginx with pidfile /var/run/nginx.pid
|
241
|
+
start program = "/etc/init.d/nginx start"
|
242
|
+
stop program = "/etc/init.d/nginx stop"
|
243
|
+
if failed host 127.0.0.1 port 80 then restart
|
244
|
+
|
245
|
+
###############################################################################
|
246
|
+
## Includes
|
247
|
+
###############################################################################
|
248
|
+
##
|
249
|
+
## It is possible to include additional configuration parts from other files or
|
250
|
+
## directories.
|
251
|
+
#
|
252
|
+
include /etc/monit/conf.d/*
|
253
|
+
#
|
metadata
CHANGED
@@ -1,7 +1,7 @@
|
|
1
1
|
--- !ruby/object:Gem::Specification
|
2
2
|
name: o2webappizer
|
3
3
|
version: !ruby/object:Gem::Version
|
4
|
-
version: 0.2.
|
4
|
+
version: 0.2.3
|
5
5
|
platform: ruby
|
6
6
|
authors:
|
7
7
|
- Patrice Lebel
|
@@ -127,6 +127,7 @@ files:
|
|
127
127
|
- templates/config/locales/en.yml
|
128
128
|
- templates/config/locales/routes.en.yml
|
129
129
|
- templates/config/locales/simple_form.en.yml
|
130
|
+
- templates/config/monitrc.erb
|
130
131
|
- templates/config/nginx.app.conf.erb
|
131
132
|
- templates/config/nginx.conf.erb
|
132
133
|
- templates/config/routes.rb.tt
|