Create a template service file at /etc/systemd/system/secure-tunnel@.service. The template parameter will correspond to the name
of target host:
[Unit]
Description=Setup a secure tunnel to %I
After=network.target
Aleksey Lelik13a
CHERTS
/ media_telegram.xml
Created
May 15, 2020 17:59
Fixed use http proxy for official media telegram in Zabbix 5.0
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| <?xml version="1.0" encoding="UTF-8"?> | |
| <zabbix_export> | |
| <version>5.0</version> | |
| <date>2020-05-15T17:57:20Z</date> | |
| <media_types> | |
| <media_type> | |
| <name>Telegram</name> | |
| <type>WEBHOOK</type> | |
| <parameters> | |
| <parameter> |
drmalex07
/ README-setup-tunnel-as-systemd-service.md
Last active
September 13, 2024 00:48
Setup a secure (SSH) tunnel as a systemd service. #systemd #ssh #ssh-tunnel #ssh-forward
Moved to git repository: https://github.com/denji/nginx-tuning
For this configuration you can use web server you like, i decided, because i work mostly with it to use nginx.
Generally, properly configured nginx can handle up to 400K to 500K requests per second (clustered), most what i saw is 50K to 80K (non-clustered) requests per second and 30% CPU load, course, this was 2 x Intel Xeon with HyperThreading enabled, but it can work without problem on slower machines.
You must understand that this config is used in testing environment and not in production so you will need to find a way to implement most of those features best possible for your servers.