Adjust documentation + examples

README.md

@@ -93,28 +93,6 @@ The exporter contains features that are currently experimental and may change wi
 To use these features, either set the `-enable-experimental` flag or add a `enable_experimental` option
 to your configuration file.
 
-### Aggregation by request path
-
-Collecting metrics by the requested resource path has been discussed in #14. Directly
-adding the requested path as a label is problematic since the set of possible values is
-infinitely large. For this reason, you can specify a set of `routes` in your
-configuration file, which is basically a list of regular expressions; if one of these matches
-a request path, the regular expression will be added as a label to the respective metric:
-
-```hcl
-namespace "app-1" {
-  format = "$remote_addr - $remote_user [$time_local] \"$request\" $status $body_bytes_sent \"$http_referer\" \"$http_user_agent\" \"$http_x_forwarded_for\""
-  source_files = [
-    "/var/log/nginx/app1/access.log"
-  ]
-  routes = [
-    "^/users/[0-9]+",
-    "^/profile",
-    "^/news"
-  ]
-}
-```
-
 ### Dynamic re-labeling
 
 Re-labeling lets you add arbitrary fields from the parsed log line as labels to your metrics.
@@ -138,6 +116,28 @@ The `whitelist` property is optional; if set, only the supplied values will be a
 All other values will be subsumed under the `"other"` label value. See #16 for a more detailed
 discussion around the reasoning.
 
+Dynamic relabeling also allows you to aggregate your metrics by request path (which replaces
+the experimental feature originally introduced in #23):
+
+```hcl
+namespace "app-1" {
+  // ...
+
+  relabel "request_uri" {
+    from = "request"
+    split = 2
+
+    match "^/users/[0-9]+" {
+      replacement = "/users/:id"
+    }
+
+    match "^/profile" {
+      replacement = "/profile"
+    }
+  }
+}
+```
+
 Running the collector
 ---------------------
 

example-config.hcl

@@ -32,7 +32,12 @@ namespace "nginx" {
     // whitelist = ["-", "user1", "user2"]
   }
 
-  routes = [
-    "^/users/[0-9]+"
-  ]
+  relabel "request_uri" {
+    from = "request"
+    split = 2
+
+    match "^users/[0-9]+" {
+      replacement = "/users/:id"
+    }
+  }
 }