docs(amqp): cover usage examples of amqp and slack integration

Includes:
- What openQA publishes
- shortly describes slacky integration
- real event body as examples

Anything else seems is provided by linked references, so no need
to be verbose.

Issue: https://progress.opensuse.org/issues/190737
Signed-off-by: Ioannis Bonatakis <ybonatakis@suse.com>

Author: d3flex

docs/Installing.asciidoc

@@ -1100,6 +1100,56 @@ topic_prefix = suse
 
 For a TLS connection use `amqps://` and port `5671`.
 
+The message topic follows the format `SCOPE.APPLICATION.OBJECT.ACTION`, for
+example `opensuse.openqa.job.done` or `opensuse.openqa.comment.create`.
+The `topic_prefix` setting controls the `SCOPE` part; if left empty the topic
+starts with `openqa.` directly.
+Consumers can use `#` to match any number of words or `*` to match exactly one
+word. `suse.openqa.#` subscribe to all openQA events, for instance.
+
+Here is what events are triggerred and published by openQA per Topic:
+
+1. `openqa.job.create` when A job is created
+2. `openqa.job.delete` when A job is deleted
+3. `openqa.job.cancel` when A job is cancelled
+4. `openqa.job.restart` when A job is restarted or duplicated
+5. `openqa.job.update_result` when A job result is updated
+6. `openqa.job.done` when A job finishes
+
+Job event bodies include the job settings (e.g. `BUILD`, `TEST`, `ARCH`,
+`MACHINE`, `FLAVOR`, asset fields like `ISO` or `HDD_1`) plus `id`, `group_id`,
+and `remaining` (number of pending jobs for the same build). Finished jobs
+additionally include `result`, `reason`, `newbuild`, `failedmodules`, `bugref`,
+and `bugurl` (only present when a bug reference exists).
+
+Example (at the time of writing) `suse.openqa.job.done` message body:
+
+[source,json]
+--------------------------------------------------------------------------------
+ {"ARCH":"x86_64","BUILD":"N.487.1","FLAVOR":"Staging-DVD","ISO":"openSUSE-Staging:N-Tumbleweed-DVD-x86_64-Build487.1-Media.iso","MACHINE":"64bit","TEST":"autoyast_mini","bugref":null,"failedmodules":[],"group_id":2,"id":5735489,"newbuild":null,"reason":null,"remaining":13,"result":"passed"}
+--------------------------------------------------------------------------------
+
+comments which are also published and are self-explanatory too:
+
+1. `openqa.comment.create`
+2. `openqa.comment.update`
+3. `openqa.comment.delete`
+
+Comment event bodies include: `id`, `job_id`, `group_id`, `parent_group_id`,
+`user`, `text`, `created`, `updated`.
+
+Example `suse.openqa.comment.create` message body:
+
+[source,json]
+--------------------------------------------------------------------------------
+{"created":"2026-03-11T14:35:23Z","group_id":null,"id":865726,"job_id":5735489,"parent_group_id":null,"text":"amqp sent","updated":"2026-03-11T14:35:23Z","user":"demo"}
+--------------------------------------------------------------------------------
+
+A real-world example of an AMQP consumer built on top of openQA events is
+https://github.com/dirkmueller/slacky[slacky], a bot that monitors CI/build
+pipelines and posts failure notifications to Slack. It subscribes to openQA job
+events and tracks job results per build group.
+
 
 === Configuring worker to use more than one openQA server