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

WIP : Expose active/inactive connection to service backend as prometheus metrics #65

Merged
merged 1 commit into from
Jul 15, 2017

Conversation

murali-reddy
Copy link
Member

partial fix for #5

…eus metrics

putting basic skelton framework to use prometheus

Fixes #5
@murali-reddy
Copy link
Member Author

murali-reddy commented Jul 15, 2017

metrics exposed as http://nodeip:8080/metrics

# HELP kube_router_service_backend_active_connections Active conntection to backend of service
# TYPE kube_router_service_backend_active_connections gauge
kube_router_service_backend_active_connections{backend="100.96.1.2",namespace="kube-system",service_name="kube-dns"} 0
kube_router_service_backend_active_connections{backend="100.96.1.3",namespace="default",service_name="redis-slave"} 0
kube_router_service_backend_active_connections{backend="100.96.1.4",namespace="default",service_name="frontend"} 0
kube_router_service_backend_active_connections{backend="100.96.1.5",namespace="default",service_name="frontend"} 0
kube_router_service_backend_active_connections{backend="100.96.2.3",namespace="kube-system",service_name="kube-dns"} 0
kube_router_service_backend_active_connections{backend="100.96.2.4",namespace="default",service_name="redis-master"} 1
kube_router_service_backend_active_connections{backend="100.96.2.5",namespace="default",service_name="redis-slave"} 0
kube_router_service_backend_active_connections{backend="100.96.2.6",namespace="default",service_name="frontend"} 0
kube_router_service_backend_active_connections{backend="172.20.51.157",namespace="default",service_name="kubernetes"} 1
# HELP kube_router_service_backend_inactive_connections Active conntection to backend of service
# TYPE kube_router_service_backend_inactive_connections gauge
kube_router_service_backend_inactive_connections{backend="100.96.1.2",namespace="kube-system",service_name="kube-dns"} 0
kube_router_service_backend_inactive_connections{backend="100.96.1.3",namespace="default",service_name="redis-slave"} 0
kube_router_service_backend_inactive_connections{backend="100.96.1.4",namespace="default",service_name="frontend"} 0
kube_router_service_backend_inactive_connections{backend="100.96.1.5",namespace="default",service_name="frontend"} 0
kube_router_service_backend_inactive_connections{backend="100.96.2.3",namespace="kube-system",service_name="kube-dns"} 0
kube_router_service_backend_inactive_connections{backend="100.96.2.4",namespace="default",service_name="redis-master"} 2
kube_router_service_backend_inactive_connections{backend="100.96.2.5",namespace="default",service_name="redis-slave"} 0
kube_router_service_backend_inactive_connections{backend="100.96.2.6",namespace="default",service_name="frontend"} 0
kube_router_service_backend_inactive_connections{backend="172.20.51.157",namespace="default",service_name="kubernetes"} 0

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.

1 participant