Skip to content

Logging should have a prefix #149

@stanislavkozlovski

Description

@stanislavkozlovski

Today, (in debug, since that's what I use) the library logs arbitrary stuff like:

consumer exited.

queueing: {'properties': {'..., '$lib': 'posthog-python', '$lib_version': '3.7.2', '$geoip_disable': True}, 'timestamp': '2024-11-29T13:25:36.143687+00:00', 'context': {}, 'distinct_id': '019362b1-37ca-7e98-bb6a-0c9c54c1b99a', 'event': '...'}

enqueued [event].

making request: {"batch": ..."}, "$lib": "posthog-python", "$lib_version": "3.7.2", "$geoip_disable": true}, "timestamp": "2024-11-29T13:25:36.143687+00:00", "context": {}, "distinct_id": "019362b1-37ca-7e98-bb6a-0c9c54c1b99a", "event": "..."}], "historical_migration": false, "sentAt": "2024-11-29T13:25:36.536523+00:00", "api_key": "..."}

data uploaded successfully

In any regular app, this is easy to confuse with the regular application logs. And more importantly - it's hard to tell apart when you want to debug posthog specifically.

It would be great if the logger had some set prefix.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions