Files
query-orchestration/deployments/readme.md
T
Jay Brown 477518e5eb Merged in feature/prometheus (pull request #52)
API instrumentation - metrics and logging

* api instrumentation

prometheus metrics and logging for all routes

* Merge branch 'main' of bitbucket.org:aarete/query-orchestration into feature/prometheus

* add log_level

and sync the config initialize

* docs

* cleanup

* add to compose:up:test

* docs for prometheus testing

* custom metrics

* cleanup

* merge main

* add tests

* cleanup docs

* cleanup

* lint

* fix unit tests (attempt)

* fix tests

* resolvesetlogger

* expose 8080

* compose changes

* bugfixesformichael

* don't build _test

* merge in main

* job_sync_runner
2025-02-13 15:44:08 +00:00

856 B

Deployments

Note about host service testing

If you want the docker prometheus in this stack to pull from your locally running service on localhost:8080 then edit the compose.local.yaml and change the reference from ./prometheus.allmetrics.yaml:/etc/prometheus/prometheus.yml to ./prometheus.localservice.yaml:/etc/prometheus/prometheus.yml

Local

When running task compose:up:local prometheus will be available on http://localhost:9090

When running task compose:up prometheus will be available on http://localhost:9091

To see which target services are being scraped by prometheus you can go to http:// localhost: [port] /targets

Local with service on host

If you need to run a service directly on the host for debugging then use task compose:up:test and then run the service like DB_PORT=5430 go run ./cmd/queryService