The Graylog Extended Log Format (GELF) is a log format that avoids the shortcomings of classic plain syslog:
- Limited to length of 1024 bytes. Inadequate space for payloads like backtraces.
- No data types in structured syslog. Numbers and strings are indistinguishable.
- The RFCs are strict enough, but there are so many syslog dialects out there that you cannot possibly parse all of them.
- No compression.
Syslog is sufficient for logging system messages of machines or network gear, while GELF is a strong choice for logging from within applications. There are libraries and appenders for many programming languages and logging frameworks, so it is easy to implement. GELF can send every exception as a log message to your Graylog cluster without complications from timeouts, connection problems, or anything that may break your application from within your logging class because GELF can be sent via UDP.
!(Graylog GELF)(https://go2docs.graylog.org/current/resources/images/logo.png)
Proxy UDP connections over HTTP(s). The main use case is to proxy WireGuard packets.
VXLAN is an overlay network to carry Ethernet traffic over an existing (highly available and scalable) IP network while accommodating a very large number of tenants. It is defined in RFC 7348.
Starting from Linux 3.12, the VXLAN implementation is quite complete as both multicast and unicast are supported as well as IPv6 and IPv4. Let’s explore the various methods to configure it.
Dieser Artikel beschreibt welche TCP/UDP Ports auf einer Firewall für einen Zugriff auf die unterschiedlichen Dienste (z.B. Webinterface, IPMI, Remote Console) des Full Remote Managements von Supermicro Servern offen sein müssen.
The following configuration reads the Windows EventLog and sends it to the Graylog2 server in GELF format.
In concept nxlog is similar to syslog-ng or rsyslog but it is not limited to unix and syslog only. It supports different platforms, log sources and formats so nxlog can be an ideal choice to implement a centralized logging system.
Centralize your Windows, Unix, Linux, BSD, Android and application logs on Windows, Unix, Linux, BSD, Android.
Main features
This is a short but not exhaustive list of supported features on this beta version:
Powerful MCU (Multipoint Control Unit) for audio and video mixing
Stereoscopic (spatial) 3D and stereophonic audio
Full (1080p) and Ultra (2160p) HD video up to 120fps
Conference recording to a file (containers: .mp4, .avi, .mkv or .webm)
Revolutionary way to share presentations: documents are "streamed" in the video channel to allow any SIP client running on any device to participate
Smart adaptive audio and video bandwidth management
Congestion control mechanism
SIP registrar
4 SIP transports (WebSocket, TCP, TLS and UDP)
SA (direct connection to SIP clients) and AS (behind a server, such as Asterisk, reSIProcate, openSIPS, Kamailio…) modes
Support for any WebRTC-capable browser (WebRTC demo client at http://conf-call.org/)
Mixing different audio and video codecs on a single bridge (h264, vp8, h263, mp4v-es, theora, opus, g711, speex, g722, gsm, g729, amr, ilbc)
Protecting a bridge with PIN code
Unlimited number of bridges and participants
Connecting any SIP client (Mobiles, Tablets, Desktops, Set-top-boxes, Smart TVs...)
Easy interconnection with PSTN
NAT traversal (Symmetric RTP, RTCP-MUX, ICE, STUN and TURN)
RTCP Feedbacks (NACK, PLI, FIR, TMMBN, REMB…) for better video experience
Secure signalling (WSS, TLS) and media (SDES-SRTP and DTLS-SRTP)
Continuous presence
Smart algorithm to detect speakers and listeners
Different video patterns/layouts
Multiple operating systems (Linux, OS X, Windows …)
100% open source and free (no locked features)
Full documentation
…and many others
libuv is a multi-platform support library with a focus on asynchronous I/O. It was primarily developed for use by Node.js, but it’s also used by Luvit, Julia, pyuv, and others.