Fix sample_config.yaml in regards track_puppeted_user_ips

changelog.d/11749.feature

@@ -0,0 +1 @@
+Add `track_puppeted_user_ips` config flag to track puppeted user IP addresses. This also includes them in monthly active user counts.

docs/sample_config.yaml

@@ -1503,11 +1503,12 @@ room_prejoin_state:
    #additional_event_types:
    #  - org.example.custom.event.type
 
-# If enabled, puppeted user IP's can also be tracked. By default when
-# puppeting another user, the user who has created the access token
-# for puppeting is tracked. If this is enabled, both requests are tracked.
-# Implicitly enables MAU tracking for puppeted users.
-#track_puppeted_user_ips: false
+# By default when puppeting another user, the user who has created the
+# access token for puppeting is tracked. If this is enabled, both
+# requests are tracked. Implicitly enables MAU tracking for puppeted users.
+# Uncomment to also track puppeted user IP's.
+#
+#track_puppeted_user_ips: true
 
 
 # A list of application service config files to use

synapse/config/api.py

@@ -61,11 +61,12 @@ def generate_config_section(cls, **kwargs) -> str:
            #additional_event_types:
            #  - org.example.custom.event.type
 
-        # If enabled, puppeted user IP's can also be tracked. By default when
-        # puppeting another user, the user who has created the access token
-        # for puppeting is tracked. If this is enabled, both requests are tracked.
-        # Implicitly enables MAU tracking for puppeted users.
-        #track_puppeted_user_ips: false
+        # By default when puppeting another user, the user who has created the
+        # access token for puppeting is tracked. If this is enabled, both
+        # requests are tracked. Implicitly enables MAU tracking for puppeted users.
+        # Uncomment to also track puppeted user IP's.
+        #
+        #track_puppeted_user_ips: true
         """ % {
             "formatted_default_state_types": formatted_default_state_types
         }