Update UDP docs for the new executor

src/content/docs/integrations/syslog.mdx

@@ -201,7 +201,7 @@ from {
   message: " PARENT process running...",
 }
 write_syslog
-save_udp "1.2.3.4:514"
+to_udp "1.2.3.4:514"
 ```
 
 This pipeline sends the following RFC 5424-formatted message to

src/content/docs/integrations/udp.mdx

@@ -15,8 +15,8 @@ Use the IP address `0.0.0.0` to listen on all available network interfaces.
 ## Examples
 
 Use <Op>from_udp</Op> to receive UDP datagrams as
-structured events containing message data and peer information. For sending, use
-<Op>save_udp</Op> with a write operator.
+structured events containing message data and peer information. Use <Op>to_udp</Op>
+to send one UDP datagram per event directly from structured data.
 
 ### Receive syslog messages over UDP
 
@@ -29,6 +29,5 @@ this = data.parse_syslog()
 
 ```tql
 from {message: "Tenzir"}
-write_ndjson
-save_udp "1.2.3.4:8080"
+to_udp "1.2.3.4:8080", message=message
 ```

src/content/docs/reference/operators.mdx

@@ -451,10 +451,6 @@ operators:
     description: 'Loads bytes from a TCP or TLS connection.'
     example: 'load_tcp "0.0.0.0:8090" { read_json }'
     path: 'reference/operators/load_tcp'
-  - name: 'load_udp'
-    description: 'Loads bytes from a UDP socket.'
-    example: 'load_udp "0.0.0.0:8090"'
-    path: 'reference/operators/load_udp'
   - name: 'load_zmq'
     description: 'Receives ZeroMQ messages.'
     example: 'load_zmq'
@@ -691,10 +687,10 @@ operators:
     description: 'Saves bytes to a TCP or TLS connection.'
     example: 'save_tcp "0.0.0.0:8090", tls=true'
     path: 'reference/operators/save_tcp'
-  - name: 'save_udp'
-    description: 'Saves bytes to a UDP socket.'
-    example: 'save_udp "0.0.0.0:8090"'
-    path: 'reference/operators/save_udp'
+  - name: 'to_udp'
+    description: 'Sends one UDP datagram per input event.'
+    example: 'to_udp "127.0.0.1:514"'
+    path: 'reference/operators/to_udp'
   - name: 'save_zmq'
     description: 'Sends bytes as ZeroMQ messages.'
     example: 'save_zmq'
@@ -2134,14 +2130,6 @@ load_tcp "0.0.0.0:8090" { read_json }
 
 </ReferenceCard>
 
-<ReferenceCard title="load_udp" description="Loads bytes from a UDP socket." href="/reference/operators/load_udp">
-
-```tql
-load_udp "0.0.0.0:8090"
-```
-
-</ReferenceCard>
-
 <ReferenceCard title="load_zmq" description="Receives ZeroMQ messages." href="/reference/operators/load_zmq">
 
 ```tql
@@ -2490,10 +2478,10 @@ save_tcp "0.0.0.0:8090", tls=true
 
 </ReferenceCard>
 
-<ReferenceCard title="save_udp" description="Saves bytes to a UDP socket." href="/reference/operators/save_udp">
+<ReferenceCard title="to_udp" description="Sends one UDP datagram per input event." href="/reference/operators/to_udp">
 
 ```tql
-save_udp "0.0.0.0:8090"
+to_udp "127.0.0.1:514"
 ```
 
 </ReferenceCard>

src/content/docs/reference/operators/from.mdx

@@ -150,7 +150,6 @@ load_tcp "tcp://0.0.0.0:12345", parallel=10 {
 | `s3`            | <Op>load_s3</Op>                 | `from "s3://bucket/file.json"`                  |
 | `sqs`           | <Op>load_sqs</Op>                | `from "sqs://my-queue" { read_json }`           |
 | `tcp`           | <Op>load_tcp</Op>                | `from "tcp://127.0.0.1:13245" { read_json }`    |
-| `udp`           | <Op>load_udp</Op>                | `from "udp://127.0.0.1:56789" { read_json }`    |
 | `zmq`           | <Op>load_zmq</Op>                | `from "zmq://127.0.0.1:56789" { read_json }`    |
 
 Please see the respective operator pages for details on the URI's locator format.

src/content/docs/reference/operators/from_udp.mdx

@@ -15,7 +15,6 @@ from_udp endpoint:string, [resolve_hostnames=bool], [binary=bool]
 Listens for UDP datagrams on the specified endpoint and outputs each datagram as
 a structured event containing the data and peer information.
 
-Unlike <Op>load_udp</Op>, which outputs raw bytes,
 `from_udp` produces structured events with metadata about the sender.
 
 ### `endpoint: string`
@@ -91,6 +90,5 @@ select data
 
 ## See Also
 
-- <Op>load_udp</Op>
-- <Op>save_udp</Op>
+- <Op>to_udp</Op>
 - <Integration>udp</Integration>

src/content/docs/reference/operators/to.mdx

@@ -97,7 +97,6 @@ If no scheme is present, the connector attempts to save to the local filesystem.
 | `s3`                               | <Op>save_s3</Op>                 | `to "s3://bucket/file.json"`                   |
 | `sqs`                              | <Op>save_sqs</Op>                | `to "sqs://my-queue" { write_json }`           |
 | `tcp`                              | <Op>save_tcp</Op>                | `to "tcp://127.0.0.1:56789" { write_json }`    |
-| `udp`                              | <Op>save_udp</Op>                | `to "udp://127.0.0.1:56789" { write_json }`    |
 | `zmq`                              | <Op>save_zmq</Op>                | `to "zmq://127.0.0.1:56789" { write_json }`    |
 | `smtp`, `smtps`, `mailto`, `email` | <Op>save_email</Op>              | `to "smtp://john@example.com"`                 |
 

src/content/docs/reference/operators/to_udp.mdx

@@ -0,0 +1,58 @@
+---
+title: to_udp
+category: Outputs/Events
+example: 'to_udp "127.0.0.1:514"'
+---
+
+import Integration from '@components/see-also/Integration.astro';
+import Op from '@components/see-also/Op.astro';
+
+Sends one UDP datagram per input event.
+
+```tql
+to_udp endpoint:string, [message=string|blob|record]
+```
+
+## Description
+
+Sends one UDP datagram per input event to a fixed remote UDP endpoint.
+
+### `endpoint: string`
+
+The address of the remote endpoint. Must be of the format `host:port`. The
+optional `udp://` prefix is accepted but not required.
+
+### `message = string|blob|record (optional)`
+
+An expression that is evaluated once per input event and must produce one of
+the following types:
+
+- `string` values are sent as UTF-8 bytes.
+- `blob` values are sent verbatim.
+- `record` values are serialized as compact JSON.
+- `null` values are skipped with a warning.
+
+All other result types are ignored with a warning.
+
+If you omit `message`, the operator sends the whole event as compact JSON.
+
+## Examples
+
+Send a field as a UDP datagram:
+
+```tql
+from {message: "hello"}
+to_udp "127.0.0.1:514", message=message
+```
+
+Send the full event as compact JSON:
+
+```tql
+from {service: "dns", status: "ok"}
+to_udp "127.0.0.1:514"
+```
+
+## See Also
+
+- <Op>from_udp</Op>
+- <Integration>udp</Integration>