Any recommendations for an API Monitoring solution that can be triggered post deployment from Seed.run ?

We use Epsagon and it's very good. Although not triggered post deployment, the Epsagon config is created at build time and it's then always on

Yes we use Lumigo for ongoing monitoring and tracing of the Lambda functions. But, Lumigo doesn’t have the ability to do external API Testing, ie. every T minutes, send request X, check that response = Y; if not, send alert notification. @Ross Coundon can you do that in Epsagon? I didn’t think so but maybe I overlooked something

Ah, no. I guess you could set up an endpoint that calls a lambda which in turn calls the necessary endpoints in the seed Post deployment step

Everytime I think to do that, I realize there are 5-10 companies with SaaS solutions that do that. e.g. postman, checkly, moesif, uptrends just to name a few. However, it can get expensive if you want to do checks every few minutes for many functions. What I was thinking about was a way to set up ongoing monitoring, at a low frequency, say every hour to save cost; but to force trigger an “API check” post deployment. It’s the last bit which seems hard to find a solution for.

Depending on what kind of error you're looking for, if you have your monitoring setup in Lumigo then by triggering a cUrl command to the API in seed.yml( after_deploy hook ) or in the seed post deployment phase, Lumigo should alert if there's a problem. You could also send the curl result somewhere

set up dashbird recently and it was a very easy set up process that just monitors everything by default

Thanks @Bec Martin. seems in the same family as Lumigo and Epsagon