Skip to content

telemetry: Request Response telemetry #8461

Closed
#11335
Closed
telemetry: Request Response telemetry#8461
#11335
Assignees
Maddiaa0
Labels
C-p2pComponent: peer to peer

Description

@Maddiaa0
Maddiaa0
opened on Sep 9, 2024

Overview

In order to perform #8458 we will need to collect appropiate telemetry data about the Request Response P2P protocols.

A/C
Be able to collect data that can measure:

  • How often nodes ask for particular resources
  • Track how long Request Response operations take

The purpose of this data is to be able to tune:

  • timeouts
  • How we should perform peer requests (serially based on reputation / in parallel to multiple peers)

Activity

  1. github-project-automation
    added this to A3on Sep 9, 2024
  2. github-project-automation
    moved this to Todo in A3on Sep 9, 2024
  3. Maddiaa0
    changed the title [-]telemetry: Request Response telemetry modules[/-] [+]telemetry: Request Response telemetry[/+] on Sep 9, 2024
  4. Maddiaa0
    removed this from A3on Sep 9, 2024
  5. Maddiaa0
    self-assigned this
    on Sep 9, 2024
  6. Maddiaa0
    added
    C-p2pComponent: peer to peer
    on Oct 2, 2024
  7. github-project-automation
    moved this to Todo in A3on Oct 2, 2024
  8. github-project-automation
    added this to A3on Oct 2, 2024
  9. Maddiaa0
    linked a pull request that will close this issuefeat(p2p): reqresp spans #11335on Jan 19, 2025

  10. Maddiaa0 commented on Feb 9, 2025

    @Maddiaa0
    Maddiaa0
    on Feb 9, 2025
    ContributorAuthor

    closed by #11335

  11. Maddiaa0
    closed this as completedon Feb 9, 2025
  12. github-project-automation
    moved this from Todo to Done in A3on Feb 9, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

C-p2pComponent: peer to peer

Type

No type

Projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions