Back to videos

Shoreline on Shoreline: Alarms & Actions for Release Testing

Hear from Senior Director, Haritha Gongalore, on how rewarding it is to use Shoreline Alarms and Actions to test and certify our own releases.
1 min
play_arrow
Summary

In order to succeed, we understand that innovating to meet the needs of our loyal users is a must. And there's no better way to understand their POV outside of becoming a customer ourself! Hear from Shoreline Senior Director of Engineering, Haritha Gongalore, on how rewarding it is to use Shoreline Alarms and Actions to test and certify our own releases.

We use Shoreline Alarms and Actions in our release certification testing.

For example, we monitor memory usage of various subsystems, and when they breach a certain threshold, an alarm is raised.

A bot is then triggered and collects all the debugging information to record it for later analysis.

We find this to be a very effective technique at debugging spikes in memory usage.

It is very rewarding when you can use your own product to make it even better.

Transcript

View more Shoreline videos

Looking for more? View our most recent videos
3 min
How to Manage Failure without Wasting Resources
How can you better utilize the resources you keep aside for failover purposes? Here's how we utilized resources kept just for failover purposes to do things that could be stopped for some time when a failure happens and had resources doing useful background activity that can be deferred to when things hit the fan.
2 min
Risks of Automation vs. Human Errors
Automation is risky. Errors in the remediation code could worsen an outage. While that’s true, we also know that human error causes 5x more incidents than automation. You can fix code. You can't fix people.
4 min
How to Solve the Challenges of MELT Data at Scale
The bigger the data set, the slower it is to analyze. For MELT, you need to be able to execute a query at scale across your fleet and see what's going on in the live environment. That’s why, at Shoreline, we favor modeling the distributed system as a distributed system.