Observe and develop serverless apps with confidence on AWS Lambda with Tracing, Metrics, Profiling, Monitoring, and more.
Home Page: https://www.iopipe.com/
License: Apache License 2.0
The gist is the version of request used by ioipie is not compatible with webpack. More background info here: request/request#1920
Migrate post-deployment (test-through) qa events funcs to agents to deploy on release+master
There are no docs in the README on this.
Currently, the report is generated inside of the report.send function.
We should separate the report generation from the report sending, and make sure that we insert the report generation in between the post:invoke and pre:report hooks.
Releasing on tags, the node coveralls package borks because it looks for git references that aren't there:
https://circleci.com/gh/iopipe/iopipe/144
Link to npm/note current agent version
Runtime reporting does not happen if emit("iopipe_event") is called by a user's code.
If we pass data to succeed (and fail etc) around this line:
https://github.com/iopipe/iopipe-js-core/blob/master/src/index.js#L176
We can allow plugins to work with the data the user intended to resolve with.
When a function is wrapped by IOpipe, and for one reason or another it cannot reach out to the data collection endpoints, the agent should not cause the function to fail with a timeout error.
In this case the IOpipe agent should exit properly so that the function can complete.
I am getting the following exception in IOpipe dashboard each time it tries to send the data, though no errors in cloudwatcg log:
Error: Timeout Exceeded.
at Timeout.<anonymous> (/var/task/node_modules/iopipe/dist/iopipe.js:851:38)
at ontimeout (timers.js:386:14)
at tryOnTimeout (timers.js:250:5)
at Timer.listOnTimeout (timers.js:214:5)
The custom metrics array is being appended to and never flushed after submitting the invocation to the IOpipe API. This array is growing and submitted on each invocation.
IOpipe duration has a small (ex. 30ms) difference between cloudwatch
On Lambda process.env.npm_package_version is not getting set and VERSION is not being set correctly.
This is helpful when using setups like SAM local where iopipe reporting generates a new function (!!) per invocation.
Proposal of an enabled flag in the agent configuration.
For better compat
so we can keep track of containers and processes we should have an id for the process (probably uuid)
I tried to integrate iopipe but haven't been able to get it working due to this error
2016-08-17T22:02:44.986Z ecac0527-64c5-11e6-99d5-09ceaa62d15a
TypeError: context.indexOf is not a function
at generateLog (/var/task/node_modules/iopipe/index.js:99:17)
at /var/task/node_modules/iopipe/index.js:213:9
I'm on lambda using the nodejs4.3 runtime.
Because we deepcopy context, the getter/setter are called for callbackWaitsForEmptyEventLoop instead of copying the getter/setter themselves. We need to preserve the getter/setter behavior such that callbackWaitsForEmptyEventLoop=false works correctly.
Rather than how much memory is used at the exit of an invocation get the max() during the invocation.
ENV vars now supported in Lambda!
report size/cost of library
also do something to make it smaller (ex. removing a dependency or two)
the vm_id should be a hex string!
"environment": {
"host": {
"vm_id": {
"type": "Buffer",
"data": [
48,
101,
102,
56,
53,
49,
48,
52,
45,
99,
50,
101,
102,
45,
52,
57,
52,
49,
45,
57,
48,
48,
51,
45,
48,
48,
100,
51,
50,
49,
50,
49,
48,
52,
57,
57
]
}
},
"os":
If the callback is not invoked, events are not submitted. We should trap this and send events before the timeout.
My index.js file looks something like this:
const iopipe = require('iopipe')({clientId: process.env.IOPIPE_CLIENTID});
module.exports.parse = (event, context, callback) => {...};
module.exports.process = (event, context, callback) => {...};
If I wrap one function into iopipe, everything works great:
const iopipe = require('iopipe')({clientId: process.env.IOPIPE_CLIENTID});
module.exports.parse = iopipe((event, context, callback) => {...});
module.exports.process = (event, context, callback) => {...};
But if I do so for both functions, I'm getting a syntax error:
const iopipe = require('iopipe')({clientId: process.env.IOPIPE_CLIENTID});
module.exports.parse = iopipe((event, context, callback) => {...});
module.exports.process = iopipe((event, context, callback) => {...});
Syntax Error -------------------------------------------
Unexpected token {
For debugging logs, run again after setting the "SLS_DEBUG=*" environment variable.
Stack Trace --------------------------------------------
SyntaxError: Unexpected token {
at new Function (<anonymous>)
at copyCollection (/dev/lambdas/node_modules/deepcopy/lib/copy.js:62:14)
at copy (/dev/lambdas/node_modules/deepcopy/lib/copy.js:17:10)
at recursiveCopy (/dev/lambdas/node_modules/deepcopy/lib/index.js:73:35)
at deepcopy (/dev/lambdas/node_modules/deepcopy/lib/index.js:35:10)
at new_context (/dev/lambdas/node_modules/iopipe/index.js:163:23)
at /dev/lambdas/node_modules/iopipe/index.js:207:17
Speaking with a user, they were not getting their logs to cloudwatch when using the debug flag. Checking, I see we specified a . instead of a _ for the response_body variable.
We can reduce the payload size by removing keys not in the schema
The following fails:
var iopipeOuter = require('iopipe')()
var iopipeInner = require('iopipe')()
export.handler = iopipeOuter(iopipeInner(
(event, callback) => { callback() }
))
I wanted to do this to perform profiling and debugging of the IOpipe library.
While working on changes to @iopipe/iopipe-plugin-profiler, I found that on timeouts post:invoke is called twice! I confirmed this by adding a console.log() in sendReport().
12:51:06
START RequestId: fd0fed0a-fbae-11e7-a3f1-859063e13748 Version: $LATEST
12:51:07
2018-01-17T17:51:07.163Z fd0fed0a-fbae-11e7-a3f1-859063e13748 Slack event:
12:51:07
12:51:07
2018-01-17T17:51:07.163Z fd0fed0a-fbae-11e7-a3f1-859063e13748 No image found in text.
12:51:07
2018-01-17T17:51:07.164Z fd0fed0a-fbae-11e7-a3f1-859063e13748 null
12:51:07
2018-01-17T17:51:07.164Z fd0fed0a-fbae-11e7-a3f1-859063e13748 sendReport called.
12:51:07
2018-01-17T17:51:07.165Z fd0fed0a-fbae-11e7-a3f1-859063e13748 PostInvoke run! 1
12:51:07
2018-01-17T17:51:07.179Z fd0fed0a-fbae-11e7-a3f1-859063e13748 invoked function context: {"callbackWaitsForEmptyEventLoop":true,"logGroupName":"/aws/lambda/slackbot-imgdesc-dev-event","logStreamName":"2018/01/17/[$LATEST]a9b3e575d58541e6bf0f190e27d88bac","functionName":"slackbot-imgdesc-dev-event","memoryLimitInMB":"512","functionVersion":"$LATEST","invokeid":"fd0fed0a-fbae-11e7-a3f1-859063e13748"
12:51:07
2018-01-17T17:51:07.427Z fd0fed0a-fbae-11e7-a3f1-859063e13748 Stopping profiling.
12:51:21
2018-01-17T17:51:21.518Z fd0fed0a-fbae-11e7-a3f1-859063e13748 sendReport called.
12:51:21
2018-01-17T17:51:21.519Z fd0fed0a-fbae-11e7-a3f1-859063e13748 PostInvoke run! 1
12:51:21
2018-01-17T17:51:21.538Z fd0fed0a-fbae-11e7-a3f1-859063e13748 invoked function context: {"callbackWaitsForEmptyEventLoop":true,"logGroupName":"/aws/lambda/slackbot-imgdesc-dev-event","logStreamName":"2018/01/17/[$LATEST]a9b3e575d58541e6bf0f190e27d88bac","functionName":"slackbot-imgdesc-dev-event","memoryLimitInMB":"512","functionVersion":"$LATEST","invokeid":"fd0fed0a-fbae-11e7-a3f1-859063e13748"
12:51:21
2018-01-17T17:51:21.600Z fd0fed0a-fbae-11e7-a3f1-859063e13748 Stopping profiling.
12:51:21
END RequestId: fd0fed0a-fbae-11e7-a3f1-859063e13748
END RequestId: fd0fed0a-fbae-11e7-a3f1-859063e13748
12:51:21
REPORT RequestId: fd0fed0a-fbae-11e7-a3f1-859063e13748 Duration: 15012.01 ms Billed Duration: 15000 ms Memory Size: 512 MB Max Memory Used: 97 MB
If promises are returned and resolved when the report is sent, consuming tools can effectively wait for the report to be sent in the cases that they need to.
We are getting a warning in iopipe console that a newer version is available but the newest version is not available on NPM
We should have acceptance tests that run on master that use the package/rc configuration options
once we add the iopipe wrapper to the lambda the serverless `invoke local` feature breaks - From a user
This repo's docs should say @iopipe/core per the name change
https://github.com/dherault/serverless-offline
[ 'SyntaxError: Block-scoped declarations (let, const, function, class) not yet supported outside strict mode',
'at Function (native)',
'at copyCollection (/git/retraced/api/node_modules/iopipe/node_modules/deepcopy/lib/copy.js:62:14)',
'at copy (/git/retraced/api/node_modules/iopipe/node_modules/deepcopy/lib/copy.js:17:10)',
'at recursiveCopy (/git/retraced/api/node_modules/iopipe/node_modules/deepcopy/lib/index.js:73:35)',
'at deepcopy (/git/retraced/api/node_modules/iopipe/node_modules/deepcopy/lib/index.js:35:10)',
'at emitter.on.context.__defineSetter__ (/git/retraced/api/node_modules/iopipe/index.js:163:23)',
'at /git/retraced/api/node_modules/iopipe/index.js:207:17' ]
used from: "iopipe": "0.0.20"
'use strict';
const iopipe = require('iopipe')({
clientId: require('./lib/config/getConfig')().IOPipe.ClientID,
});
module.exports.default = iopipe(
(event, context, cb) => {
Use stdlib https module rather than dependency
In order to be consistent with the timeout window setting, network timeout should be configurable via environment variable.
We use the serverless-mocha-plugin to run our mocha unit tests before deploying to AWS.
https://github.com/SC5/serverless-mocha-plugin
Our unit tests run locally on Jenkins.
When we wrap our lambdas in iopipe, the following exception is thrown when the unit tests are run:
Uncaught TypeError: context.getRemainingTimeInMillis is not a function
This error is coming from iopipe code, and not our code under test. This means that our unit tests fail, and Jenkins will not deploy to AWS.
At the moment, this is blocking us from using iopipe :(
Remove or update/maintain the data collected section.
User reports that calling context.getRemainingTimeInMillis() is not working as a consequence of deepcopy behavior. To be confirmed and fixed.
IOpipe believes it is seeing new functions (resulting in lots of unique functions on the IOpipe dash) when invoking using SAM local, because in each invoke SAM local is changing the AWS account ID in the ARN. Somewhat annoying, so could possibly try to detect SAM local and prevent this from happening in IOpipe data.
We read files from /proc that do not exist on non-Linux systems, breaking execution on MacOS and other operating systems when doing local dev & test.
Update README and docs to show users how to use newer config functionality
When executing a functional using SLS w/ SLS-webpack, the function fails to execute when wrapped with iopipe. It appears the agent is not auto-mocking some of the Linux based commands in this type of environment. Once the function is deployed to AWS however it works normally.
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
Django
The Web framework for perfectionists with deadlines.
Laravel
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
Microsoft
Open source projects and samples from Microsoft.
Google
Google ❤️ Open Source for everyone.
Alibaba
Alibaba Open Source for everyone
D3
Data-Driven Documents codes.
Tencent
China tencent open source team.