Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Probes POST to apps #342

Merged
merged 2 commits into from
Aug 10, 2015
Merged

Probes POST to apps #342

merged 2 commits into from
Aug 10, 2015

Conversation

peterbourgon
Copy link
Contributor

Change the flow of the streams.

image

router := mux.NewRouter()
post := router.Methods("POST").Subrouter()
post.HandleFunc("/", handleReport(c))

This comment was marked as abuse.

This comment was marked as abuse.

@tomwilkie
Copy link
Contributor

For the OSS to work, doesn't the probe need to use the resolver to publish to multiple apps?

@@ -25,10 +25,11 @@ var version = "dev" // set at build time

func main() {
var (
publish = flag.String("publish", fmt.Sprintf("http://localhost:%d", xfer.AppPort), "URL to publish reports")

This comment was marked as abuse.

This comment was marked as abuse.

@peterbourgon peterbourgon force-pushed the reverse-publish branch 4 times, most recently from 75f6fc5 to 9099b2a Compare August 7, 2015 10:59
- App takes POST report on /api/report
- Probe publishes to configured target(s)
- Name resolution happens on probe-side
- There's no longer an xfer.ProbePort
- xfer.Collector responsibility is reduced
- Fixes to remaining experimental components.
- rm experimental/bridge: it's not being used, and by changing the
  app/probe comm model, it would require a complete refactor anyway. We
  can easily rebuild it when we need to. It will even be much simpler.
- rm experimental/graphviz: it's broken for some time anyway, and we
  don't really need to play around with it as a rendering option
  anymore.
- rm experimental/oneshot: we never use this anymore.
@peterbourgon peterbourgon changed the title [WIP] Probes connect to apps Probes POST to apps Aug 7, 2015
@peterbourgon
Copy link
Contributor Author

@tomwilkie @paulbellamy @2opremio Ready for review!

p.closer.Close()
// AuthorizationHeader returns a value suitable for an HTTP Authorization
// header, based on the passed token string.
func AuthorizationHeader(token string) string {

This comment was marked as abuse.

This comment was marked as abuse.

@paulbellamy
Copy link
Contributor

Overall, LGTM

peterbourgon added a commit that referenced this pull request Aug 10, 2015
@peterbourgon peterbourgon merged commit 514f4bc into master Aug 10, 2015
@peterbourgon peterbourgon deleted the reverse-publish branch August 10, 2015 08:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants