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

Update to Scope 0.13 #313

Merged
merged 9 commits into from
Mar 4, 2016
Merged

Update to Scope 0.13 #313

merged 9 commits into from
Mar 4, 2016

Conversation

2opremio
Copy link

@2opremio 2opremio commented Mar 2, 2016

As part of #311

DO NOT MERGE YET, pipes don't work because of weaveworks/scope#1085 so we will need to make a new release (0.13.1) and update this PR accordingly.

@2opremio 2opremio force-pushed the 311-scope-0.13 branch 2 times, most recently from 6e2e366 to c0aacaf Compare March 3, 2016 17:18
@tomwilkie
Copy link

You should run scope with the following arguments:

  • --app.weave.addr= to stop scope trying to update weave
  • -e CHECKPOINT_DISABLE=true (to docker) to stop it checking for new versions (and polluting the stats)

Both for:
* The apps run in the service
* The Scope instances used to monitor the service
@2opremio 2opremio changed the title [WIP] Update to Scope 0.13 Update to Scope 0.13 Mar 4, 2016
@2opremio
Copy link
Author

2opremio commented Mar 4, 2016

I have successfully tested this in the local cluster

  • Update the monitoring Scope instance in dev/prod

@tomwilkie PTAL

@2opremio
Copy link
Author

2opremio commented Mar 4, 2016

@peterbourgon Maybe you can also have a look at the monitoring bits? There are new endpoints, some of which are websockets.

@peterbourgon
Copy link

Just one new websocket endpoint, right? And it looks like you're excluding it properly. 👍

@2opremio
Copy link
Author

2opremio commented Mar 4, 2016

@peterbourgon Good point, now that I think about it there's two .. one from the app. Let me exclude that one too.

args:
- --no-app
- --probe.docker.bridge=cbr0
- --probe.docker=true
- --probe.kubernetes=true
- --app.weave.addr=

This comment was marked as abuse.

This comment was marked as abuse.

This comment was marked as abuse.

@2opremio
Copy link
Author

2opremio commented Mar 4, 2016

It turns out monitoring was broken too. I have fixed it in this PR as well since it requires updating monitoring due to an update in its rules.

@tomwilkie @peterbourgon Please take a final look

@@ -98,13 +98,13 @@ func (f *flags) makeAppProvisioner() appProvisioner {

var p appProvisioner

args := []string{"--no-probe"}

args := []string{"--no-probe", "--app.weave.addr="}

This comment was marked as abuse.

@peterbourgon
Copy link

I had some questions but they were more for my own edification. LGTM.

2opremio pushed a commit that referenced this pull request Mar 4, 2016
@2opremio 2opremio merged commit 5efb038 into master Mar 4, 2016
@2opremio 2opremio deleted the 311-scope-0.13 branch March 4, 2016 18:28
@2opremio 2opremio mentioned this pull request Mar 4, 2016
7 tasks
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