Bringing context to alerting and incident management
About this episode
While FireHydrant is mostly known for their incident management software, they’re introducing Signals to modernize alerting and consolidate it with incident management.
FireHydrant was born out of an incident where a database was dropped at 5:30pm on a Friday right before network maintenance started. It also led to Robert’s social media handle, Bobby Tables.
This one time…at band camp…Robert got paged in the middle of trumpet practice…on his sabbatical.
Congrats to Great Question badge winner timdim for asking How can I flush GPU memory using CUDA (physical reset is unavailable)?. 100 people thought it was worth voting for.
See Privacy Policy at https://art19.com/privacy and California Privacy Notice at https://art19.com/privacy#do-not-sell-my-info.
Get every episode summarized
Each time The Stack Overflow Podcast publishes, we email you a written briefing from the transcript — the topics, who appeared, and any specific claims, with the ad reads skipped.
Email me new episodesFree for 3 shows. No card needed.
No transcript yet
This episode has not been transcribed. Request it and it moves to the front of the queue.
More episodes
More from The Stack Overflow Podcast
Connecting the dots for accurate AI
The Stack Overflow Podcast
AI giveth and AI taketh CPU
The Stack Overflow Podcast
What (un)exactly do you mean by semantic search?
The Stack Overflow Podcast
Time is a construct but it can still break your software
The Stack Overflow Podcast