Skip to content

Add time_frame to metrics guide

Alina Mihaila requested to merge am-add-time-frame-details-to-metrics-guide into master

What does this MR do?

Add time frame section to metric guide

### Metric time_frame

- `7d`: Data corresponds to recent 7 days. Example number of users creating epics in the last 7 days `ee/config/metrics/counts_28d/20210305144719_g_product_planning_epic_created_monthly.yml`.
- `28d`: Data corresponds to recent 28 days. Example number of unique users creating isssues in last 28 days `config/metrics/counts_28d/20210216181139_issues.yml`.
- `all`: Data corresponds to all-time interval. Example number of users creating issues `/config/metrics/counts_all/20210216181115_issues.yml`.
- `none`: No time interval applicable, used for settings and configurations. Example `uuid` has no time interval applicable `config/metrics/license/20210201124933_uuid.yml`.

Screenshots (strongly suggested)

Does this MR meet the acceptance criteria?

Conformity

Availability and Testing

Security

Does this MR contain changes to processing or storing of credentials or tokens, authorization and authentication methods or other items described in the security review guidelines? If not, then delete this Security section.

  • Label as security and @ mention @gitlab-com/gl-security/appsec
  • The MR includes necessary changes to maintain consistency between UI, API, email, or other methods
  • Security reports checked/validated by a reviewer from the AppSec team

Merge request reports