v1.6.0

Improved plugin behavior. Now default plugins that may come from extended packages like @iopipe/config can be overridden. Plugins specified in package.json configurations should also work as well.

Features

• Improved plugin loading behavior

v1.5.0

• Adds .iopiperc RC file configuration
• Adds extends config package configuration

Configuration Additions - Employ Cosmiconfig

Features

We are adding even more ways to configure the iopipe agent through the use of cosmiconfig!

You can now specify .iopiperc or iopipe.config.js files along with package.json files for maximum flexibility to specify your plugins and options.

Enhanced configuration options

Configuration ++

We're opening up how you can configure iopipe through the addition of package.json config. Check the Readme for details!

Breaking Changes

None

Function timeout bugfix

Bug fixes

• Fix bug in the timeout feature, detailed here

Chores

• Add enabled flag for schema and associated tests

Async hooks support and end timestamp collection

In this release, we add support for async hooks for plugins; for example, should a plugin wish to await an external API call before closing out the invocation, this is now possible. We've also started collecting end timestamps, which will allow us to better support reporting of concurrently running functions.

Plugin reporting and async hooks

New enhancements to plugin support! We've added plugins used to the report payload for enhanced support for users leveraging plugins in their IOpipe architectures.

We've also added support for plugins to use async hooks for certain hooks – which means plugins can make asynchronous calls to say, an API, and the work will complete before the report is sent.

Add support for ap-northeast-1 region

For our friends in the ap-northeast-1, we're adding support for your region! We support 7 regions for collection, to reduce latency in telemetry reporting to our service, and bring more regions on-board to support our customers. Welcome, ap-northeast-1! 🗾

1.0 Release

Notes

At IOpipe, we've listened to your success stories and use cases for serverless. We've also heard your struggles and pain points. Throughout the process, we've honed in on features that help you and your team:

• Achieve performance gains
• Accelerate the debugging process and
• Increase the availability and observability of your applications.

We are proud to release iopipe 1.0.0, a stable, well-tested library with plenty of user validation. We want our reporting software to be performant, low-dependency, and easy to use. We feel we have hit our marks and will continue to do so as we launch even more insightful tools for your serverless architectures.
Cheers! 🍸

Breaking Changes

• None

Features

• Adds timestamp field to keep time of start of invocation
• Updates "engines" to note IOpipe supports 4.3+

Bug fixes

• Avoid thrown type errors when descriptors are undefined

Plugin Support

iopipe now supports plugins! Plugins are a way to extend the functionality of IOpipe in a piecemeal and configurable fashion.

The IOpipe team has several plugins in the pipeline, and we'd love your feedback as we beta test.
support@iopipe.com if you're interested!

We're also looking forward to learning about the plugins you create!

Breaking Change

In previous versions, the this variable available directly inside of the handler function was erroneously altered from the object you'd typically receive inside of an invocation without iopipe. This has now been rectified.

exports.handler = iopipe(HandlerIdentity(event, context){
  console.log(this)
  // {global: Object, process: Object, console: Object}
})