From: Lincoln Lavoie <lylavoie@iol.unh.edu>
To: Aaron Conole <aconole@redhat.com>
Cc: ci@dpdk.org
Subject: Re: [CUSTOM] http on dpdk-dashboard.iol.unh.edu is OK!
Date: Wed, 17 Nov 2021 08:46:50 -0500 [thread overview]
Message-ID: <CAOE1vsMmK+1GJyJtevU-mAaVBGFQQrf+8MODsPvGsVZLMYbCrA@mail.gmail.com> (raw)
In-Reply-To: <f7t1r3eoq4l.fsf@redhat.com>
Hi Aaron,
No, that was a notification I "forced" to happen from the GUI, after the
email issue was fixed. Notifications happen for down two, but that would
require me to actually kill the service or somehow break the monitoring.
The "forced" ones just report the current state of the object being
monitored.
Cheers,
Lincoln
On Wed, Nov 17, 2021 at 8:42 AM Aaron Conole <aconole@redhat.com> wrote:
> Hi Lincoln,
>
> This looks good - seems like it only happens on 'up.' Is there also a
> notification that can be sent when we first detect 'down' as well?
>
> -Aaron
>
> UNH-IOL Open Source Team Monitoring <os-team@iol.unh.edu> writes:
>
> > ***** Service Monitoring on aed1b7bcbb73 *****
> >
> > http on dpdk-dashboard.iol.unh.edu is OK!
> >
> > Info: HTTP OK: HTTP/1.1 301 Moved Permanently - 495 bytes in 0.002
> second response time
> >
> > When: 2021-11-16 16:01:59 +0000
> > Service: http
> > Host: dpdk-dashboard.iol.unh.edu
> > IPv4: 132.177.123.104
> > IPv6: 2606:4100:3880:1234::104
> >
> > Comment by lylavoie:
> > Sending a test notificaiton.
> >
> >
> http://os-monitor.iol.unh.edu/monitoring/service/show?host=dpdk-dashboard.iol.unh.edu&service=http
>
>
--
*Lincoln Lavoie*
Principal Engineer, Broadband Technologies
21 Madbury Rd., Ste. 100, Durham, NH 03824
lylavoie@iol.unh.edu
https://www.iol.unh.edu
+1-603-674-2755 (m)
<https://www.iol.unh.edu>
prev parent reply other threads:[~2021-11-17 13:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-16 16:01 UNH-IOL Open Source Team Monitoring
2021-11-17 13:42 ` Aaron Conole
2021-11-17 13:46 ` Lincoln Lavoie [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAOE1vsMmK+1GJyJtevU-mAaVBGFQQrf+8MODsPvGsVZLMYbCrA@mail.gmail.com \
--to=lylavoie@iol.unh.edu \
--cc=aconole@redhat.com \
--cc=ci@dpdk.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).