Skip to content

Calculate uplink rate metrics#190

Closed
jekka001 wants to merge 4 commits into
thingsboard:rcfrom
jekka001:uplink-rate-metrics
Closed

Calculate uplink rate metrics#190
jekka001 wants to merge 4 commits into
thingsboard:rcfrom
jekka001:uplink-rate-metrics

Conversation

@jekka001
Copy link
Copy Markdown
Contributor

@jekka001 jekka001 commented Aug 11, 2025

Pull Request description

Implemented collection and calculation of uplink message sending rate metrics between Edge and Cloud.
Added logic to compute average uplink rate in kilobytes per second based on message size and transfer time.

General checklist

  • You have reviewed the guidelines document.
  • Labels that classify your pull request have been added.
  • The milestone is specified and corresponds to fix version.
  • Description references specific issue.
  • Description contains human-readable scope of changes.
  • Description contains brief notes about what needs to be added to the documentation.
  • No merge conflicts, commented blocks of code, code formatting issues.
  • Changes are backward compatible or upgrade script is provided.
  • Similar PR is opened for PE version to simplify merge. Crosslinks between PRs added. Required for internal contributors only.

Back-End feature checklist

  • Added corresponding unit and/or integration test(s). Provide written explanation in the PR description if you have failed to add tests.
  • If new dependency was added: the dependency tree is checked for conflicts.
  • If new service was added: the service is marked with corresponding @TbCoreComponent, @TbRuleEngineComponent, @TbTransportComponent, etc.
  • If new REST API was added: the RestClient.java was updated, issue for Python REST client is created.
  • If new yml property was added: make sure a description is added (above or near the property).

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants