feedback

Author: aslamovamir

content/vault/v1.18.x/content/api-docs/system/internal-counters.mdx

@@ -366,9 +366,15 @@ is unknown.
 
 ### Parameters
 
-- `start_time` `(string, optional)` - An RFC3339 timestamp or Unix epoch time. Specifies the start of the
-  period for which client counts will be reported. If no start time is specified, the billing start date will be used.
-  The [billing start date](/vault/docs/concepts/billing-start-date) automatically rolls over to the latest billing year at the end of the last cycle.
+- `start_time` `(string, optional)` - An RFC3339 timestamp or Unix epoch time.
+  Specifies the start of the period for which client counts will be reported.
+  Vault uses the [billing start date](/vault/docs/concepts/billing-start-date)
+  by default, which automatically rolls over to the latest billing year at the
+  end of the last cycle. Vault Community **requires** `start_time`, but Vault
+  Enterprise uses the billing start date as defined by the cluster license by
+  default. Vault Community does not have a billing start time, so ommitting
+  `start_time` can lead to undefined behavior. We recommend setting an explicit
+  start time to ensure reliable behavior in all Vault versions.
 
 
 - `end_time` `(string, optional)` - An RFC3339 timestamp or Unix epoch time. Specifies the end of the period

content/vault/v1.19.x/content/api-docs/system/internal-counters.mdx

@@ -366,18 +366,27 @@ is unknown.
 
 ### Parameters
 
-- `start_time` `(string, optional)` - An RFC3339 timestamp or Unix epoch time. Specifies the start of the
-  period for which client counts will be reported. If no start time is specified, the billing start date will be used.
-  The [billing start date](/vault/docs/concepts/billing-start-date) automatically rolls over to the latest billing year at the end of the last cycle.
-- `end_time` `(string, optional)` - An RFC3339 timestamp or Unix epoch time. Specifies the end of the period
-  for which client counts will be reported. If no end time is specified, the end of the current month will be used.
-- `limit_namespaces` `(int, optional)` - Controls the total number of by_namespace data returned. This can
-   be used to return the client counts for the specified number of namespaces having highest activity.
-   If no `limit_namespaces` parameter is specified, client counts for all namespaces in specified usage period is returned.
-- `current_billing_period` `(bool, optional)` - **DEPRECATED** Uses the builtin billing start
-  timestamp as `start_time` and the current time as the `end_time`, returning a
+- `start_time` `(string, optional)` - An RFC3339 timestamp or Unix epoch time.
+  Specifies the start of the period for which client counts will be reported.
+  Vault uses the [billing start date](/vault/docs/concepts/billing-start-date)
+  by default, which automatically rolls over to the latest billing year at the
+  end of the last cycle. Vault Community **requires** `start_time`, but Vault
+  Enterprise uses the billing start date as defined by the cluster license by
+  default. Vault Community does not have a billing start time, so ommitting
+  `start_time` can lead to undefined behavior. We recommend setting an explicit
+  start time to ensure reliable behavior in all Vault versions.
+- `end_time` `(string, optional)` - An RFC3339 timestamp or Unix epoch time. 
+  Specifies the end of the period for which client counts will be reported. If 
+  no end time is specified, the end of the current month will be used.
+- `limit_namespaces` `(int, optional)` - Controls the total number of by_namespace
+  data returned. This can be used to return the client counts for the specified number
+  of namespaces having highest activity. If no `limit_namespaces` parameter is 
+  specified, client counts for all namespaces in specified usage period is returned.
+- `current_billing_period` `(bool, optional)` - **DEPRECATED** Uses the builtin billing
+  start timestamp as `start_time` and the current time as the `end_time`, returning a
   response with the current billing period information without having to
-  explicitly provide a start and end time. This parameter is deprecated, as this option is now the default, so no parameter is needed to specify.
+  explicitly provide a start and end time. This parameter is deprecated, as this option
+  is now the default, so no parameter is needed to specify.
 
 
 ### Sample request