Recommendations to others considering IOpipe:
Consider using the trial for a short period of time with functions that are mature/stable. This will provide time to learn all the features of IOpipe without trying to determine if there is a bug on your side or lack of knowledge integrating with IOpipe.
During the trial, examine your code to determine if features of IOpipe can be leveraged to reduce your code footprint. Things like alerting during exception handling consume many lines of code and these are good candidates for IOpipe handling.
Definitely leverage the support structure of IOpipe using Slack. They are highly responsive and have the agility to solve problems quickly. Their principals are actively involved with the support community and will jump in as needed to expedite a resolution. Don't wait, just ask and you will see the rapid response provided. Review collected by and hosted on G2.com.
What problems is IOpipe solving and how is that benefiting you?
During normal DevOps you are always trying to answer questions about application performance. Sometimes it is the code, sometimes the infrastructure. With IOpipe we are able to monitor executing code and our test/validation scripts to quickly isolate issues. There is no need to go searching through the various logs to find the needle in the haystack.
One additional benefit is by leveraging the built-in logging, labeling and alerting we have been able to remove more than half of all function code that was performing a similar purpose. This allows the functions to rightly focus on performing the task(s) without the overhead of self-watch routines to alert on certain operational conditions. This has greatly reduced the complexity of functions, reduced overhead and reduced the financial impact of functions during runtime. Review collected by and hosted on G2.com.
