-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Add prometheus metrics to subsonic and plugins #4266
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.
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
Add prometheus metrics to subsonic and plugins #4266
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Summary of Changes
Hello @kgarner7, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!
This pull request significantly enhances the observability of the application by integrating comprehensive Prometheus metrics for both the Subsonic API and plugin interactions. The core change involves refactoring the Prometheus instance into a singleton, which streamlines its usage throughout the codebase and enables detailed performance and usage monitoring.
Highlights
- New Prometheus Metrics for Subsonic API: I've introduced new Prometheus metrics to track Subsonic API requests. These include method counts by endpoint, HTTP method, and HTTP status code, as well as latency measurements (50th, 90th, and 99th percentiles, plus total elapsed time) for these requests.
- New Prometheus Metrics for Plugins: Similarly, I've added Prometheus metrics for plugin calls. These metrics capture call counts by plugin name, method, and whether the response was successful. Latency calculations (50th, 90th, and 99th percentiles, and total elapsed time) are also included for plugin interactions.
- Prometheus Instance Refactor to Singleton: The Prometheus metrics instance has been refactored to be a singleton. This change simplifies its management and passing across different parts of the application, making it more accessible for various components to record metrics.
- DataStore Dependency for Scan Metrics: As a consequence of the Prometheus singleton refactor, the
DataStore
is now explicitly passed as an argument to functions that write scan-related metrics (e.g.,WriteInitialMetrics
,WriteAfterScanMetrics
), rather than being held directly by the metrics instance.
Using Gemini Code Assist
The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.
Invoking Gemini
You can request assistance from Gemini at any point in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command>
or @gemini-code-assist <command>
. Below is a summary of the supported commands.
Feature | Command | Description |
---|---|---|
Code Review | /gemini review |
Performs a code review for the current pull request in its current state. |
Pull Request Summary | /gemini summary |
Provides a summary of the current pull request in its current state. |
Comment | @gemini-code-assist | Responds in comments when explicitly tagged, both in issue comments and review comments. |
Help | /gemini help |
Displays a list of available commands. |
Customization
To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/
folder in the base of the repository. Detailed instructions can be found here.
Limitations & Feedback
Gemini Code Assist is currently in preview and may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments to provide feedback.
You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.
Footnotes
-
Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Code Review
This pull request introduces Prometheus metrics for Subsonic API endpoints and for plugin calls, which is a great addition for observability. The implementation is mostly solid, using a singleton for the Prometheus instance and a middleware for capturing HTTP metrics.
I've identified a couple of areas for improvement:
- A bug in the plugin metric recording logic due to a shadowed variable.
- An opportunity to refactor repetitive code in metric registration for better maintainability.
- A minor naming issue for clarity.
Sample data collected (example using my listenbrainz plugin):
|
Updated example, with openmetrics:
(The tiemstamp indicates metric creation time) |
…n every call Signed-off-by: Deluan <deluan@navidrome.org>
This exposes the following metrics:
Note that prometheus is now a singleton, so that it can be passed around much easier to plugins.
Consequently, the scan metrics require passing in the database now.
I'd like to also support native API, but that's trickier as there are URL fragments.