Add detailed logging for responses in each handler #110
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.
Description
This pull request introduces detailed logging for each handler. The primary goal is to enhance the observability and traceability of the application's behavior by providing comprehensive logs for each handler's response.
Changes
Logging Enhancements
probe_metrics_list.go
: Importedzap
library and added logging toprobeMetricsListHandler
to log request details including method, status, and latency. [1] [2]probe_metrics_resource.go
: Importedzap
library and added logging toprobeMetricsResourceHandler
to log request details including method, status, and latency. [1] [2]probe_metrics_resourcegraph.go
: Importedzap
library and added logging toprobeMetricsResourceGraphHandler
to log request details including method, status, and latency. [1] [2]probe_metrics_scrape.go
: Importedzap
library and added logging toprobeMetricsScrapeHandler
to log request details including method, status, and latency. [1] [2]probe_metrics_subscription.go
: Importedzap
library and added logging toprobeMetricsSubscriptionHandler
to log request details including method, status, and latency. [1] [2]Benefits
Testing