[inputs.socket_listener] Add support for Source-Specific-Multicast

(2 Kommentare) (0 Reaktionen) (0 zugewiesene Personen)Go (5.831 Forks)batch import

feature requesthelp wantedsize/m

Repository-Metriken

Stars: (17.731 Sterne)
PR-Merge-Metriken: (Durchschn. Merge 2T 12h) (136 gemergte PRs in 30 T)

Beschreibung

Use Case

I want to use the socket_listener to join and receive messages from Source-Specific-Multicast (SSM) groups using IGMPv3.

Expected behavior

When the socket_listener is configured with a specific "multicast_source" and a multicast "service_address", I expect telegraf to join the multicast group using IGMPv3 "IP_ADD_SOURCE_MULTICAST".

Actual behavior

Currently telegraf's socket_listener can only join Any-Source-Multicast (ASM) groups using "IP_ADD_MEMBERSHIP". No SSM messages can be received as SSM requires listeners to join using the correct join request.

Additional info

No response

Contributor Guide

Research-Richtung: Investigate the socket listener plugin in Telegraf, specifically the code that handles multicast joins (likely using syscall.Setsockopt). Research Go's net package for IP ADD SOURCE MEMBERSHIP (syscall.IP ADD SOURCE MEMBERSHIP) and how to implement IGMPv3. Review existing multicast implementation to understand the structure. Test on Linux with a known SSM source. Look for any related issues or PRs in the repository.
Tech Stack: go
Domain: backend
Issue Type: Funktion
Schwierigkeit: 3
Geschätzte Zeit: 1-2 Tage
Aktivitätsstatus: Frisch
Klarheit: Meist klar
Voraussetzungen: Go programmingnetworking basicsmulticast concepts
Einsteigerfreundlichkeit: 40