Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Add link to conditional plug invocation #244

Merged
merged 1 commit into from
Sep 13, 2024
Merged

Add link to conditional plug invocation #244

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 3 additions & 0 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -270,6 +270,9 @@ There are a couple of solutions to this problem:
maintain in order to only execute the `PromEx.Plug` plug when the incoming request fulfills your configured
requirements (see the [PromEx.Plug HexDocs](https://hexdocs.pm/prom_ex/1.1.1/PromEx.Plug.html) for an example).

3. If Unplug doesn't suit your needs, you can invoke `PromEx.Plug`
[conditionally with your own logic](https://hexdocs.pm/plug/1.16.1/Plug.Builder.html#module-conditional-plugs).

## Performance Concerns

You may think to yourself that with all these metrics being collected and scraped, that the performance of your
Expand Down
Loading