DMARC analytics services are expensive and aren’t really meant for individual use. Why not build one myself, now that we live in a world where Claude Code is so powerful? So I did.
Introducing DMARC Dashboard Kit.
Dev tips when making a Cloud Run service
- You can identify if your service is running on a Knative platform like Cloud Run by looking for the
K_SERVICEenvironment variable.
https://docs.cloud.google.com/run/docs/container-contract#env-vars - When connecting to Cloud SQL, you should switch to IAM authentication and only use a connection string as a local fallback. Set a
CLOUD_SQL_INSTANCEvariable only in the deploy environment, and your application can detect this and use@google-cloud/cloud-sql-connector.
https://docs.cloud.google.com/sql/docs/mysql/connect-connectors#node.js - Correlate your container logs with a request log (services only)
By default, container logs are not correlated with request logs. To link them without a client library like@google-cloud/logging, write a structured JSON log containing alogging.googleapis.com/tracefield with the trace identifier extracted from theX-Cloud-Trace-Contextrequest header.
https://docs.cloud.google.com/run/docs/logging#writing_structured_logs - Remember that Cloud Run is a serverless service, meaning instances can be scaled down at any time. If required, install a
SIGTERMhandler in your application to receive a warning when Cloud Run is about to shut down an instance. You will have a 10-second window to react.
https://docs.cloud.google.com/run/docs/container-contract#instance-shutdown - Cloud Run uses an in-memory file system, so every file you write to the instance is actually consuming your instance’s memory.
- Outbound network connections from Cloud Run can occasionally be terminated, either due to timeout or infrastructure restarts. If your application reuses long-lived connections, we recommend configuring it to re-establish connections to avoid reusing a dead connection.
- Cloud Run injects a
PORTenvironment variable and expects your application to listen on it. Do not hardcode a port number (e.g. 8080); always read fromprocess.env.PORTinstead.