← GQ3

Clients/GQ3/slack/2026/02/2026-02-19_google.md

slack
Source
3
Chunks
9
Entities
Doc
Type

Content

# #google — 2026-02-19 **08:10 [Mason Radke](https://slack.com/archives/C0A56N14A5S/p1771517447015079):** Running a little behind this morning, but I should be ready to chat in 10 or 15 minutes if you have time **08:23 [Reno Hiltermann](https://slack.com/archives/C0A56N14A5S/p1771518234250149):** No problem. Same **08:40 [Mason Radke](https://slack.com/archives/C0A56N14A5S/p1771519216254659):** ok.. lets see.. where should we start. **08:40 [Mason Radke](https://slack.com/archives/C0A56N14A5S/p1771519227478019):** all alarms are still using the existing pipeline that you had **08:40 [Mason Radke](https://slack.com/archives/C0A56N14A5S/p1771519247756339):** so eventually we'll either need to update alarms to use the new pipeline or update the existing pipeline to use our new logic **08:42 [Reno Hiltermann](https://slack.com/archives/C0A56N14A5S/p1771519337521879):** Standby **08:44 [Reno Hiltermann](https://slack.com/archives/C0A56N14A5S/p1771519462682099):** The new pipeline will send emails only from Signl4? **08:45 [Mason Radke](https://slack.com/archives/C0A56N14A5S/p1771519535391399):** no, i dont think we have signl4 to email alert.. only text/push/call **08:45 [Mason Radke](https://slack.com/archives/C0A56N14A5S/p1771519554526899):** so on p2 (i think) the pipeline will use ignition SMTP to send email alerts **08:47 [Reno Hiltermann](https://slack.com/archives/C0A56N14A5S/p1771519643676079):** what is the pipeline called **08:48 [Mason Radke](https://slack.com/archives/C0A56N14A5S/p1771519709300699):** i called it GQ3_Signl4 but that might not be the best name since that pipeline is also sending ignition email alerts based on priority **08:51 [Reno Hiltermann](https://slack.com/archives/C0A56N14A5S/p1771519901360809):** I am looking at your pipeline. **08:52 [Mason Radke](https://slack.com/archives/C0A56N14A5S/p1771519977405619):** pretty simple.. a priority switch.. critical alarms call a webhook to signl4 which signls the P0-Critical Team **08:53 [Mason Radke](https://slack.com/archives/C0A56N14A5S/p1771519985498839):** High does the same for the P1-High Team **08:53 [Mason Radke](https://slack.com/archives/C0A56N14A5S/p1771519992683759):** (same users, just different notification methods) **08:53 [Mason Radke](https://slack.com/archives/C0A56N14A5S/p1771520000991039):** medium (p2) uses ignition email alerts **08:53 [Mason Radke](https://slack.com/archives/C0A56N14A5S/p1771520019940399):** and P3, P4 no notifications.. only on scada **08:54 [Reno Hiltermann](https://slack.com/archives/C0A56N14A5S/p1771520050781849):** I want emails on P0 and P1. So need a splitter on those **08:54 [Mason Radke](https://slack.com/archives/C0A56N14A5S/p1771520073811109):** gotcha.. let me see if signl4 can do email alerts as well.. that might simplifiy.. or we just do a splitter **08:55 [Reno Hiltermann](https://slack.com/archives/C0A56N14A5S/p1771520102335209):** Splitter is fine with me. Just wanted to make sure we had emails. **08:55 [Mason Radke](https://slack.com/archives/C0A56N14A5S/p1771520108766639):** copy **08:57 [Reno Hiltermann](https://slack.com/archives/C0A56N14A5S/p1771520241480439):** Can you please make a local backup of Ignition **08:57 [Mason Radke](https://slack.com/archives/C0A56N14A5S/p1771520260888079):** yes **08:58 [Mason Radke](https://slack.com/archives/C0A56N14A5S/p1771520287956069):** done **08:58 [Mason Radke](https://slack.com/archives/C0A56N14A5S/p1771520290492579):** and in the downloads folder **08:58 [Mason Radke](https://slack.com/archives/C0A56N14A5S/p1771520322497249):** splitter is done **08:59 [Reno Hiltermann](https://slack.com/archives/C0A56N14A5S/p1771520351567179):** Let's get the P0 and P1 items changed over to the new pipeline **08:59 [Mason Radke](https://slack.com/archives/C0A56N14A5S/p1771520388867759):** ok. i'll go through the spreadsheet and get them updated **09:00 [Mason Radke](https://slack.com/archives/C0A56N14A5S/p1771520407313679):** do we want to do a final test? especially since we added the splitter and made some changes **09:02 [Reno Hiltermann](https://slack.com/archives/C0A56N14A5S/p1771520520158739):** Let's wait and do your plan. **09:02 [Reno Hiltermann](https://slack.com/archives/C0A56N14A5S/p1771520530268369):** How do we test **09:02 [Reno Hiltermann](https://slack.com/archives/C0A56N14A5S/p1771520545548299):** First we should delete the other users on Signl4 **09:02 [Mason Radke](https://slack.com/archives/C0A56N14A5S/p1771520560564859):** so i have a P0-Test team with just me in it **09:02 [Mason Radke](https://slack.com/archives/C0A56N14A5S/p1771520571405409):** and P1-High is new.. so it also jsut has me in it **09:03 [Mason Radke](https://slack.com/archives/C0A56N14A5S/p1771520582658099):** using those two teams for testing **09:03 [Reno Hiltermann](https://slack.com/archives/C0A56N14A5S/p1771520596819669):** If you are confident using those, go ahead :+1: **09:03 [Mason Radke](https://slack.com/archives/C0A56N14A5S/p1771520634098169):** go ahead for a function test? **09:03 [Reno Hiltermann](https://slack.com/archives/C0A56N14A5S/p1771520639692689):** Yes **09:04 [Mason Radke](https://slack.com/archives/C0A56N14A5S/p1771520643992549):** copy. standby **09:05 [Reno Hiltermann](https://slack.com/archives/C0A56N14A5S/p1771520706398659):** On a separate note, feel free to reorganize the ALARM_LIST sheet. My JLL WebCTRL technician did that and I hate how he does spreadsheets. **09:05 [Mason Radke](https://slack.com/archives/C0A56N14A5S/p1771520715246449):** haha **09:05 [Mason Radke](https://slack.com/archives/C0A56N14A5S/p1771520715883639):** k **09:06 [Reno Hiltermann](https://slack.com/archives/C0A56N14A5S/p1771520798712169):** Also, on that sheet Low/High is LOLO, HIHI. Low/High warning is LO/HI. **09:06 [Mason Radke](https://slack.com/archives/C0A56N14A5S/p1771520806200159):** the way the pipeline is setup now, everyone will get an email in the P0 All Hands Roster **09:07 [Mason Radke](https://slack.com/archives/C0A56N14A5S/p1771520823066539):** should we change that? **09:07 [Reno Hiltermann](https://slack.com/archives/C0A56N14A5S/p1771520847236179):** Good catch. **09:07 [Mason Radke](https://slack.com/archives/C0A56N14A5S/p1771520858908069):** make a new temp roster to just email us? **09:07 [Mason Radke](https://slack.com/archives/C0A56N14A5S/p1771520862614079):** to confirm function **09:08 [Reno Hiltermann](https://slack.com/archives/C0A56N14A5S/p1771520885148859):** Yes **09:08 [Mason Radke](https://slack.com/archives/C0A56N14A5S/p1771520889996219):** k **09:13 [Reno Hiltermann](https://slack.com/archives/C0A56N14A5S/p1771521229259719):** I am afk. If needed call me **09:14 [Mason Radke](https://slack.com/archives/C0A56N14A5S/p1771521241034299):** sounds good.. let me know when you're back. **09:22 [Reno Hiltermann](https://slack.com/archives/C0A56N14A5S/p1771521758606139):** I think maybe there is a better way to do this change. **09:22 [Mason Radke](https://slack.com/archives/C0A56N14A5S/p1771521769500609):** which change specifically? **09:23 [Reno Hiltermann](https://slack.com/archives/C0A56N14A5S/p1771521787031689):** pipeline per alarm **09:23 [Mason Radke](https://slack.com/archives/C0A56N14A5S/p1771521831377009):** we could incorporate our changes into the existing pipeline, then we wouldnt have to touch every alarm **09:24 [Reno Hiltermann](https://slack.com/archives/C0A56N14A5S/p1771521872836589):** right. am i missinga negative consequence **09:25 [Mason Radke](https://slack.com/archives/C0A56N14A5S/p1771521908993349):** we wouldnt know if every alarm uses that pipeline.. and we would still need to touch every alarm to make sure its severity is set correctly **09:25 [Mason Radke](https://slack.com/archives/C0A56N14A5S/p1771521947423459):** (did you get text/push/email?) i triggered a P1 test **09:27 [Reno Hiltermann](https://slack.com/archives/C0A56N14A5S/p1771522048937889):** i think. on road **09:27 [Mason Radke](https://slack.com/archives/C0A56N14A5S/p1771522054857979):** k **09:30 [Mason Radke](https://slack.com/archives/C0A56N14A5S/p1771522213339539):** you ok if i trigger a P0 alarm (it will only notify us, but you'll get a call) **09:36 [Reno Hiltermann](https://slack.com/archives/C0A56N14A5S/p1771522568703249):** yes **09:36 [Reno Hiltermann](https://slack.com/archives/C0A56N14A5S/p1771522572759829):** got call **09:36 [Mason Radke](https://slack.com/archives/C0A56N14A5S/p1771522592586599):** our setup is working great **09:36 [Mason Radke](https://slack.com/archives/C0A56N14A5S/p1771522614149149):** when you have time, we just need to decide if i should go through the spreadsheet and check/update each alarm **09:37 [Mason Radke](https://slack.com/archives/C0A56N14A5S/p1771522624879399):** or just update the existing pipeline **09:39 [Reno Hiltermann](https://slack.com/archives/C0A56N14A5S/p1771522768526919):** Let's just update P0 for today. **09:40 [Reno Hiltermann](https://slack.com/archives/C0A56N14A5S/p1771522806032759):** I have some bigger plans for the UDTs and standardizing some other issues I created :upside_down_face: **09:41 [Mason Radke](https://slack.com/archives/C0A56N14A5S/p1771522878248869):** haha ok. i'll go through the spreadsheet and get those alarms on the new pipeline and make sure the severity is set to P0. in signl4 and also the igntion email roster are we only using the users you have listed? **09:44 [Reno Hiltermann](https://slack.com/archives/C0A56N14A5S/p1771523077930409):** Signl4 yes. Emails I have to check. Might want to add some others. **09:45 [Mason Radke](https://slack.com/archives/C0A56N14A5S/p1771523121855069):** ok, it doesnt look like these users are in signl4 yet? are we removing all the existing users and inviting this new group? **09:45 [Reno Hiltermann](https://slack.com/archives/C0A56N14A5S/p1771523135407859):** Yes. **09:46 [Reno Hiltermann](https://slack.com/archives/C0A56N14A5S/p1771523202817009):** Maintenance team decided to use their existing WebCTRL system only. Huge mistake. Their server for all SOCAL crashed last night :upside_down_face:. Took 5 hours to recover. **09:48 [Mason Radke](https://slack.com/archives/C0A56N14A5S/p1771523339839519):** yikes.. ok to confirm.. im removing signl4 users, and sending out invites to the new users. will you work with them to verify they got the app installed and logged in? **09:49 [Reno Hiltermann](https://slack.com/archives/C0A56N14A5S/p1771523354546309):** Correct. **10:56 [Reno Hiltermann](https://slack.com/archives/C0A56N14A5S/p1771527397858009):** can you call **10:56 [Mason Radke](https://slack.com/archives/C0A56N14A5S/p1771527415517059):** yeah. **11:24 [Mason Radke](https://slack.com/archives/C0A56N14A5S/p1771529062612599):** ![[F0AGUU8JXME_screenshot_2026-02-19_at_11.22.47___am.png]] **11:24 [Mason Radke](https://slack.com/archives/C0A56N14A5S/p1771529064329249):** P0 OXYGEN_SENSORS O2-1 Low Oxigen O2-2 Low Oxigen O2-3 Low Oxigen O2-4 Low Oxigen **11:25 [Mason Radke](https://slack.com/archives/C0A56N14A5S/p1771529105557499):** i see 4 alarms configured here from the UDT. is this the Low oxygen alarm that we want to be P0? **11:25 [Mason Radke](https://slack.com/archives/C0A56N14A5S/p1771529128339029):** @Reno Hiltermann this can wait if you're still driving **11:31 [Mason Radke](https://slack.com/archives/C0A56N14A5S/p1771529516068909):** ![[F0AGDKHUF33_image.png]] **11:32 [Mason Radke](https://slack.com/archives/C0A56N14A5S/p1771529540188529):** down below for P1 i also see low oxygen.. i wonder if P1 is the Low alarm, and P0 is the Low Low.. just need to confirm the tags **11:32 [Mason Radke](https://slack.com/archives/C0A56N14A5S/p1771529567756929):** in fact having a hard time identifying the other tags as well, we may need to discuss briefly when you are free. **11:34 [Reno Hiltermann](https://slack.com/archives/C0A56N14A5S/p1771529657170799):** refer to 906am. **11:34 [Mason Radke](https://slack.com/archives/C0A56N14A5S/p1771529689199109):** haha. thanks. **11:34 [Mason Radke](https://slack.com/archives/C0A56N14A5S/p1771529698854859):** brain doing too many things at once **11:35 [Reno Hiltermann](https://slack.com/archives/C0A56N14A5S/p1771529702727699):** All good **11:35 [Mason Radke](https://slack.com/archives/C0A56N14A5S/p1771529708622659):** will still need help finding the right tags **11:35 [Reno Hiltermann](https://slack.com/archives/C0A56N14A5S/p1771529731589529):** Having a hell of a time with pharmacy/doctor. In a bit of a mood.... **11:35 [Mason Radke](https://slack.com/archives/C0A56N14A5S/p1771529748685649):** that happens **11:36 [Mason Radke](https://slack.com/archives/C0A56N14A5S/p1771529795080719):** i can always shift gears, but i dont want to leave the alarms in a spot with no notifications.. i guess email will continue to work **11:45 [Mason Radke](https://slack.com/archives/C0A56N14A5S/p1771530305678949):** I can work on this anytime today or tonight, but will be unavailble tomorrow - sunday. When you have time, lets touch base to see how we want to leave the system for the weekend. no rush, take your time. **20:32 [Reno Hiltermann](https://slack.com/archives/C0A56N14A5S/p1771561966757139):** Sorry, I had some meetings then never responded. I will troubleshoot tomorrow, and the emails are sensing me texts through Zapier. So next week it is unless I get an answer from technical support. **20:33 [Mason Radke](https://slack.com/archives/C0A56N14A5S/p1771562011231949):** no problem!! reach out anytime, if i can help.. lets get it polished up next week

