| ▲ | tgv 2 days ago |
| Am I reading correctly that your software generates 25 million error messages per day? |
|
| ▲ | xmodem 2 days ago | parent | next [-] |
| Sentry does a lot more than tracking errors - presumably most of those transactions are 'breadcrumb'-style events. |
|
| ▲ | Weryj a day ago | parent | prev | next [-] |
| Nope, 25M transactions. In Sentry a transaction is more like an OTEL-trace.
Errors are much lower ;) |
| |
| ▲ | almd a day ago | parent [-] | | sorry if this is a silly question, the quick google search didn’t give me clues. Transactions like full user flows start to finish, or 1 transaction = 1 post/get and 1 response? | | |
| ▲ | Volundr a day ago | parent [-] | | > Transactions like full user flows start to finish, or 1 transaction = 1 post/get and 1 response? For most applications we are talking closer to 1 transportation 1 web request. Distributed tracing across microservices is possible, the level of extra effort required depends on your stack. But that's also the out of the box, plug and play stuff. With lower level APIs you define your own transactions, when they start and end, which is needed for tracing applications where there isn't a built in framework integration (e.x not a web application). |
|
|
|
| ▲ | pebble 2 days ago | parent | prev [-] |
| That is more likely performance traces or session replays. |
