Skip to content

separate the data from the app, for generalized data. #62

@thinkocapo

Description

@thinkocapo

Basically, it would be nice to be able to pass any kind of data into this (i.e. not just Sentry event data). Right now, event-to-sentry.go assumes it's nothing bunch a sentry event object.

Would be cool if you could define this through Structs & Interfaces in a separate file, this way it would be more generalized. Then monetize it. How? No idea. Run this all in the Cloud (SaaS) and make it easy to replay your own traffic and customize the traffic (update the data), let users publish their own data sets to it. Or that could be overkill.

compare/contrast feature sets to:
https://www.soapui.org/http-recording/http-recording/
https://mockmotor.com/blog/record-and-mock-http-traffic/
https://www.telerik.com/fiddler/web-traffic-recording
https://www.http4k.org/cookbook/record_and_replay/
https://github.com/Netflix/pollyjs
https://learning.postman.com/docs/postman/sending-api-requests/capturing-http-requests/

I def saw some solutions that allow you to store offline the traffic and replay, but did not allow you to modify that data as you replay it. There's probably a way to hack it together with whatever existing ($) solution are out there, but at that rate you could just build your own solution (Undertaker) instead?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions