doc: Rename log messages metric (TheThingsIndustries#373)

htdvisser · web-flow · commit a345ea02d97a · 2021-06-04T10:11:36.000+02:00
diff --git a/doc/content/getting-started/aws/ecs/monitoring/_index.md b/doc/content/getting-started/aws/ecs/monitoring/_index.md
@@ -46,7 +46,8 @@ In addition to the [metrics exported by {{% tts %}}]({{< ref "/reference/telemet
 
 For all services the following metrics are recorded:
 
-- `ttn_lw_log_log_messages_rate` records the rate of log messages by job (service), namespace and level. This can be useful for monitoring warning and error rates.
+- `ttn_lw_log_messages_rate` records the rate of log messages by job (service), namespace and level. This can be useful for monitoring warning and error rates. {{< new-in-version "3.13.1" >}}
+  - Before version 3.13.1 this metric was called `ttn_lw_log_log_messages_rate`.
 - `ttn_lw_events_publishes_rate` records the rate of published events by event name.
 
 For the Gateway Server:
diff --git a/doc/content/reference/telemetry/_index.md b/doc/content/reference/telemetry/_index.md
@@ -26,7 +26,8 @@ Similar metrics exist for gRPC client connections opened by {{% tts %}}, and RPC
 ## General Metrics
 
 - `ttn_lw_license_expiry_seconds` can be used to keep track of license expiry {{< distributions "Enterprise" >}}
-- `ttn_lw_log_log_messages_total` can be used to track the log messages written by different log namespaces at different log levels.
+- `ttn_lw_log_messages_total` can be used to track the log messages written by different log namespaces at different log levels. {{< new-in-version "3.13.1" >}}
+  - Before version 3.13.1 this metric was called `ttn_lw_log_log_messages_total`.
 - `ttn_lw_events_publishes_total` can be used to track the published events by event type.
 - `ttn_lw_events_channel_dropped_total` can be used to watch for dropped events, which typically indicates that a consumer (such as a user's web browser) can't keep up.
 
