Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/nebrius/request-inspector
A request timing diagnostic tool for Web and Node.js applications
https://github.com/nebrius/request-inspector
Last synced: about 2 months ago
JSON representation
A request timing diagnostic tool for Web and Node.js applications
- Host: GitHub
- URL: https://github.com/nebrius/request-inspector
- Owner: nebrius
- License: mit
- Created: 2018-02-01T16:33:07.000Z (over 6 years ago)
- Default Branch: master
- Last Pushed: 2023-03-04T02:34:27.000Z (over 1 year ago)
- Last Synced: 2024-07-10T18:18:23.609Z (2 months ago)
- Language: TypeScript
- Size: 643 KB
- Stars: 53
- Watchers: 4
- Forks: 2
- Open Issues: 17
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
# Request Inspector
***WARNING:*** _This software is still in beta. It is highly likely that you will encounter bugs. If you do, please file an issue on GitHub and let me know!_
Request Inspector is an HTTP(S) request diagnostic tool for Node.js servers.
When a web or mobile client makes an HTTP call to a backend, it can be tricky
to find out why that particular request took X amount of time. This is especially
true in the days of microservices, where servers make calls to servers which make
calls to other servers. How does one correlate timing information across all of
these microservices? Enter Request Inspector.
Request inspector works by adding a header to all HTTP requests that is then used
to track the request through multiple systems. Request inspector also uses continuation
local storage in Node.js to track that request through asynchronous calls locally.
This data is then sent to a special Request Inspector server which aggregates and
correlates all of this data.
Here is a screenshot showing the timeline working across three separate servers:
Be sure to [check out the example](./example).
## Installation
Request Inspector is currently split into three packages: a brwoser instrumenter, a Node.js instrumenter,
and a server. The instrumenters run inside of your web app and Node.js server, which collect
data and sends it to the server.
Start by installing the server globally:
```bash
npm install -g @request-inspector/server
```
Then install the Node.js instrumenter in your server project:
```bash
npm install @request-inspector/node-instrumenter
```
Finally, install the browser instrumenter in your client project and use [webpack](webpack.js.org),
[browserfiy](http://browserify.org/) or similar to bundle it into your application:
```bash
npm install @request-inspector/browser-instrumenter
```
Alternatively, you can [download the browser instrumenter as a single file](https://raw.githubusercontent.com/nebrius/request-inspector/master/browser-instrumenter/dist/bundle.js)
and add it with a script tag, e.g. ``.
## Usage
Start by instrumenting your Node.js application by requiring/importing the module and initializing it:
```JavaScript
const instrumenter = require('@request-inspector/node-instrumenter');
instrumenter.init({
serverHostname: 'localhost',
serverPort: 7176,
serviceName: 'template'
}, (initErr) => {
// Your app code here
});
```
Then instrument your browser application by initializing the module:
```JavaScript
const instrumenter = require('@request-inspector/browser-instrumenter');
instrumenter.init({
serverHostname: 'localhost',
serverPort: 7176,
serviceName: 'browser',
}, () => {
// Your app code here
});
```
Alternatively, if you are not using a build system, you can do:
```JavaScript
window.requestInspector.init({
serverHostname: 'localhost',
serverPort: 7176,
serviceName: 'browser',
}, () => {
// Your app code here
});
```
Then, start the server:
```bash
request-inspector [-p PORT]
```
Note: it is recommended that you run this initialization code _before_ you require/import
any other code.
Request Instrumenter will _automatically_ instrument all inbound HTTP requests for
you. You can also add more data points in your Node.js server to get a more
fine-grained look at what your application is doing (browser support pending):
```JavaScript
const templateReadEvent = instrumenter.begin('file-read');
fs.readFile('./my-file', (err, data) => {
instrumenter.end(templateReadEvent);
});
```
Each begin and end call is automatically correlated with an HTTP request that Node.js
received. Note that you _cannot_ `begin` an event that is not associated with an HTTP
request. You can use the `instrumenter.isInRequestContext()` check to see if you are
in a request context or not.
You can also add extra data associated with your event:
```JavaScript
const templateReadEvent = instrumenter.begin('file-read', {
filename: './my-file'
});
fs.readFile('./my-file', (err, data) => {
instrumenter.end(templateReadEvent, {
error: err && err.toString()
});
});
```
This information can be in any format that can be passed to `JSON.stringify`, and it
is sent to the server and shown in the UI.
To view the results, point your browser to the request-inspector server URL that you
entered in the `init` method above, e.g. `http://localhost:7176/`.
# License
MIT License
Copyright (c) 2018 Bryan Hughes
Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.