Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

making the describe task queue command more descriptive #672

Closed
wants to merge 2 commits into from

Conversation

Shivs11
Copy link
Member

@Shivs11 Shivs11 commented Sep 16, 2024

What was changed

  • addressed comments by adding more description to the task-queue describe command

Why?

  • better readability

Checklist

  1. Closes

  2. How was this tested:

  1. Any docs updates needed?

increasing (if positive) or decreasing (if negative), measured in tasks per
second, averaged over the last 30 seconds. This is equivalent to:
`TasksAddRate` - `TasksDispatchRate`.

NOTE: The `TasksAddRate` and `TasksDispatchRate` metrics may differ from the
actual rate of add/dispatch, because tasks may be dispatched eagerly to an
available worker, or may apply only to specific workers (they are "sticky").
Such tasks are not counted by these metrics.
Such tasks are not counted by these metrics. Despite the inaccuracy of
these two metrics, the derived metric of BacklogIncreaseRate is accurate
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

to be consistent.

Suggested change
these two metrics, the derived metric of BacklogIncreaseRate is accurate
these two metrics, the derived metric of `BacklogIncreaseRate` is accurate

Such tasks are not counted by these metrics.
Such tasks are not counted by these metrics. Despite the inaccuracy of
these two metrics, the derived metric of BacklogIncreaseRate is accurate
for backlogs older than few seconds.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Idiomatic/native English:

Suggested change
for backlogs older than few seconds.
for backlogs older than a few seconds.

Shivs11 added a commit that referenced this pull request Oct 2, 2024
<!--- Note to EXTERNAL Contributors -->
<!-- Thanks for opening a PR! 
If it is a significant code change, please **make sure there is an open
issue** for this.
We work best with you when we have accepted the idea first before you
code. -->

<!--- For ALL Contributors 👇 -->

## What was changed
<!-- Describe what has changed in this PR -->
- addressed minor comments which were requested in #672 

## Why?
<!-- Tell your future self why have you made these changes -->
- opened a new PR since the repo went through some changes with respect
to generating code (now uses a .yml file)
- attempted at resolving conflicts on the previous open PR but was faced
with unknown issues
- thought it was best, in the interest of time and given the relatively
small size of the PR, to open a new branch and close the issue.

## Checklist
<!--- add/delete as needed --->

1. Closes <!-- add issue number here -->

2. How was this tested:
<!--- Please describe how you tested your changes/how we can test them
-->

3. Any docs updates needed?
<!--- update README if applicable
      or point out where to update docs.temporal.io -->
@Shivs11
Copy link
Member Author

Shivs11 commented Oct 2, 2024

closing this as an updated PR was merged to main.

@Shivs11 Shivs11 closed this Oct 2, 2024
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.

4 participants