Skip to content

Document ASB QueueLengthQueryDelayInterval as a monitoring-only setting#8405

Open
ramonsmits wants to merge 2 commits into
masterfrom
docs-asb-queuelength-monitoring-section
Open

Document ASB QueueLengthQueryDelayInterval as a monitoring-only setting#8405
ramonsmits wants to merge 2 commits into
masterfrom
docs-asb-queuelength-monitoring-section

Conversation

@ramonsmits

Copy link
Copy Markdown
Member

The QueueLengthQueryDelayInterval connection string option was buried in the ASB topic-per-event topology section. It only affects the Monitoring instance, so it now has its own "Queue length monitoring" section noting the value can be increased if rate throttling is observed.

@johnsimons johnsimons left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

It LGTM but I asked a couple of questions to check

Comment thread servicecontrol/transports.md Outdated
> [!NOTE]
> This setting applies only to the [Monitoring instance](/servicecontrol/monitoring-instances/), which is the only instance type that tracks queue lengths.

The Monitoring instance periodically queries the Azure Service Bus namespace to refresh the queue length data behind the throughput graphs:

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Maybe consider adding a link to the graphs you referring to

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

Added it in 4329d0d

Comment thread servicecontrol/transports.md
Addresses review feedback: point to the metric the Monitoring instance's
queue length queries feed, and correct "throughput graphs" to the queue
length metric.
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