Browse Source

'prosody/loggrep_prosodys2sfails/README.md' ändern

Fix for Prosody 0.10 usage
master
Martin Sebald 4 years ago
parent
commit
95329a1cc3
  1. 14
      prosody/loggrep_prosodys2sfails/README.md

14
prosody/loggrep_prosodys2sfails/README.md

@ -13,6 +13,8 @@ Create symlink:
`ln -s /usr/share/munin/plugins/loggrep /etc/munin/plugins/loggrep_prosodys2sfails`
Create a file */etc/munin/plugin-conf.d/loggrep_prosodys2sfails* (we don't want change the standard file */etc/munin/plugin-conf.d/munin-node* as future updates might want to undo the changes) and put the following into it:
**Prosody 0.9:**
```
[loggrep_prosodys2sfails]
user root
@ -24,6 +26,18 @@ env.logfile /var/log/prosody/prosody.log
env.title Prosody failed encrypted S2S communication
```
**Prosody 0.10:**
```
[loggrep_prosodys2sfails]
user root
env.regex_outencfailed Outgoing s2s stream .* closed: Encrypted server-to-server communication is required but was not offered
env.label_outencfailed outgoing S2S encryption failed
env.regex_inencfailed Incoming s2s stream .* closed: Encrypted server-to-server communication is required but was not used
env.label_inencfailed incoming S2S encryption failed
env.logfile /var/log/prosody/prosody.log
env.title Prosody failed encrypted S2S communication
```
Edit */etc/munin/munin.conf* - in our case we have a Munin host named *tethys.hot-chilli.net*, please add it under the specifications for your own host:
```
[tethys.hot-chilli.net]

Loading…
Cancel
Save