Extracted Entities

TypeKeyValueConfidenceEvidence
site SOCAL server SOCAL server 80% Their server for all SOCAL crashed last night ... Took 5 hours to recover
system SCADA product Ignition 100% the pipeline will use ignition SMTP to send email alerts
task Test alarm notifications Perform function test on P0 and P1 alarm notifications using test teams 100% so i have a P0-Test team with just me in it ... using those two teams for testing
task Signl4 user management Remove existing Signl4 users and invite new group; verify app installation 100% im removing signl4 users, and sending out invites ... will you work with them to verify they got the app installed
task Update alarms to new pipeline Update P0 alarms to new pipeline and check severity 100% Let's just update P0 for today ... i'll go through the spreadsheet and get those alarms on the new pipeline
task Backup Ignition Make a local backup of Ignition 100% Can you please make a local backup of Ignition ... done
task Alarm notification configuration Decide on email recipients for P0 All Hands Roster and create temp roster 90% everyone will get an email in the P0 All Hands Roster ... make a new temp roster to just email us?
task Confirm alarm severity tags Confirm P0 and P1 alarm tags for low oxygen alarms 90% P0 is the Low oxygen alarm ... P1 is the Low alarm ... just need to confirm the tags
task Spreadsheet reorganization Reorganize ALARM_LIST sheet for clarity 80% feel free to reorganize the ALARM_LIST sheet ... I hate how he does spreadsheets
File: Clients/GQ3/slack/2026/02/2026-02-19_google.md
Updated: 2026-02-20 04:45:21.130176