Skip to content

Commit

Permalink
Add a note about configuring Yabeda in non-Rails apps (#20)
Browse files Browse the repository at this point in the history
For saving time of other developers

Co-authored-by: Andrey Novikov <[email protected]>
  • Loading branch information
buzjuka and Envek authored Oct 24, 2022
1 parent f2190ae commit ffdaf0d
Showing 1 changed file with 11 additions and 0 deletions.
11 changes: 11 additions & 0 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -43,6 +43,17 @@ plugin :yabeda
```
It will activate default puma control application working over the unix socket, and runs the `yabeda` puma plugin, for registering and collecting the metrics.

> **Note**
>
> In case if you're **not** using Rails, don't forget configure Yabeda manually either in your app initialization or in Puma configuration hook:
> ```ruby
> # config/puma.rb
> before_fork do
> Yabeda.configure!
> end
> ```
> See [yabeda usage](https://github.com/yabeda-rb/yabeda#usage) for more information.
### Exposing metrics
Some monitoring system agents (like NewRelic or DataDog) will send metrics automatically in the background. But for some of monitoring systems (like Prometheus) you have to explicitly set up metrics export.
Expand Down

0 comments on commit ffdaf0d

Please sign in to comment.