e1d73c4b5d
Currently we don't have any capability to monitor the internal TLS/SSL certificates. i.e. SSL certificates used by MySQL for replication, RabbitMQ for distribution, etc. The cert_check plugin is not adequate for this purpose becaue it can only check on certficates over HTTPS endpoints. Furthermore, checking on these internal certificates over the network is cumbersome because the agent plugin would have to speak specific protocols. This patch adds a cert_file_check plugin to detect the certificate expiry (in days from now) for the given X.509 certificate file in PEM format. Similar to cert_check plugin, this plugin will a metric 'cert_file.cert_expire_days' which contains the number of days from now the given certificate will be expired. If the certificate has already expired, this will be a negative number. Change-Id: Id95cc7115823f972e234417223ab5906b57447cc Story: 2006753
14 lines
493 B
Plaintext
14 lines
493 B
Plaintext
# The order of packages is significant, because pip processes them in the order
|
|
# of appearance. Changing the order has an impact on the overall integration
|
|
# process, which may cause wedges in the gate later.
|
|
hacking>=1.1.0,<1.2.0 # Apache-2.0
|
|
bandit!=1.6.0,>=1.1.0 # Apache-2.0
|
|
mock>=2.0.0 # BSD
|
|
coverage!=4.4,>=4.0 # Apache-2.0
|
|
oslotest>=3.2.0 # Apache-2.0
|
|
prometheus_client
|
|
stestr>=1.0.0 # Apache-2.0
|
|
docutils>=0.11 # OSI-Approved Open Source, Public Domain
|
|
freezegun>=0.3.6 # Apache-2.0
|
|
|