This is my first attempt at integrating Django with Pyctuator.
It's not finished yet, but I wanted to get your opinion first. The code isn't clean and, among other things, the disabled_endpoints part is missing.
I've implemented it using the same strategy as for the other Frameworks. However, I wonder if it wouldn't be better for django
to create a Django application with urls and middelware.
Indeed, in this PR, I modify the settings of django behind de scene. This doesn't seem to me to follow the Django philosophy.
For me, having a Django app in the pyctuator project would be the best solution.
All the user would have to do is configure the /pyctuator endpoint on the ROOT_URLS and add the middleware needed to track traces.
Hello there,
This is my first attempt at integrating Django with Pyctuator. It's not finished yet, but I wanted to get your opinion first. The code isn't clean and, among other things, the disabled_endpoints part is missing.
I've implemented it using the same strategy as for the other Frameworks. However, I wonder if it wouldn't be better for django to create a Django application with urls and middelware.
Indeed, in this PR, I modify the settings of django behind de scene. This doesn't seem to me to follow the Django philosophy. For me, having a Django app in the pyctuator project would be the best solution.
All the user would have to do is configure the /pyctuator endpoint on the ROOT_URLS and add the middleware needed to track traces.