This topic was automatically generated from Slack. You can find the original thread here.
Has Pipedream thought of implementing app level service disruption detection and visibility?
- When a Component Developer first integrates an app, have some sort of logic they can implement to check the status of the app’s API(Plenty of products have Status pages or status APIs). Could automatically run this logic periodically?
- If a certain threshold is hit for failing API requests that aren’t client level errors of a certain app platform wide for all customers, then you can know the third party app is having some sort of outage unrelated to Pipedream’s infrastructure.
Why?
If I have extremely critical operations failing due to a third party service, I don’t have visibility of that automatically. Of course I can use my brain a bit and figure it out by looking into it, but it’s hard when integrating Pipedream for someone else who isn’t as technical. I know people who have stopped using Pipedream even though it was a third party service they were using with downtime because they thought it was Pipedream’s problem. Off to a competitor or custom integration they go 
A simple notification along failed runs or somewhere in the UI when you are building a workflow there could be a tiny blurb on the app saying something like “This app is currently experiencing downtime unrelated to Pipedream aka not Pipedreams fault” with a link to that third party apps Status page if they have one.
Just a thought.
