-
Notifications
You must be signed in to change notification settings - Fork 712
Issues: weaveworks/scope
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
Author
Label
Projects
Milestones
Assignee
Sort
Issues list
How can update or upgrade docker instance for scope or git pull?
#3907
opened Jul 27, 2022 by
johnfelipe
Weavescope provides email notification? Is there a plugin for this.
#3896
opened Feb 9, 2022 by
PradeepShetty14
codahale/hdrhistogram repo url has been transferred under the github HdrHstogram umbrella
#3884
opened Aug 16, 2021 by
filipecosta90
weavescope after installing on openshift cluster not showing container and process details.
#3881
opened Aug 2, 2021 by
cynosure711
Migrate off of eslint-loader
tech-debt
Unpleasantness that does (or may in future) affect development
#3876
opened Jul 9, 2021 by
dholbach
Migrate off of url-loader
tech-debt
Unpleasantness that does (or may in future) affect development
#3873
opened Jul 7, 2021 by
dholbach
Weave Scope does not record the pod topology when there is only job(not cronjob) in kubernetes
#3864
opened May 30, 2021 by
shabicheng
Add Describe control to Kubernetes hosts
estimate/hours
It will take less than 8 hours to implement
good-first-issue
Indicates a good issue for first-time contributors
k8s
Pertains to integration with Kubernetes
#3860
opened May 21, 2021 by
bboreham
Probe websocket double-connect/disconnect
chore
Related to fix/refinement/improvement of end user or new/existing developer functionality
mystery
We don't know what could be causing this
#3857
opened May 18, 2021 by
bboreham
Terminal is not accessible with screen readers
chore
Related to fix/refinement/improvement of end user or new/existing developer functionality
help-wanted
An issue that would be good for non-maintainers to attempt
#3840
opened Mar 30, 2021 by
alper061
Use S3 for historical queries instead of DynamoDB
estimate/weeks
It will take more than 7 8-hour work days to implement
performance
Excessive resource usage and latency; usually a bug or chore
#3839
opened Mar 20, 2021 by
bboreham
Previous Next
ProTip!
Find all open issues with in progress development work with linked:pr.