django-silk VS ara

But that's still not backend-specific SQL?

There should be an interface method for this. Why does psycopg call it mogrify?

https://django-debug-toolbar.readthedocs.io/en/latest/panels... :

> debug_toolbar.panels.sql.SQLPanel: SQL queries including time to execute and links to EXPLAIN each query

But debug toolbars mostly don't work with APIs.

https://github.com/django-query-profiler/django-query-profil... :

> Django query profiler - one profiler to rule them all. Shows queries, detects N+1 and gives recommendations on how to resolve them

https://github.com/jazzband/django-silk :

> Silk is a live profiling and inspection tool for the Django framework. Silk intercepts and stores HTTP requests and database queries before presenting them in a user interface for further inspection

you're using DRF, which DDT doesn't work well with. DDT is more for template rendered pages, not API responses. Have you brought in Django silk for monitoring this?

https://github.com/jazzband/django-silk/issues?q=is%3Aopen+is%3Aissue+label%3Abug

Are you using Django-silk? Googling for the error shows https://github.com/jazzband/django-silk/issues/374

Those docs are wrong. They still reference syncdb. Use the README at https://github.com/jazzband/django-silk.

Perhaps https://github.com/jazzband/django-silk?

If you're using Django as an API, without templates, django debug toolbar is useless because it requires templates. It won't work with DRF endpoints which means you miss out on profiling and SQL tracing. That's where django-silk shines.

You can also install django-silk to profile your app, and play around with different implementations.

https://github.com/ansible-community/ara/pull/358 https://github.com/b12io/orchestra/pull/830 https://github.com/batiste/django-page-cms/pull/210 https://github.com/carpentries/amy/pull/2130 https://github.com/celery/django-celery/pull/612 https://github.com/django-cms/django-cms/pull/7241 https://github.com/django-oscar/django-oscar/pull/3867 https://github.com/esrg-knights/Squire/pull/253https://github.com/Frojd/django-react-templatetags/pull/64 https://github.com/groveco/django-sql-explorer/pull/474 https://github.com/jazzband/django-silk/pull/550 https://github.com/keras-team/keras/pull/16073 https://github.com/ministryofjustice/cla_backend/pull/773 https://github.com/nitely/Spirit/pull/306 https://github.com/python/pythondotorg/pull/1987 https://github.com/rapidpro/rapidpro/pull/1610 https://github.com/ray-project/ray/pull/22396 https://github.com/saltstack/salt/pull/61647 https://github.com/Swiss-Polar-Institute/project-application/pull/483 https://github.com/UEWBot/dipvis/pull/216

Look into AWX as an alternative to Tower. If you just want better reporting on runs, check out ARA or callback plugins.

Also worth considering is ARA for playbook reporting, and then whatever you want for orchestration (Jenkins, Azure Devops, Rundeck, etc).

Why not use ara?

For general recording of playbook activity with a web dashboard, ARA works really well.

If you don’t want any UI / access control then you can also look at ARA - https://ara.recordsansible.org This works as a callback plugin to capture the job run data.

I'm not sure how to interpret running 100 debug messages (https://github.com/ansible-community/ara/blob/master/tests/integration/benchmark_tasks.yaml) into real life performance. Mitogen's Benchmark used either 100 times a "hostname" command on the target machine (https://github.com/mitogen-hq/mitogen/blob/master/tests/ansible/bench/loop-100-items.yml) or running the DebOps project (https://github.com/debops/debops-playbooks/blob/master/playbooks/common.yml) for some sorta real-world module usage.

Reach out on Mastodon or see this issue on GitHub.

There has been discussions about a prometheus exporter for monitoring, metrics and eventually fancy graphs in grafana but work on this has not started yet: https://github.com/ansible-community/ara/issues/177