This project was created with the simplest problem in mind, know how many devices are connected to a websocket, and export that metric to a Prometheus endpoint. Currently the only feature this project has is counting the numbers of open connections to a given websocket inside Django Channels.
You can either choose to enable logging for multiple consumers or just one.
Currently there are plans for naming the websockets and outputting different stats, for different websockets.
At the moment all consumers will count towards the same metric.
It works by you add a decorator that redirects all calls to, connect and disconnect functions inside your consumer to proxy through a counter first, and then calls your function in your consumer. That's all it does, nothing fancy, but I really needed the functionallity and decided to publish my work.
This project only support 1 worker at a time.
If you have installed versions before 1.0.0, you need to make changes to your consumers. This project has switched to a decorator approach, instead of mocking the consumer class.
Firstly you need to have Django Channels installed, and configured correctly. The project is currently only tested with Daphne and Uvicorn, but other ASGI web servers can be added to tests if the community deems so and or helps with it.
Then install the package via pip:
pip install django-channels-prometheus
Inside your installed apps in settings.py add the package:
INSTALLED_APPS = [
...
'channels_prometheus',
...
]
Inside your consumer you need to add either the 'ensure_prometheus_connect_async' decorator if you are using the async version, or 'ensure_prometheus_connect' if you are using the sync version.
See example:
import json
from channels.generic.websocket import AsyncWebsocketConsumer
from channels_prometheus.decorators import ensure_prometheus_connect_async
@ensure_prometheus_connect_async
class ChatConsumer(AsyncWebsocketConsumer):
async def connect(self):
self.room_name = self.scope["url_route"]["kwargs"]["room_name"]
self.room_group_name = f"chat_{self.room_name}"
# Join room group
await self.channel_layer.group_add(self.room_group_name, self.channel_name)
await self.accept()
async def disconnect(self, close_code):
# Leave room group
await self.channel_layer.group_discard(self.room_group_name, self.channel_name)
# Receive message from WebSocket
async def receive(self, text_data):
text_data_json = json.loads(text_data)
message = text_data_json["message"]
# Send message to room group
await self.channel_layer.group_send(
self.room_group_name, {"type": "chat.message", "message": message}
)
# Receive message from room group
async def chat_message(self, event):
message = event["message"]
# Send message to WebSocket
await self.send(text_data=json.dumps({"message": message}))
After that you will need to add the urls to the Prometheus endpoint to your projects urls like so:
from django.urls import path, include
from channels_prometheus import urls as channels_prometheus_urls
from . import views
urlpatterns = [
path('', views.home),
path('metrics/', include(channels_prometheus_urls))
]
Also make sure that you are pointing to the Djangos ASGI version inside your asgi.py
:
import os
from channels.auth import AuthMiddlewareStack
from channels.routing import ProtocolTypeRouter, URLRouter
from channels.security.websocket import AllowedHostsOriginValidator
from django.core.asgi import get_asgi_application
os.environ.setdefault("DJANGO_SETTINGS_MODULE", "tests.settings")
# Initialize Django ASGI application early to ensure the AppRegistry
# is populated before importing code that may import ORM models.
django_asgi_app = get_asgi_application()
from tests.routing import websocket_urlpatterns
application = ProtocolTypeRouter(
{
"http": django_asgi_app,
"websocket": AllowedHostsOriginValidator(
AuthMiddlewareStack(URLRouter(websocket_urlpatterns))
),
}
)
When all of that is configured you will be able to find your endpoint metrics at the defined url route.
- Create documentation
- Seperate different consumers to their own metrics.
- Known issue if the websockets are running on more than one worker, it will give inconsistent results.
Contributions are always welcome!
Read through the contributing.md
to know how to get started.
Please adhere to this project's code of conduct
.