[CHORE] adding metric usage correlation #162
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This pull request introduces significant changes to the
prom-analytics-proxy
project, focusing on adding new metrics usage endpoints, updating database schema and operations, and modifying dependencies.New Endpoints and Routes:
/api/v1/serieUsage/{name}
and/api/v1/metrics
inapi/routes/routes.go
. These endpoints handle the retrieval and pushing of metrics usage data. [1] [2]Database Schema and Operations:
Dependency Updates:
go.mod
to include new dependencies:github.com/perses/metrics-usage
andgithub.com/sirupsen/logrus
. Also, updated the Go version to 1.23.1 and added a toolchain specification. [1] [2] [3]Minor Code Improvements:
internal/db/clickhouse.go
to handle rules usage data.These changes enhance the functionality of the project by adding support for metrics usage tracking and improving database interactions.