Skip to content

[HOLD for payment 2024-10-10] Improve the metrics doccumentation #49376

Closed

Description

@mountiny

Coming from this thread

Problem

Various performance metrics are currently sent to Firebase for monitoring and analysis. However, team members struggle to understand, interpret, and utilize the performance data effectively. This difficulty can result in misunderstandings, misinterpretations, and challenges in leveraging metrics to drive performance improvements.

Some examples where it’s not clear what metrics are representing and what is the difference between them:

  • load_search_options and search_filter_options
  • switch_report and open_report

Solution

To resolve this issue, let’s create comprehensive documentation for our performance metrics. The documentation should include:

  1. Metric Definitions and Descriptions: Provide clear definitions and detailed descriptions of each performance metric.
  2. Data Collection Process: Explain how each metric is collected, including the start and end points of the data collection process.
  3. Documentation Maintenance: Outline the steps for updating and maintaining the documentation as new metrics are added or existing metrics are modified.

This documentation will be included in the project’s README to ensure easy access and reference for everyone.

Activity

  1. self-assigned this
    on Sep 18, 2024
  2. melvin-bot commented on Sep 18, 2024

    @melvin-bot

    Current assignee @mountiny is eligible for the AutoAssignerNewDotQuality assigner, not assigning anyone new.

  3. TMisiukiewicz commented on Sep 18, 2024

    @TMisiukiewicz
    Contributor

    Hi, I'm Tomasz from Callstack, I'd like to work on this issue

  4. mountiny commented on Sep 22, 2024

    @mountiny
    ContributorAuthor

    not overdue

  5. added and removed on Sep 22, 2024
  6. TMisiukiewicz commented on Sep 24, 2024

    @TMisiukiewicz
    Contributor

    I have documented all the metrics we send to Firebase. Should we also include descriptions for the metrics collected exclusively by the Performance module (used by react-native-performance, not being sent anywhere)?

  7. mountiny commented on Sep 24, 2024

    @mountiny
    ContributorAuthor

    I think it does not hurt if you document that as well.

  8. TMisiukiewicz commented on Sep 30, 2024

    @TMisiukiewicz
    Contributor

    PR is open ✅

  9. added
    Awaiting PaymentAuto-added when associated PR is deployed to production
    and removed on Oct 3, 2024
  10. changed the title [-]Improve the metrics doccumentation[/-] [+][HOLD for payment 2024-10-10] Improve the metrics doccumentation[/+] on Oct 3, 2024
  11. melvin-bot commented on Oct 3, 2024

    @melvin-bot

    Reviewing label has been removed, please complete the "BugZero Checklist".

  12. melvin-bot commented on Oct 3, 2024

    @melvin-bot

    The solution for this issue has been 🚀 deployed to production 🚀 in version 9.0.43-6 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:

    If no regressions arise, payment will be issued on 2024-10-10. 🎊

    For reference, here are some details about the assignees on this issue:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions