1319869 - New heroku apps need nagios checks

Status: RESOLVED DUPLICATE of bug 1383047

(Release Engineering :: General, defect, P5)

Description

[Jake Watkins [:dividehex]]

New domains and ssl certs are being setup in bug 1317026.  These new apps will need basic https ssl and https cert expiration checks setup in nagios.

Comment 1

[Jake Watkins [:dividehex]]

Nagios checks have been added for the following web apps:
treestatus.mozilla-releng.net
tooltool.mozilla-releng.net
mapper.mozilla-releng.net
archiver.mozilla-releng.net

commit 71213ab50cb0143bb258958568270522a3da7f96
Author: Jake Watkins <[e-mail]>
Date:   Thu Dec 15 09:40:19 2016 -0800

    Bug 1319869: add nagios checks for new releng webapps

Comment 2

[Jake Watkins [:dividehex]]

These checks failed from a 502 Bad gateways code on https.  This was a bit confusing since I checked the urls with curl before implementing the checks.  Turns out, even if you heroku app doesn't have an code or dynos running, they will serve up a nice landing page with a 'Heroku | Welcome to your new app!' msg.  All looks fine but that page is actually returning a 502 error.

Comment 3

[Jake Watkins [:dividehex]]

I've commented out the checks for now. :garbas, when apps are ready for production, let me know here and I'll remove the comments blocks in nagios.

commit 5d95e95b5fc1c2ee4d86b247b6eca31dc3172d60
Author: Jake Watkins <[e-mail]>
Date:   Thu Dec 15 11:05:01 2016 -0800

    Bug 1319869: comment out nagios checks for non working releng webapps

Comment 4

[Rok Garbas [:garbas]]

just to confirm i got the message and i'm keeping <needinfo> so that it is a constant reminder.

Comment 5

[Rok Garbas [:garbas]]

2 Heroku apps went live this week:

- treestatus.mozilla-releng.net
- dashboard.shipit.mozilla-releng.net

As discussed I would like to request Nagios checks.

To move forward (as more Heroku apps are planned for this month) should I keep a ticket open or should create new ticket(s) for each release that we have?

Comment 6

[Chris Cooper [:coop] (he/him)]

buildduty should be able to help with this.

Comment 7

[Alin Selagea [:aselagea]]

Attachment: dashboard.shipit+treestatus.patch

Removed the comments block for treestatus and added new entries for dashboard.shippit.

Do we also need domain and heroku entries for dashboard.shipit.mozilla-releng.net (similar to treestatus)?

Comment 8

[Amy Rich [:arr] [:arich]]

Comment on attachment 8834392 [details] [diff] [review]
dashboard.shipit+treestatus.patch

Review of attachment 8834392 [details] [diff] [review]:
-----------------------------------------------------------------

These look syntactically correct, which is really the only review I'm qualified to give in this instance.

Comment 9

[Alin Selagea [:aselagea]]

Comment on attachment 8834392 [details] [diff] [review]
dashboard.shipit+treestatus.patch

I missed the fact that we already have entries for "dashboard.shipit.mozilla-releng.net", so I guess we only have to remove the comments for treestatus.

Comment 10

[Mihai Tabara [:mtabara]⌚️GMT]

Looks like we're really close to finish this. However, I see no activity for more than half a year on this bug.
@aselagea: is this worth finishing up or do we don't need this anymore?

Comment 11

[Amy Rich [:arr] [:arich]]

:garbas has been working on these, I'll assign to him.

Comment 12

[Rok Garbas [:garbas]]

I will close this in favor of Bug 1383047 where the conversation is already happening.