At the moment, the blazegraph URL is hardcoded to http://localhost:9999/bigdata/. We need to support multiple blazegraph instances, so we need this endpoint to be configurable.
We could take the opportunity to allow a single exporter to monitor multiple blazegraph instances, but it is probably simpler to keep a 1-1 relationship, as is done for most exporters.
| Subject | Repo | Branch | Lines +/- | |
|---|---|---|---|---|
| make blazegraph port configurable | operations/debs/prometheus-blazegraph-exporter | master | +21 -13 |
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | Smalyshev | T213210 WDQS is hitting allocator limit on Blazegraph | |||
| Resolved | Smalyshev | T213212 Move category namespace to a separate blazegraph instance | |||
| Resolved | Smalyshev | T213234 Create puppet config to run two instances of Blazegraph | |||
| Resolved | Smalyshev | T213289 blazegraph endpoint in prometheus-blazegraph-exporter should be configureable |
Change 483144 had a related patch set uploaded (by Gehel; owner: Gehel):
[operations/debs/prometheus-blazegraph-exporter@master] make blazegraph port configurable
Change 483144 merged by Gehel:
[operations/debs/prometheus-blazegraph-exporter@master] make blazegraph port configurable