| From: | Rory Campbell-Lange <rory(at)campbell-lange(dot)net> |
|---|---|
| To: | Steve Clark <steve(dot)clark(at)netwolves(dot)com> |
| Cc: | pgsql <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Schedule |
| Date: | 2017-06-20 16:48:52 |
| Message-ID: | 20170620164852.544s4rr44bpniu6u@campbell-lange.net |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 20/06/17, Steve Clark (steve(dot)clark(at)netwolves(dot)com) wrote:
> > 4) Equipment table keyed to location.
> We already have a monitoring system in place that has been in operation circa 2003. Just recently we have
> added a new class of customer whose operation is not 24/7.
>
> I envision the schedule could be fairly complicated
> including WE and holidays, plus the enduser might shut down for lunch etc. I am looking for more on how to organize the
> schedule, EG a standard weekly schedule then exceptions for holidays etc, or a separate individual schedule for
> each week, also need to consider how easy it is to maintain the schedule, etc.
Assuming you have the ability to disable alerts for a
client/location/group/machine for a period of time, you could use
pg_cron schedules https://github.com/citusdata/pg_cron to enable and
disable this ability on a scheduled basis.
With some sort of front-end it would be trivial for the customer to
make their own schedules.
Rory
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alban Hertroys | 2017-06-20 20:23:41 | Re: Schedule |
| Previous Message | Adrian Klaver | 2017-06-20 16:46:32 | Re: Schedule |