Checkmk werks level1 June 2017

checkmk-werks-lvl1@lists.checkmk.com

12 participants
145 discussions

Check_MK Werk 4737: cisco_asa_failover: Now roles of cluster and state of failover is configurable

by Marcel Arentz

ID: 4737 Title: cisco_asa_failover: Now roles of cluster and state of failover is configurable Component: Checks & agents Level: 1 Class: New feature Version: 1.5.0i1 The roles of primary and secondary devices can now be configured. Defaults are "active" for primary and "standby" for secondary. Also the state if a failover takes place can be set.

7 years, 5 months

Check_MK Werk 4879: akcp_sensor_humidity, akcp_exp_humidity: Fixed wrong order of level evaluation

by Simon Betz

ID: 4879 Title: akcp_sensor_humidity, akcp_exp_humidity: Fixed wrong order of level evaluation Component: Checks & agents Level: 1 Class: Bug fix Version: 1.5.0i1

7 years, 5 months

Check_MK Werk 4919: Service discovery: Fixed disabling services with backslashes in description

by Lars Michelsen

ID: 4919 Title: Service discovery: Fixed disabling services with backslashes in description Component: WATO Level: 1 Class: Bug fix Version: 1.5.0i1

7 years, 5 months

Check_MK Werk 4938: Make sure that a notification has the plugin output available

by Sven Panne

ID: 4938 Title: Make sure that a notification has the plugin output available Component: Notifications Level: 1 Class: Bug fix Version: 1.5.0i1 Plugin output in notifications can be either host-related or service-related. Make sure that the resulting notification has always access to the right kind. Previously notifications triggered e.g. by the event console could have an empty plugin output. Note: This was a bug introduced in 1.4.0p6, earlier versions were not affected.

7 years, 5 months

Check_MK Werk 4918: EC views: Hiding wrong icons for events that are not related to a host

by Lars Michelsen

ID: 4918 Title: EC views: Hiding wrong icons for events that are not related to a host Component: Multisite Level: 1 Class: Bug fix Version: 1.5.0i1 This issue was introduced with 1.4.0p6.

7 years, 5 months

Check_MK Werk 4898: Liveproxy daemon: Log level can now be configuration via WATO

by Lars Michelsen

ID: 4898 Title: Liveproxy daemon: Log level can now be configuration via WATO Component: Livestatus Proxy Level: 1 Class: New feature Version: 1.5.0i1

7 years, 5 months

Check_MK Werk 4901: Reworked Livestatus Proxy to be more scalable

by Lars Michelsen

ID: 4901 Title: Reworked Livestatus Proxy to be more scalable Component: Livestatus Proxy Level: 2 Class: New feature Version: 1.5.0i1 The livestatus proxy daemon has been reworked to use a multi process architecture. It now has a master process that mainly cares about monitoring the site processes. Each connected site has an own subprocess that manages all channels to this site and the clients that use these channels to communicate with the sites. When you have a look at ps/top you should see something like this: C+: OMD[heute]:~$ ps -ef | grep liveproxyd UID PID PPID C STIME TTY TIME CMD heute 9261 1 0 11:40 ? 00:00:00 liveproxyd[master] heute 9262 9261 0 11:40 ? 00:00:00 liveproxyd[heute_slave_1] heute 9263 9261 0 11:40 ? 00:00:00 liveproxyd[heute_slave_2] C-: As you can may see there is the master process that has the process <tt>1</tt> as parent process. The site processes have the master as parent. When one site process terminates for some reason the master will restart it. When the master is terminated all site processes will terminate too. In case of a restart or config reload the master will restart itself and stop all site processes and restart them again. With this change the load of the livestatus proxy will now spread over multiple CPUs. Side note: There is a new global setting <i>Logging of the Livestatus Proxy</i> that can be used to control the detail level of the log entries written to the <tt>var/log/liveproxyd.log</tt> log file. In case you experience any issues with the livestatus proxy daemon take a look at this log file and maybe increase the log level to get more details.

7 years, 5 months

Check_MK Werk 4291: mk_postgres, postgres_instances, postgres_bloat, postgres_conn_time, postgres_connections, postgres_locks, postgres_query_duration, postgres_sessions, postgres_stat_database, postgres_stats, postgres_version: plugin and checks are now instance aware

by Simon Betz

ID: 4291 Title: mk_postgres, postgres_instances, postgres_bloat, postgres_conn_time, postgres_connections, postgres_locks, postgres_query_duration, postgres_sessions, postgres_stat_database, postgres_stats, postgres_version: plugin and checks are now instance aware Component: Checks & agents Level: 1 Class: New feature Version: 1.4.0i4 Now the {{mk_postgres}} agent plugin is instance aware. Moreover the new check {{postgres_instances}} reports if instance is running or not. All other checks go PEND if instance is not running. The following lines describe the agent plugin configuration. If you have default postgres installation it's not necessary to give a configuration file, ie. if - user is 'postgres' or 'pgsql' and - PGDATABASE is 'postgres' Configuration of the plugin is needed if you want to monitor multiple instances. Then you have to determine - database user - path to instance env file - user name for this instance - path to .pgpass file where password is stored This can be done via postgres.cfg file with following syntax: DBUSER=DB_USER_NAME INSTANCE=/home/postgres/INSTANCE1.env:USER_NAME:/PATH/TO/.pgpass INSTANCE=/home/postgres/INSTANCE2.env:USER_NAME:/PATH/TO/.pgpass It's incompatible because now the following checks need an item. Thus the service descriptions will change. - postgres_conn_time - postgres_sessions - postgres_version Another reason is that {{postgres_sessions}} needs a new rule set {{PostgreSQL Sessions}} which can handle items. The older one is marked as {{deprecated}}. It is located below {{WATO > Host & Service Parameters > Deprecated Rulesets}}. You have to transfer these old rulesets to new ones which can be found below {{WATO > Host & Service Parameters > Parameters for discovered services > PostgreSQL Sessions}}.

7 years, 5 months

Check_MK Werk 4902: Monitoring history views: Fixed possible XSS when displaying "plugin output"

by Lars Michelsen

ID: 4902 Title: Monitoring history views: Fixed possible XSS when displaying "plugin output" Component: Multisite Level: 1 Class: Security fix Version: 1.5.0i1 A possible XSS issue has been fixed in the monitoring history views displaying the plugin output of hosts or services. In case a host or service problem is being acknowledged with HTML code in the acknowlegement comment, this HTML code was not being escaped properly when being displayed in the "plugin output" column. Only authenticated users that are permitted to acknowledge host or service problems could trigger this issue.

7 years, 5 months

Check_MK Werk 4877: netscaler_vserver: Added some performance data such as request rate, received and transmitted byte rates

by Simon Betz

ID: 4877 Title: netscaler_vserver: Added some performance data such as request rate, received and transmitted byte rates Component: Checks & agents Level: 1 Class: New feature Version: 1.5.0i1

7 years, 5 months

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

Checkmk werks level1 June 2017