icinga2

Author	SHA1	Message	Date
Julian Brost	e6300aacf9	InfluxdbCommonWriter: only flush from work queue There is no explicit synchronization of access to m_DataBuffer which is fine if it is only accessed from the single-threaded work queue. However, Stop() also called Flush() in another thread, leading to concurrent write access to m_DataBuffer which can result in a crash due to use after free/double free. Changes in this commit: * Flush() is renamed to FlushWQ() to show that it should only be called from the work queue. Additionally, it now asserts that it is running on the work queue. * Visibility of some data members is changed from protected to private. No other classes have to access these at the moment. By this change, accidental concurrent access from derived classes in the future is prevented. * Stop() now flushes by posting FlushWQ() to the work queue and joining it.	2022-01-03 12:24:26 +01:00
Alexander Aleksandrovič Klimov	99c5c24a17	InfluxdbCommonWriter#Flush(): fix log message s/InfluxdbWriter/Influxdb2Writer/ fixes #9035	2021-10-14 12:03:45 +02:00
Julian Brost	8f3f692ecf	InfluxdbCommonWriter: actually verify TLS server certificates And add a new option ssl_insecure_noverify to explicitly disable it if desired.	2021-08-13 17:24:24 +02:00
Alexander A. Klimov	d26aa9fb34	InfluxdbCommonWriter: abstract InfluxdbWriter refs #8711	2021-07-20 16:21:36 +02:00