You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 28, 2022. It is now read-only.
Need to expose options so that PDK ingestion code can configure go-pilosa to use tracing.
Additionally, the usual configuration will probably be that go-pilosa is writing to the same tracing infra as Pilosa, so it might be worth Pilosa exposing its tracing config through an endpoint which go-pilosa can consume, thereby allowing hands-off config by default... 🤔 This second part is not too relevant directly to the PDK... I think we still need the first part anyway.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Need to expose options so that PDK ingestion code can configure go-pilosa to use tracing.
Additionally, the usual configuration will probably be that go-pilosa is writing to the same tracing infra as Pilosa, so it might be worth Pilosa exposing its tracing config through an endpoint which go-pilosa can consume, thereby allowing hands-off config by default... 🤔 This second part is not too relevant directly to the PDK... I think we still need the first part anyway.
The text was updated successfully, but these errors were encountered: