Skip to content

[ Tracking Issue ] Observatory -> DevTools Migration #3858

Activity

  1. kenzieschmoll commented on Mar 15, 2022

    @kenzieschmoll
    Member

    Do we have usage metrics from Observatory on any of the missing features so that we can prioritize which ones we work on first? Or decide if any tools should be left out completely if users hardly use them?

  2. bkonyi commented on Mar 15, 2022

    @bkonyi
    ContributorAuthor

    Do we have usage metrics from Observatory on any of the missing features so that we can prioritize which ones we work on first? Or decide if any tools should be left out completely if users hardly use them?

    Unfortunately not. I'm going to go through advanced features with the VM team (maybe some engine folks) to see what they use and would want migrated. There's already some features (e.g., Observatory's heap map) that we won't bother migrating.

    So far I've only created issues for features that are actually useful or extend existing functionality (I'm sure I'll have more filed tomorrow).

  3. added this to the On Deck milestone on Mar 18, 2022
  4. self-assigned this
    on Mar 22, 2022
  5. a-siva commented on Jan 23, 2023

    @a-siva

    In the list of core/advanced functionality being tracked I do not see the issue of general devtools snappiness, do we have an issue tracking that ?

  6. elliette commented on Jul 31, 2024

    @elliette
    Member

    Closing this tracking issue since the migration has been completed.

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

Metadata

Metadata

Assignees

Labels

observatory migrationRelated to the Observatory -> DevTools migration effort

Type

No type

Projects

No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions