From: Kaike Subject: Re: [sloan-25mlog 7196] 2.5m obslog 20240423 (SJD 60424) Date: Wed, 24 Apr 2024 13:02:45 -0600 --Apple-Mail=_131D56A4-534A-4A09-A738-EF07E17D4775 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 Sounds to me it worths a effort to change the message to clearly state = that there was an issue, now it is cleared.=20 > On Apr 24, 2024, at 12:43=E2=80=AFPM, Donor, John = wrote: >=20 > "Ok" status alerts are only emailed if they were initially serious or = critical (with some possible exceptions), things like temperature or = vacuum alarms I think should still be broadcast even if the condition = only persisted for a minute. If the microNotTalking alert doesn't rise = to that level, there should be a flag that can be set so it doesn't = email if it has already cleared. >=20 > I'm also happy to change the message so it isn't just "ok" as the = status. "ok" has always been fine for me but I aim to please site staff! >=20 > These alerts should not email more than once if they've cleared. I = think even active alerts should be better about spamming now? I vaguely = recall adding that feature (or fixing that bug if you prefer) many = months ago, and not seeing the behavior recently? Of course if we see it = again I'll be happy to address it. >=20 > Thanks, > John >=20 > From: John > > Sent: Wednesday, April 24, 2024 1:37 PM > To: Donor, John >; Jos=C3=A9 = S=C3=A1nchez-Gallego > > Cc: obs-report-25m@apo.nmsu.edu = >; = Shane Thomas > > Subject: Re: [sloan-25mlog 7194] Re: 2.5m obslog 20240423 (SJD 60424) > =20 > [EXTERNAL EMAIL WARNING] DO NOT CLICK LINKS or open attachments unless = you recognize the sender and know the content is safe. > Odd to use one alert for two different conditions - first condition = being that this is a problem, second condition being that this was a = problem but is no longer a problem. Those are two very distinctly = different states of malfunction, seems to me that each warrants a = distinctly different alert. =20 >=20 > Of course, one could argue that the "ok" modifier is the distinct = difference. Perhaps a less ambiguous indicator would be useful, clearly = communicating that this alert was spawned by a momentary condition but = if it continues to happen often it may warrant attention? In such a = case, the alert should be emailed once, but not incessantly the way = ongoing alerts tend to be emailed. >=20 > Just a thought. Could save us some log mining to try to sort out = whether this current issue is actually a problem or not. >=20 > Thanks, > John >=20 > On 4/24/24 12:23 PM, Donor, John wrote: >> It looks like all the BOSS alerts have a 120 second delay. So some = alerts could clear up before an email is sent, but if the alert is = severe enough we'll get an email if the alert wasn't cleared. This was = the case with the microNotTalking alert from yesterday; it was sent with = "ok" status, indicating it was no longer in the bad state, but had not = been acknowledged yet. >>=20 >> -John >>=20 >> From: Jos=C3=A9 S=C3=A1nchez-Gallego = >> Sent: Wednesday, April 24, 2024 12:09 PM >> To: Donor, John >> Cc: obs-report-25m@apo.nmsu.edu = ; = Shane Thomas ; John = >> Subject: Re: [sloan-25mlog 7191] Re: 2.5m obslog 20240423 (SJD 60424) >> =20 >> [EXTERNAL EMAIL WARNING] DO NOT CLICK LINKS or open attachments = unless you recognize the sender and know the content is safe. >> The last daytime alerts I got are from September 2023. The more = recent ones are all night-time. But it may be the observers have seen = the alerts and dealt with them before they sent an email, or if they are = very transitory they may not generate an email. >>=20 >> John, do these alerts immediately email or do they need to be active = for some time? >>=20 >> Thanks, >>=20 >> Jos=C3=A9 >>=20 >>=20 >> On Apr 24, 2024 at 09:47:19, "Donor, John" > wrote: >>> I definitely see an alert from yesterday for microNotTalking? I'm = not sure what timestamp we should be looking for. >>>=20 >>> Did no one else get that email? It looks like it went to the list = but I get emailed directly as well so there might be an issue with the = list. >>>=20 >>> On Apr 24, 2024 11:44 AM, John via sloan-25mlog = > wrote: >>> [EXTERNAL EMAIL WARNING] DO NOT CLICK LINKS or open attachments = unless you recognize the sender and know the content is safe. >>>=20 >>> On 4/24/24 10:38 AM, Kaike via sloan-25mlog wrote: >>> > >>> >> On Apr 24, 2024, at 10:14=E2=80=AFAM, John > wrote: >>> >> >>> >> The physical connections appear to be ok. >>> >> >>> >> Before we do something like unplug them to clean the contacts, = can you tell me if this is happening outside of observing time as well? = Obviously we wouldn't see a netburner problem while not observing, but = we would see camcheck connection problems. Before assuming this is a = connection trouble, lets establish that it happens during the day also. >>> > This happened during days also well, but not recently. This = happened last time is a couple of weeks ago. >>> Any similar connection issues with the specmech? >>> > >>> > >>> >> Either I'm no longer on the alerts email list, or alerts no = longer sends out emails. No clue which, so much has changed since 2020. = In previous surveys I would have been well aware of camcheck problems = just from the alerts emails. >>> > Not sure what changed, sounds like most people don=E2=80=99t = receive this particular alert on MicroNotTalk. I am including John Donor = in the email so he and Jose can comment on this. >>> I'm not sure I see any alert emails at all. >>> > >>> > -Kaike >>> > >>> > >>> >> John >>> >> >>> >> On 4/24/24 9:11 AM, Kaike wrote: >>> >>>> On Apr 24, 2024, at 6:14=E2=80=AFAM, Conner via sloan-25mlog = > wrote: >>> >>>> >>> >>>> >>> >>>> APACHE POINT OBSERVATORY SDSS 2.5M >>> >>>> >>> >>>> OBSERVING LOG >>> >>>> Tuesday April 23, 2024 >>> >>>> >>> >>>> (SJD 60424) >>> >>>> >>> >>>> ---- Observing Team ---- >>> >>>> >>> >>>> >>> >>>> Conner Scoresby >>> >>>> >>> >>>> ---- Observing Plan ---- >>> >>>> >>> >>>> >>> >>>> Tue 23 Apr 2024 60424 1.00 02:36 02:52 11:10 09:59 = 18:18 Day bright ( 9.3 h) >>> >>>> >>> >>>> ---- Observing Summary ---- >>> >>>> >>> >>>> Another excellent and efficient night for observing from the = queue. >>> >>>> >>> >>>> Notes: >>> >>>> >>> >>>> 1. Another Netburner issue around 03:00Z >>> >>> Once again, the event is associated with a broader communication = issue, the SP1MicroNotTalking issue: alert=3DcamCheck.SP1MicroNotTalking, = ok, "at 2024-04-24 03:19:06 UT found 'Reported by camCheck'", enabled, = noack, -1 >>> >>> >>> >>> Can the network switch, media converter, and cables for SP1 = communication be checked out? >>> >>> >>> >>> Thanks, >>> >>> >>> >>> -Kaike >>> >>> >>> > ____________________________________________________________ >>> > Logs of Nightly APO Activities > >>> > = https://urldefense.com/v3/__https://trac.sdss.org/tracmailman/browser/priv= ate/sloan-25mlog/index.html__;!!K6Z8K8YTIA!AZ6YvOGL-odqvU7J-mRp7WhaeJig4Md= lKkIXGGDxJ7-K-hi3wsOTCuE4qlV-t9zDFwtvjawrAR6-Rw1C9vtp$ >>> ____________________________________________________________ >>> Logs of Nightly APO Activities > >>> = https://urldefense.com/v3/__https://trac.sdss.org/tracmailman/browser/priv= ate/sloan-25mlog/index.html__;!!K6Z8K8YTIA!AZ6YvOGL-odqvU7J-mRp7WhaeJig4Md= lKkIXGGDxJ7-K-hi3wsOTCuE4qlV-t9zDFwtvjawrAR6-Rw1C9vtp$ >>>=20 >>> ____________________________________________________________ >>> Logs of Nightly APO Activities > >>> = https://urldefense.com/v3/__https://trac.sdss.org/tracmailman/browser/priv= ate/sloan-25mlog/index.html__;!!K-Hz7m0Vt54!gljVnVcNf37YfTucgMLpuV4ecLHR3L= hWAxnJhUwbQ334OxvO-NbRvuO3FdaR6mEmoO8UusRsiWTgSXui$ >>=20 >>=20 >> ____________________________________________________________ >> Logs of Nightly APO Activities = >> = https://trac.sdss.org/tracmailman/browser/private/sloan-25mlog/index.html = > ____________________________________________________________ > Logs of Nightly APO Activities > = https://trac.sdss.org/tracmailman/browser/private/sloan-25mlog/index.html --Apple-Mail=_131D56A4-534A-4A09-A738-EF07E17D4775 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8 Sounds to me = it worths a effort to change the message to clearly state that there was = an issue, now it is cleared. On Apr 24, 2024, at 12:43=E2=80=AFPM, Donor, John = wrote:"Ok" status alerts are = only emailed if they were initially serious or critical (with some = possible exceptions), things like temperature or vacuum alarms I think = should still be broadcast even if the condition only persisted for a = minute. If the microNotTalking alert doesn't rise to that level, there = should be a flag that can be set so it doesn't email if it has already = cleared.I'm also happy to change the message so it isn't just = "ok" as the status. "ok" has always been fine for me but I aim to please = site staff!These alerts should not email more than once if they've cleared. = I think even active alerts should be better about spamming now? I = vaguely recall adding that feature (or fixing that bug if you prefer) = many months ago, and not seeing the behavior recently? Of course if we = see it again I'll be happy to address it.Thanks,JohnFrom: John Se= nt: Wednesday, = April 24, 2024 1:37 PMTo: Donor, John ; Jos=C3=A9 = S=C3=A1nchez-Gallego Cc: obs-report-25m@apo.nmsu.edu ; Shane Thomas Subjec= t: Re: = [sloan-25mlog 7194] Re: 2.5m obslog 20240423 (SJD = 60424) [EXTERNAL EMAIL WARNING] DO NOT CLICK LINKS = or open attachments unless you recognize the sender and know the content = is safe.Odd to use one alert for two different conditions - first = condition being that this is a problem, second condition being that this = was a problem but is no longer a problem. Those are two very = distinctly different states of malfunction, seems to me that each = warrants a distinctly different alert. Of course, one could = argue that the "ok" modifier is the distinct difference. Perhaps a = less ambiguous indicator would be useful, clearly communicating that = this alert was spawned by a momentary condition but if it continues to = happen often it may warrant attention? In such a case, the alert = should be emailed once, but not incessantly the way ongoing alerts tend = to be emailed.Just = a thought. Could save us some log mining to try to sort out = whether this current issue is actually a problem or not.Thanks,JohnOn = 4/24/24 12:23 PM, Donor, John wrote:It looks like all the BOSS alerts have a = 120 second delay. So some alerts could clear up before an email is sent, = but if the alert is severe enough we'll get an email if the alert wasn't = cleared. This was the case with the microNotTalking alert from = yesterday; it was sent with "ok" status, indicating it was no longer in = the bad state, but had not been acknowledged yet.-JohnFrom: Jos=C3=A9 = S=C3=A1nchez-Gallego Sent: Wednesday, April 24, = 2024 12:09 PMTo: Donor, John Cc: obs-report-25m@apo.nmsu.edu ; Shane Thomas ; = John Subject: Re: = [sloan-25mlog 7191] Re: 2.5m obslog 20240423 (SJD = 60424) [EXTERNAL EMAIL WARNING] DO NOT CLICK LINKS = or open attachments unless you recognize the sender and know the content = is safe.The last daytime alerts I got = are from September 2023. The more recent ones are all night-time. But it = may be the observers have seen the alerts and dealt with them before = they sent an email, or if they are very transitory they may not generate = an email.John, do = these alerts immediately email or do they need to be active for some = time?Thanks,Jos=C3=A9= On Apr 24, 2024 at 09:47:19, = "Donor, John" = wrote:I = definitely see an alert from yesterday for microNotTalking? I'm not sure = what timestamp we should be looking for.Did no one else get that email? = It looks like it went to the list but I get emailed directly as well so = there might be an issue with the list.On Apr 24, 2024 11:44 AM, John via = sloan-25mlog = wrote:[EXTERNAL EMAIL = WARNING] DO NOT CLICK LINKS or open attachments unless you recognize the = sender and know the content is safe.On 4/24/24 10:38 AM, Kaike = via sloan-25mlog wrote:>>> On Apr 24, 2024, at = 10:14=E2=80=AFAM, John = wrote:>>>> The physical connections appear to be = ok.>>>> Before we do something like unplug them to = clean the contacts, can you tell me if this is happening outside of = observing time as well? Obviously we wouldn't see a netburner = problem while not observing, but we would see camcheck connection = problems. Before assuming this is a connection trouble, lets = establish that it happens during the day also.> This happened = during days also well, but not recently. This happened last time is a = couple of weeks ago.Any similar connection issues with the = specmech?>>>> Either I'm no longer on the alerts = email list, or alerts no longer sends out emails. No clue which, = so much has changed since 2020. In previous surveys I would have = been well aware of camcheck problems just from the alerts = emails.> Not sure what changed, sounds like most people don=E2=80=99= t receive this particular alert on MicroNotTalk. I am including John = Donor in the email so he and Jose can comment on this.I'm not sure I = see any alert emails at all.>> = -Kaike>>>> John>>>> On = 4/24/24 9:11 AM, Kaike wrote:>>>> On Apr 24, 2024, at = 6:14=E2=80=AFAM, Conner via sloan-25mlog = wrote:>>>>>>>>>>>> &n= bsp; &nbs= p; APACHE POINT = OBSERVATORY SDSS = 2.5M>>>>>>>> = &n= bsp; &nbs= p; OBSERVING = LOG>>>> &nb= sp;  = ; Tuesday April 23, = 2024>>>>>>>> = &n= bsp; &nbs= p; (SJD = 60424)>>>>>>>> ---- Observing Team = ---->>>>>>>>>>>> Conner = Scoresby>>>>>>>> ---- Observing Plan = ---->>>>>>>>>>>> Tue 23 = Apr 2024 60424 1.00 = 02:36 02:52 11:10 09:59 = 18:18 Day bright ( 9.3 = h)>>>>>>>> ---- Observing Summary = ---->>>>>>>> Another excellent and = efficient night for observing from the = queue.>>>>>>>> = Notes:>>>>>>>> 1. Another Netburner = issue around 03:00Z>>> Once again, the event is associated = with a broader communication issue, the SP1MicroNotTalking issue: = alert=3DcamCheck.SP1MicroNotTalking, ok, "at 2024-04-24 03:19:06 UT = found 'Reported by camCheck'", enabled, noack, = -1>>>>>> Can the network switch, media = converter, and cables for SP1 communication be checked = out?>>>>>> = Thanks,>>>>>> -Kaike>>>> = ____________________________________________________________> = Logs of Nightly APO Activities >= ; https://ur= ldefense.com/v3/__https://trac.sdss.org/tracmailman/browser/private/sloan-= 25mlog/index.html__;!!K6Z8K8YTIA!AZ6YvOGL-odqvU7J-mRp7WhaeJig4MdlKkIXGGDxJ= 7-K-hi3wsOTCuE4qlV-t9zDFwtvjawrAR6-Rw1C9vtp$______________________= ______________________________________Logs of Nightly APO Activities = https://ur= ldefense.com/v3/__https://trac.sdss.org/tracmailman/browser/private/sloan-= 25mlog/index.html__;!!K6Z8K8YTIA!AZ6YvOGL-odqvU7J-mRp7WhaeJig4MdlKkIXGGDxJ= 7-K-hi3wsOTCuE4qlV-t9zDFwtvjawrAR6-Rw1C9vtp$_____________= _______________________________________________Logs of Nightly APO = Activities https://urlde= fense.com/v3/__https://trac.sdss.org/tracmailman/browser/private/sloan-25m= log/index.html__;!!K-Hz7m0Vt54!gljVnVcNf37YfTucgMLpuV4ecLHR3LhWAxnJhUwbQ33= 4OxvO-NbRvuO3FdaR6mEmoO8UusRsiWTgSXui$________________________________________________= ____________ Logs of Nightly APO Activities https://tra= c.sdss.org/tracmailman/browser/private/sloan-25mlog/index.html ____________________________________________________________Logs of Nightly APO = Activities https://trac.sdss.org/tracmailman/browser/private/sloan-25mlo= g/index.html= --Apple-Mail=_131D56A4-534A-4A09-A738-EF07E17D4775--