This plugin provides native RabbitMQ instrumentation for monitoring and metrics collection, including: service health, message, consumer, and queue health/metrics via `rabbitmq_management`, and more.
Updates the requirements on bunny to permit the latest version.
Changelog
*Sourced from [bunny's changelog](https://github.com/ruby-amqp/bunny/blob/master/ChangeLog.md).*
> ## Changes between Bunny 2.12.0 and 2.13.0 (unreleased)
>
> No changes yet.
>
>
> ## Changes between Bunny 2.11.0 and 2.12.0 (Sep 22nd, 2018)
>
> ### More Defensive Treatment of `queue.declare-ok` Responses
>
> Responses for `queue.declare` are now checked against a memoized
> queue name (but only if the queue is not server-named). This helps
> avoids scenarios with overlapping/concurrent requests due to high
> network latency as demonstrated in [#558](https://github-redirect.dependabot.com/ruby-amqp/bunny/issues/558).
>
> "Mismatched" responses will be ignored: Bunny channel API would throw
> an exception for such declarations and there would be no way to "return to"
> even if a matching response arrived and was matched with one of the pending
> requests in a reasonable period of time.
>
> As part of this work a new Toxiproxy-based test suite was introduced
> to Bunny.
>
> GitHub issue: [#558](https://github-redirect.dependabot.com/ruby-amqp/bunny/issues/558)
>
> Reproduction steps contributed by Brian Morton and Scott Bonebraker.
>
> ### I/O Exceptions from Heartbeat Sender are Now Silent
>
> Heartbeat sender's purpose is to notify the peer, not so much
> to detect local connectivity failures; those will be detected
> by the I/O loop and transport.
>
> For single threaded connection users that prefer to roll their own
> recovery strategies getting exceptions from the heartbeat sender
> was counterproductive and painful to deal with.
>
> As part of this work a new Toxiproxy-based test suite was introduced
> to Bunny.
>
> GitHub issue: [#559](https://github-redirect.dependabot.com/ruby-amqp/bunny/issues/559)
>
> Contributed by Scott Bonebraker.
>
> ### Correct Connection State on Connections that Experienced Missed Heartbeat
>
> Connections that experienced connection closure did not always correctly transition to the closed state.
> `Bunny::ConnectionClosedError` will now be thrown when an operation is attempted on such
> connections.
>
> GitHub issue: [#561](https://github-redirect.dependabot.com/ruby-amqp/bunny/issues/561)
> ... (truncated)
Commits
- See full diff in [compare view](https://github.com/ruby-amqp/bunny/commits/2.6.4)
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.
Note: This repo was added to Dependabot recently, so you'll receive a maximum of 5 PRs for your first few update runs. Once an update run creates fewer than 5 PRs we'll remove that limit.
You can always request more updates by clicking Bump now in your Dependabot dashboard.
Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
- `@dependabot rebase` will rebase this PR
- `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it
- `@dependabot merge` will merge this PR after your CI passes on it
- `@dependabot cancel merge` will cancel a previously requested merge
- `@dependabot reopen` will reopen this PR if it is closed
- `@dependabot ignore this [patch|minor|major] version` will close this PR and stop Dependabot creating any more for this minor/major version (unless you reopen the PR or upgrade to it yourself)
- `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
- `@dependabot use these labels` will set the current labels as the default for future PRs for this repo and language
- `@dependabot use these reviewers` will set the current reviewers as the default for future PRs for this repo and language
- `@dependabot use these assignees` will set the current assignees as the default for future PRs for this repo and language
- `@dependabot use this milestone` will set the current milestone as the default for future PRs for this repo and language
- `@dependabot badge me` will comment on this PR with code to add a "Dependabot enabled" badge to your readme
Additionally, you can set the following in your Dependabot [dashboard](https://app.dependabot.com):
- Update frequency (including time of day and day of week)
- Automerge options (never/patch/minor, and dev/runtime dependencies)
- Pull request limits (per update run and/or open at any time)
- Out-of-range updates (receive only lockfile updates, if desired)
- Security updates (receive only security updates, if desired)
Finally, you can contact us by mentioning @dependabot.
Updates the requirements on bunny to permit the latest version.
Changelog
*Sourced from [bunny's changelog](https://github.com/ruby-amqp/bunny/blob/master/ChangeLog.md).* > ## Changes between Bunny 2.12.0 and 2.13.0 (unreleased) > > No changes yet. > > > ## Changes between Bunny 2.11.0 and 2.12.0 (Sep 22nd, 2018) > > ### More Defensive Treatment of `queue.declare-ok` Responses > > Responses for `queue.declare` are now checked against a memoized > queue name (but only if the queue is not server-named). This helps > avoids scenarios with overlapping/concurrent requests due to high > network latency as demonstrated in [#558](https://github-redirect.dependabot.com/ruby-amqp/bunny/issues/558). > > "Mismatched" responses will be ignored: Bunny channel API would throw > an exception for such declarations and there would be no way to "return to" > even if a matching response arrived and was matched with one of the pending > requests in a reasonable period of time. > > As part of this work a new Toxiproxy-based test suite was introduced > to Bunny. > > GitHub issue: [#558](https://github-redirect.dependabot.com/ruby-amqp/bunny/issues/558) > > Reproduction steps contributed by Brian Morton and Scott Bonebraker. > > ### I/O Exceptions from Heartbeat Sender are Now Silent > > Heartbeat sender's purpose is to notify the peer, not so much > to detect local connectivity failures; those will be detected > by the I/O loop and transport. > > For single threaded connection users that prefer to roll their own > recovery strategies getting exceptions from the heartbeat sender > was counterproductive and painful to deal with. > > As part of this work a new Toxiproxy-based test suite was introduced > to Bunny. > > GitHub issue: [#559](https://github-redirect.dependabot.com/ruby-amqp/bunny/issues/559) > > Contributed by Scott Bonebraker. > > ### Correct Connection State on Connections that Experienced Missed Heartbeat > > Connections that experienced connection closure did not always correctly transition to the closed state. > `Bunny::ConnectionClosedError` will now be thrown when an operation is attempted on such > connections. > > GitHub issue: [#561](https://github-redirect.dependabot.com/ruby-amqp/bunny/issues/561) > ... (truncated)Commits
- See full diff in [compare view](https://github.com/ruby-amqp/bunny/commits/2.6.4)Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Note: This repo was added to Dependabot recently, so you'll receive a maximum of 5 PRs for your first few update runs. Once an update run creates fewer than 5 PRs we'll remove that limit.
You can always request more updates by clicking
Bump nowin your Dependabot dashboard.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot ignore this [patch|minor|major] version` will close this PR and stop Dependabot creating any more for this minor/major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) - `@dependabot use these labels` will set the current labels as the default for future PRs for this repo and language - `@dependabot use these reviewers` will set the current reviewers as the default for future PRs for this repo and language - `@dependabot use these assignees` will set the current assignees as the default for future PRs for this repo and language - `@dependabot use this milestone` will set the current milestone as the default for future PRs for this repo and language - `@dependabot badge me` will comment on this PR with code to add a "Dependabot enabled" badge to your readme Additionally, you can set the following in your Dependabot [dashboard](https://app.dependabot.com): - Update frequency (including time of day and day of week) - Automerge options (never/patch/minor, and dev/runtime dependencies) - Pull request limits (per update run and/or open at any time) - Out-of-range updates (receive only lockfile updates, if desired) - Security updates (receive only security updates, if desired) Finally, you can contact us by mentioning @dependabot.