You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
refactor!: polish logging across the codebase (#1005)
### Description
Logging polish across the whole codebase:
- Fix typos & grammar
- Unify logger usage
- Remove useless debug logs
- Rebalance a few log levels
### Breaking changes
The typed public API is unchanged, but log output changes in a few minor
ways:
- `error` -> `warning` for the local no-op `metamorph()` / `reboot()` /
`add_webhook()` messages and the Scrapy scheduler skip.
- `info` -> `debug` for the "unknown platform event" message.
- Internal logger names changed from `apify` to `apify.<module>` for the
charging, proxy, and events modules.
The typed public API is unchanged, so your code keeps working without edits. Only log output changes. Adjust your setup if you parse logs, route them by logger name, or assert on log records, for example in tests.
252
+
253
+
### Rebalanced log levels
254
+
255
+
- The local no-op messages from `Actor.metamorph()`, `Actor.reboot()`, and `Actor.add_webhook()`, logged when the Actor runs outside the Apify platform, are now `warning` instead of `error`. The Scrapy scheduler message for a request that can't be converted to an Apify request changed the same way.
256
+
- The "unknown platform event" message is now `debug` instead of `info`.
257
+
258
+
### Module-qualified logger names
259
+
260
+
The charging, proxy, and events modules now log under their own child loggers (`apify._charging`, `apify._proxy_configuration`, and `apify.events._apify_event_manager`) instead of the generic `apify` logger. These child loggers still propagate to `apify`, so a handler attached to `apify` keeps receiving their records. Update only configuration that targets the exact `apify` logger name for these messages.
0 commit comments