Skip to content

Commit 205fe48

Browse files
service-repl: example of mulog event message
1 parent 8d96556 commit 205fe48

File tree

1 file changed

+9
-2
lines changed

1 file changed

+9
-2
lines changed

docs/service-repl-workflow/mulog-events.md

Lines changed: 9 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -6,6 +6,15 @@ Creating a custom publisher, all mulog events can be sent to portal data inspect
66

77
![Portal - mulog event messages tap>](https://github.com/practicalli/graphic-design/blob/live/portal/portal-mulog-tap-publisher-repl-startup-dark.png?raw=true){loading=lazy}
88

9+
## Mulog event
10+
11+
`mulog/log` function is used to define an event message. The first argument is a unique event name, followed by key/value pairs that define the contents of the message.
12+
13+
!!! EXAMPLE "Simple Mulog Event"
14+
```clojure
15+
mulog/log ::dev-user-ns :message "Example event message" :ns (ns-publics *ns*))
16+
```
17+
918

1019
## Mulog configuration
1120

@@ -71,8 +80,6 @@ Creating a custom publisher, all mulog events can be sent to portal data inspect
7180
[]
7281
tap-publisher)
7382

74-
;; Example mulog event message
75-
;; (mulog/log ::dev-user-ns :message "Example event message" :ns (ns-publics *ns*))
7683
;; ---------------------------------------------------------
7784
```
7885

0 commit comments

Comments
 (0)