📄️ Use your own PostgreSQL
Store Putki execution logs in a PostgreSQL database you already operate instead of the one in the monitoring bundle.
📄️ Use your own Grafana
Add the Putki execution monitoring dashboards to a Grafana you already run, by import or by provisioning.
📄️ Monitor projects in the Putki stack
Execution monitoring when you run the full Putki compose stack - what is already there and how to connect your own projects.
📄️ Expose Grafana safely
Make the monitoring Grafana reachable for your team - TLS, public URL, login and read-only access.
📄️ Get alerts in Slack or Google Chat
Be told in Slack or Google Chat when a run fails, takes much longer than usual, is still running long after its usual time, writes no rows or an unusual number of rows, or reports a refused login.
📄️ Forward logs to Loki, OpenSearch or Splunk
Send the logs of the Hop and Putki containers to your own log platform or SIEM - Grafana Loki, OpenSearch or Splunk - with the Grafana Alloy overlay in the monitoring bundle.
📄️ Sign in with Google, Microsoft or your SSO
Let your team sign in to the monitoring Grafana with Google, Microsoft Entra ID or any OpenID Connect provider, with roles from a list of addresses.
📄️ Upgrade or remove monitoring
Move to a newer monitoring bundle, or take execution monitoring out of a project.
📄️ Manage log volume
Keep the execution logging database from growing without limit - what grows, how to record less, and how to delete old runs.
📄️ Troubleshoot
Fix the common problems with Putki execution monitoring - no data, missing runs, connection and login failures - and what to send when you need help.