From: UNH-IOL Open Source Team Monitoring <os-team@iol.unh.edu>
To: <ci@dpdk.org>
Subject: [RECOVERY] http on dpdkdashboard.iol.unh.edu is OK!
Date: Fri, 15 Dec 2023 15:00:33 -0500 [thread overview]
Message-ID: <657cb062.920a0220.bf87.ef6cSMTPIN_ADDED_MISSING@mx.google.com> (raw)
***** Service Monitoring on 9ab6452f2653 *****
http on dpdkdashboard.iol.unh.edu is OK!
Info: HTTP OK: HTTP/1.1 301 Moved Permanently - 497 bytes in 0.001 second response time
When: 2023-12-15 15:00:33 -0500
Service: http
Host: dpdkdashboard.iol.unh.edu
IPv4: 132.177.123.104
IPv6: 2606:4100:3880:1234::104
http://os-monitor.iol.unh.edu/monitoring/service/show?host=dpdkdashboard.iol.unh.edu&service=http
next reply other threads:[~2023-12-15 20:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-15 20:00 UNH-IOL Open Source Team Monitoring [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-03-02 14:19 UNH-IOL Open Source Team Monitoring
2024-01-24 15:19 UNH-IOL Open Source Team Monitoring
2023-12-21 1:04 UNH-IOL Open Source Team Monitoring
2023-12-19 15:13 UNH-IOL Open Source Team Monitoring
2023-12-19 14:03 UNH-IOL Open Source Team Monitoring
2023-12-13 14:25 UNH-IOL Open Source Team Monitoring
2023-11-03 16:49 UNH-IOL Open Source Team Monitoring
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=657cb062.920a0220.bf87.ef6cSMTPIN_ADDED_MISSING@mx.google.com \
--to=os-team@iol.unh.edu \
--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).