Use the documentation IP address range

elastic · Jan 3, 2020 · fe43b29 · fe43b29
1 parent b8c0f6f
commit fe43b29
Show file tree

Hide file tree

Showing 5 changed files with 5 additions and 5 deletions.
diff --git a/code/go/ecs/related.go b/code/go/ecs/related.go
diff --git a/docs/field-details.asciidoc b/docs/field-details.asciidoc
@@ -3632,7 +3632,7 @@ This field set is meant to facilitate pivoting around a piece of data.
 
 Some pieces of information can be seen in many places in an ECS event. To facilitate searching for them, store an array of all seen values to their corresponding field in `related.`.
 
-A concrete example is IP addresses, which can be under host, observer, source, destination, client, server, and network.forwarded_ip. If you append all IPs to `related.ip`, you can then search for a given IP trivially, no matter where it appeared, by querying `related.ip:192.168.1.15`.
+A concrete example is IP addresses, which can be under host, observer, source, destination, client, server, and network.forwarded_ip. If you append all IPs to `related.ip`, you can then search for a given IP trivially, no matter where it appeared, by querying `related.ip:192.0.2.15`.
 
 ==== Related Field Details
 

diff --git a/generated/beats/fields.ecs.yml b/generated/beats/fields.ecs.yml
@@ -2705,7 +2705,7 @@
       A concrete example is IP addresses, which can be under host, observer, source,
       destination, client, server, and network.forwarded_ip. If you append all IPs
       to `related.ip`, you can then search for a given IP trivially, no matter where
-      it appeared, by querying `related.ip:192.168.1.15`.'
+      it appeared, by querying `related.ip:192.0.2.15`.'
     type: group
     fields:
     - name: hash

diff --git a/generated/ecs/ecs_nested.yml b/generated/ecs/ecs_nested.yml
@@ -4789,7 +4789,7 @@ related:
     A concrete example is IP addresses, which can be under host, observer, source,
     destination, client, server, and network.forwarded_ip. If you append all IPs to
     `related.ip`, you can then search for a given IP trivially, no matter where it
-    appeared, by querying `related.ip:192.168.1.15`.'
+    appeared, by querying `related.ip:192.0.2.15`.'
   fields:
     hash:
       dashed_name: related-hash

diff --git a/schemas/related.yml b/schemas/related.yml
@@ -13,7 +13,7 @@
     A concrete example is IP addresses, which can be under host, observer, source,
     destination, client, server, and network.forwarded_ip.
     If you append all IPs to `related.ip`, you can then search for a given IP trivially,
-    no matter where it appeared, by querying `related.ip:192.168.1.15`.
+    no matter where it appeared, by querying `related.ip:192.0.2.15`.
   type: group
   fields: