@@ -12,31 +12,16 @@ feedback should be directed to the RabbitMQ mailing list [1] instead.
12
12
In order for the RabbitMQ team to investigate your issue, please provide
13
13
** as much as possible** of the following details:
14
14
15
- * RabbitMQ version
16
- * Erlang version
17
- * RabbitMQ server and client application log files
18
- * A runnable code sample, terminal transcript or detailed set of
19
- instructions that can be used to reproduce the issue
20
- * RabbitMQ plugin information via ` rabbitmq-plugins list `
21
- * Client library version (for all libraries used)
15
+ * Cookbook version used
22
16
* Operating system, version, and patch level
23
-
24
- Running the ` rabbitmq-collect-env ` [ 2] script can provide most of the
25
- information needed. Please make the archive available via a third-party
26
- service and note that ** the script does not attempt to scrub any
27
- sensitive data** .
28
-
29
- If your issue involves RabbitMQ management UI or HTTP API, please also provide
30
- the following:
31
-
32
- * Browser and its version
33
- * What management UI page was used (if applicable)
34
- * How the HTTP API requests performed can be reproduced with ` curl `
35
- * Operating system on which you are running your browser, and its version
36
- * Errors reported in the JavaScript console (if any)
17
+ * Node attributes
18
+ * RabbitMQ version provisioned
19
+ * Erlang version provisioned
20
+ * RabbitMQ server and client application log files
21
+ * Brief instructions that can be used to reproduce the issue e.g. with Vagrant and ` chef-solo `
37
22
38
23
This information ** greatly speeds up issue investigation** (or makes it
39
- possible to investigate it at all). Please help project maintainers and
24
+ possible to investigate it at all). Please help project maintainers and
40
25
contributors to help you by providing it!
41
26
42
27
1 . https://groups.google.com/forum/#!forum/rabbitmq-users
0 commit comments