Hi,
Checks framework is mainly built to prevent system starting management
commands in case of invalid state of the system. It's not meant for
health monitoring.
There exists several ways to run health checks - we use quite simple
setup with new relic.
There also exists django-health-checks that can provide maybe better set
of health checking and would be something that you're looking for.
On 27.03.2017 10:40, guettli wrote:
I guess a lot of people here are not only developers, they are
operators, too.
I mean they need to care for a production system and ensure it is up
and healthy.
I am unsure if the System Check Framework[1] inside Django is suited to do
monitoring checks.
With "monitoring checks" I mean these simple but valuable scripts
which exit 0=OK, 1=FAIL, 2=ERR, 3=UNKNOWN (like nagios)
Since I am mainly doing software development and only from time to time
I need to write or extend a monitoring check of our production
environment,
I prefer to code in my code base which uses django.
Updates in the monitoring area feel complicated (different git repos,
different deployment, ....)
According to the docs[1] the System Check Framework some checks are
executed during start up.
But there are no docs about periodical running checks on production
servers.
How do you handle this?
Do you use django checks for monitoring?
Or is this a bad idea?
If you use django checks for monitoring, how do you call them? The django
checks framework is only a way to provide the checks. It has no
information about
how often the checks should get executed.
Regards,
Thomas
[1] https://docs.djangoproject.com/en/1.10/topics/checks/
--
You received this message because you are subscribed to the Google
Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send
an email to django-users+unsubscr...@googlegroups.com
<mailto:django-users+unsubscr...@googlegroups.com>.
To post to this group, send email to django-users@googlegroups.com
<mailto:django-users@googlegroups.com>.
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-users/48d65ffa-5394-4af0-9002-9e98d757f01b%40googlegroups.com
<https://groups.google.com/d/msgid/django-users/48d65ffa-5394-4af0-9002-9e98d757f01b%40googlegroups.com?utm_medium=email&utm_source=footer>.
For more options, visit https://groups.google.com/d/optout.
--
Jani Tiainen
--
You received this message because you are subscribed to the Google Groups "Django
users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-users/b3922e03-f855-0d35-ff5a-e5752eb26c99%40gmail.com.
For more options, visit https://groups.google.com/d/optout.
