Event triggers for Icecast 2.5
We are introducing event triggers and need to decide what we trigger on. Currently already supported:
- source-connect
- source-disconnect
- icecast-start
- icecast-stop
Proposed additional triggers:
- client-connect (all connections that are !SOURCE|!PUT)
- client-disconnect (all connections that are !SOURCE|!PUT)
- icecast-reload (configuration reload as caused SIGHUP or web request)
- yp-failure
- metadata-change (Both in container and side-channel triggered, with differentiating field)
- various admin commands (Including authentication management)
- critical errors or even general logging (this needs to be thought through)