-
Notifications
You must be signed in to change notification settings - Fork 5
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
feat: egress tracker middleware (#120)
### Egress Tracker Middleware **Summary:** This PR introduces an egress tracking middleware for the Freeway project, enabling accurate measurement and recording of egress data for served content. The middleware tracks the bytes sent in each response body and logs them with the accounting service tied to each content ID (CID). **Key Changes:** - **Egress Middleware (`withEgressHandler`)**: - Wraps response handlers to track and count bytes sent to the client. - Controlled by the `FF_EGRESS_TRACKER_ENABLED` feature flag, enabling or disabling egress tracking as needed. It is disabled by default. - **Accounting Service Integration**: - Logs egress data with the accounting service, using either an `ACCOUNTING_SERVICE` from the context or a new instance based on the `ACCOUNTING_SERVICE_URL` environment variable. - Egress data is linked to the CID of the served content, ensuring precise tracking. (The actual accounting service implementation, integrating `w3up-client` for the new `usage/record` capability, will follow in a separate PR.) - **Efficient Byte Counting via `TransformStream`**: - Utilizes a `TransformStream` (`createEgressPassThroughStream`) to passively count bytes in the response body without altering content. - On stream completion, the `flush` method records total egress to the accounting service using `ctx.waitUntil()` for non-blocking calls. **Error Handling**: - Logs errors encountered during data streaming and halts byte counting without interrupting the original response chain. This ensures resilience even in cases of partial or interrupted streams. **Testing**: - Added thorough tests to validate egress recording across scenarios, including complete responses, interrupted streams, and error cases. **Next Steps**: - Integration tests for verifying egress tracking accuracy and accounting service interactions in various streaming conditions (planned for a future PR). - `w3up-client` integration to execute the new `usage/record` capability in subsequent development.
- Loading branch information
Showing
10 changed files
with
596 additions
and
23 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,92 @@ | ||
import { Accounting } from '../services/accounting.js' | ||
|
||
/** | ||
* @import { Context, IpfsUrlContext, Middleware } from '@web3-storage/gateway-lib' | ||
* @import { Environment } from './withEgressTracker.types.js' | ||
* @import { AccountingService } from '../bindings.js' | ||
* @typedef {IpfsUrlContext & { ACCOUNTING_SERVICE?: AccountingService }} EgressTrackerContext | ||
*/ | ||
|
||
/** | ||
* The egress tracking handler must be enabled after the rate limiting handler, | ||
* and before any handler that serves the response body. It uses the CID of the | ||
* served content to record the egress in the accounting service, and it counts | ||
* the bytes served with a TransformStream to determine the egress amount. | ||
* | ||
* @type {Middleware<EgressTrackerContext, EgressTrackerContext, Environment>} | ||
*/ | ||
export function withEgressTracker (handler) { | ||
return async (req, env, ctx) => { | ||
if (env.FF_EGRESS_TRACKER_ENABLED !== 'true') { | ||
return handler(req, env, ctx) | ||
} | ||
|
||
const response = await handler(req, env, ctx) | ||
if (!response.ok || !response.body) { | ||
return response | ||
} | ||
|
||
const { dataCid } = ctx | ||
const accounting = ctx.ACCOUNTING_SERVICE ?? Accounting.create({ | ||
serviceURL: env.ACCOUNTING_SERVICE_URL | ||
}) | ||
|
||
const responseBody = response.body.pipeThrough( | ||
createByteCountStream((totalBytesServed) => { | ||
// Non-blocking call to the accounting service to record egress | ||
if (totalBytesServed > 0) { | ||
ctx.waitUntil( | ||
accounting.record(dataCid, totalBytesServed, new Date().toISOString()) | ||
) | ||
} | ||
}) | ||
) | ||
|
||
return new Response(responseBody, { | ||
status: response.status, | ||
statusText: response.statusText, | ||
headers: response.headers | ||
}) | ||
} | ||
} | ||
|
||
/** | ||
* Creates a TransformStream to count bytes served to the client. | ||
* It records egress when the stream is finalized without an error. | ||
* | ||
* @param {(totalBytesServed: number) => void} onClose | ||
* @template {Uint8Array} T | ||
* @returns {TransformStream<T, T>} - The created TransformStream. | ||
*/ | ||
function createByteCountStream (onClose) { | ||
let totalBytesServed = 0 | ||
|
||
return new TransformStream({ | ||
/** | ||
* The transform function is called for each chunk of the response body. | ||
* It enqueues the chunk and updates the total bytes served. | ||
* If an error occurs, it signals an error to the controller and logs it. | ||
* The bytes are not counted in case of enqueuing an error. | ||
*/ | ||
async transform (chunk, controller) { | ||
try { | ||
controller.enqueue(chunk) | ||
totalBytesServed += chunk.byteLength | ||
} catch (error) { | ||
console.error('Error while counting bytes:', error) | ||
controller.error(error) | ||
} | ||
}, | ||
|
||
/** | ||
* The flush function is called when the stream is being finalized, | ||
* which is when the response is being sent to the client. | ||
* So before the response is sent, we record the egress using the callback. | ||
* If an error occurs, the egress is not recorded. | ||
* NOTE: The flush function is NOT called in case of a stream error. | ||
*/ | ||
async flush () { | ||
onClose(totalBytesServed) | ||
} | ||
}) | ||
} |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,6 @@ | ||
import { Environment as MiddlewareEnvironment } from '@web3-storage/gateway-lib' | ||
|
||
export interface Environment extends MiddlewareEnvironment { | ||
ACCOUNTING_SERVICE_URL: string | ||
FF_EGRESS_TRACKER_ENABLED: string | ||
} |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.