You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+21Lines changed: 21 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -106,6 +106,27 @@ fields can be accessed in the `resources` field of the structure.
106
106
}
107
107
```
108
108
109
+
### Telemetry Integration
110
+
111
+
Chargebeex now supports `:telemetry`, allowing users to instrument and monitor API calls using telemetry events. This enables integration with various observability tools.
112
+
113
+
#### Telemetry Events
114
+
115
+
Chargebeex emits the following telemetry events for each API request:
116
+
117
+
-`[:chargebeex, :request, :start]`: Emitted when an API request starts.
118
+
-`[:chargebeex, :request, :stop]`: Emitted when an API request completes.
119
+
120
+
When making API calls, telemetry events will automatically be emitted:
121
+
122
+
```elixir
123
+
Chargebeex.Client.get("/customers")
124
+
```
125
+
126
+
This will emit :start and :stop telemetry events with metadata such as the HTTP method, URL, and status code, which can be processed by your telemetry handler.
127
+
128
+
For more information on `:telemetry`, visit the [official documentation](https://hexdocs.pm/telemetry/).
0 commit comments