←back to thread

Pydantic Logfire

(pydantic.dev)
146 points ellieh | 2 comments | | HN request time: 0.472s | source
Show context
megaman821 ◴[] No.40215008[source]
Does this do logging or just traces? More to the point, is it economically to store tens of millions of log lines a month?
replies(2): >>40215035 #>>40215241 #
1. dmontagu ◴[] No.40215241[source]
I'm one of the Pydantic/Logfire devs — we are actually aiming to unify the ideas of logging and tracing a bit more than seems common in most such tools — our logfire SDK actually emits spans for all of the traditional logging statements rather than relying on OTel logging infrastructure (which seems to be kind of a legacy-oriented afterthought relative to the tracing APIs/infrastructure). So, yes, I would say we do support logging (certainly on a conceptual level), though the point is to try to move toward a world where as much as possible is done with spans, if only as an implementation detail.

We also have explicit integrations with popular logging packages (see the bottom of https://docs.pydantic.dev/logfire/integrations/#opentelemetr...), so if you use the standard library `logging` module, `structlog`, or `loguru`, you should be able to set up your logs to ship to Logfire with minimal modifications to your existing code.

While we have not announced our pricing yet, I am confident that tens of millions of log lines a month will absolutely be economical to store.

(Also, I'll just add that we also support metrics, though our metrics support is not as well-integrated yet as tracing. But soon!)

replies(1): >>40215328 #
2. laborcontract ◴[] No.40215328[source]
I was just looking for a logging service. Really enjoy Pydantic so this looks like it may be a delight.

Try not to surprise us on pricing, though.