DPDK CI discussions
 help / color / mirror / Atom feed
From: UNH-IOL Open Source Team Monitoring <os-team@iol.unh.edu>
To: <ci@dpdk.org>
Subject: [RECOVERY] https on dpdk-dashboard.iol.unh.edu is OK!
Date: Tue, 28 Jun 2022 13:52:26 -0400	[thread overview]
Message-ID: <62bb3fdb.1c69fb81.ed71f.88e6SMTPIN_ADDED_MISSING@mx.google.com> (raw)

***** Service Monitoring on be4a8032ed06 *****

https on dpdk-dashboard.iol.unh.edu is OK!

Info:    HTTP OK: HTTP/1.1 200 OK - 7416 bytes in 0.316 second response time 

When:    2022-06-28 13:52:26 -0400
Service: https
Host:    dpdk-dashboard.iol.unh.edu
IPv4:    132.177.123.104
IPv6:    2606:4100:3880:1234::104

http://os-monitor.iol.unh.edu/monitoring/service/show?host=dpdk-dashboard.iol.unh.edu&service=https

             reply	other threads:[~2022-06-28 17:52 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-28 17:52 UNH-IOL Open Source Team Monitoring [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-07-08 18:14 UNH-IOL Open Source Team Monitoring
2022-07-06 14:20 UNH-IOL Open Source Team Monitoring
2022-07-05  6:37 UNH-IOL Open Source Team Monitoring
2022-07-05  6:10 UNH-IOL Open Source Team Monitoring
2022-07-03  9:55 UNH-IOL Open Source Team Monitoring
2022-07-02 19:10 UNH-IOL Open Source Team Monitoring
2022-06-30 18:51 UNH-IOL Open Source Team Monitoring
2022-06-24 18:52 UNH-IOL Open Source Team Monitoring
2022-06-24 18:00 UNH-IOL Open Source Team Monitoring
2022-06-18 16:10 UNH-IOL Open Source Team Monitoring
2022-06-14 12:15 UNH-IOL Open Source Team Monitoring
2022-06-13  5:20 UNH-IOL Open Source Team Monitoring
2022-06-09 17:41 UNH-IOL Open Source Team Monitoring
2022-06-08  7:40 UNH-IOL Open Source Team Monitoring
2022-05-19  8:36 UNH-IOL Open Source Team Monitoring
2022-05-16 16:46 UNH-IOL Open Source Team Monitoring
2022-05-12  8:21 UNH-IOL Open Source Team Monitoring
2022-05-05 12:36 UNH-IOL Open Source Team Monitoring
2022-05-04 14:11 UNH-IOL Open Source Team Monitoring
2022-05-02  0:51 UNH-IOL Open Source Team Monitoring
2022-05-01  5:21 UNH-IOL Open Source Team Monitoring
2022-04-29 21:16 UNH-IOL Open Source Team Monitoring
2022-03-25 15:27 UNH-IOL Open Source Team Monitoring
2022-03-24 15:32 UNH-IOL Open Source Team Monitoring
2022-02-13  2:27 UNH-IOL Open Source Team Monitoring
2022-02-03  0:13 UNH-IOL Open Source Team Monitoring
2022-01-26 22:22 UNH-IOL Open Source Team Monitoring
2022-01-21 13:54 UNH-IOL Open Source Team Monitoring
2022-01-03 19:44 UNH-IOL Open Source Team Monitoring
2021-12-20 10:19 UNH-IOL Open Source Team Monitoring
2021-12-18  8:43 UNH-IOL Open Source Team Monitoring
2021-12-18  6:58 UNH-IOL Open Source Team Monitoring
2021-12-09  7:32 UNH-IOL Open Source Team Monitoring
2021-12-09  4:41 UNH-IOL Open Source Team Monitoring
2021-12-07 18:39 UNH-IOL Open Source Team Monitoring
2021-12-04  8:24 UNH-IOL Open Source Team Monitoring
2021-11-23  2:57 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=62bb3fdb.1c69fb81.ed71f.88e6SMTPIN_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).