Closed agardnerIT closed 8 months ago
It is taking shape...
This will require a new flag in tracepusher which allows users to specify a custom start time. This is something @Dant3s discussed a while ago. A HAR downloaded a month ago will thus result in a trace being sent with a start time of "a month ago" (be aware because you'll need to search for that in your backend).
All pertinent request / request information will be able to be added as span attributes.
It is anticipated that there will be flags to enable / disable verbose items like headers and cookies (which could blow up your backend storage) - so we give you the option of sending or not.
Edit: Documentation is here.
Alpha version available for testing!
host.docker.internal
points to your localhost so this command assumes your OpenTelemetry collector is running on http://localhost:4318
(adjust as necessary)har-to-otel
but can be configured with --service-name my-service-name
--timings false|true
will add / remove timing information as span attributes (default: true
)--request-headers true
will add request headers as span attributes (default: false
)--response-headers true
will add response headers as span attributes (default: false
)--request-cookies true
will add request cookies as span attributes (default: false
)--response-cookies true
will add response cookies as span attributes (default: false
)--debug true
enables debug mode--dry-run true
enables dry run modedocker run \
--mount type=bind,source="$(pwd)",target=/files \
gardnera/har-to-otel:dev \
-f /files/YOUR-HAR-FILE.har \
-ep http://host.docker.internal:4318 \
--insecure true
Code is available here
This issue has had significant traffic and views. No reports of broken functionality. HAR to OTEL tool will be released w/ tracepusher v0.10.0 and will always be released alongside tracepusher. Therefore, the first version of the HAR to OTEL tool will be 0.10.0
Build a HAR to OTEL trace tool