Spring Library To Potentially Log and Store Every API request? (majumdartanmay.github.io)

submitted 1 year ago by [email protected] to c/[email protected]

1 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[-] [email protected] 3 points 1 year ago

The article makes a good job of explaining the requirement but it doesn't actually explain why expanding OTEL to support a jdbc exporter is not the best solution. Other than "it's not straightforward".

Tracing is not as trivial as it seems and I would be warry of rolling out a bespoke solution.

A few questions that come to mind:

what do you mean when you say the traces should be "stateless"?
why a SQL database? Traces typically have evolving schemas
why can't this be done with a straightforward Filter implementation?

this post was submitted on 09 Jul 2023

4 points (100.0% liked)

Java

1327 readers

1 users here now

For discussing Java, the JVM, languages that run on the JVM, and other related technologies.

founded 1 year ago

MODERATORS

[email protected]