Keep your existing Python logging. Add two lines. Sentry turns raw noise into a clear dashboard: service health, anomalies, and concrete next actions.
# install once\npip install sentry-logger\n\n# init\nfrom sentry_logger import init\ninit()\n\n# your logs stay the same\nimport logging\nlogging.error("payment gateway timeout")\n
Per-service health, risk, and drift without changing your logging style.
Query incidents in plain language and get concise, actionable answers.
features
Tight surfaces, clear hierarchy, and a workflow that respects how developers actually debug.
Stay ahead of outages. Sentry surfaces changes in behavior early and points to the logs that justify it.
Track each microservice separately. Compare baselines, spot regressions, and route incidents faster.
"Why is auth failing?" becomes a short answer plus the exact log lines that support it.
Get notified when a service shifts from stable to suspicious, before users report it.
No new logging calls. No invasive instrumentation. Keep control of your code.
how it works
You shouldn’t need a week of setup to see what’s broken.
One dependency. No agents.
pip install sentry-logger
CLI authenticates and provisions keys.
sentry-logger init --app-name "my-api"
Two lines at startup.
from sentry_logger import init init()
Sign in with Google, connect your first app, and see health summaries immediately.