Configuring rolling releases with OTEL metrics not on Vercel

(edited)

I’m currently looking into implementing rolling releases with my application, but use a different observability platform (dash0) to track my metrics. In the rolling releases docs, it states to propagate the deployment ID to my observability platform, but not how I would be able to distinguish the ID’s from each other since there is no ENV (to my knowledge) to determine canary vs the base deployment.

Is there a recommended way on how to distinguish between canary and the base deployment? Would it be utilizing webhooks and storing/tracking the base deployment id vs the canary deployment id?

Vercel Alum

Hi ! We automatically add the deployment ID in log drains and trace drains so you don’t need to propagate anything to Dash0 (see the trace drains reference here on what we send).

To figure out the deployment ID of your canary and current production deployments, you can visit the Deployments page of your Vercel project and find the IDs there. Let me know if that helps!

Understood it would be ideal if we propagated a label or tag stating current prod and canary so you don’t need to actually manually look up the specific deployment ID.

Ah ok so would basically need to filter in dash0 manually by checking the deployment ids and comparing them correct? Propagating a label/tag would have to be something custom in my workflow?

Vercel Alum

Hey there, ! Just checking in to see if you still need help with filtering deployment IDs in Dash0 or if you found a solution. Let me know!

This topic is closed. It no longer accepts new replies.