Specification Adherence: Capture Heroku Context
https://devcenter.heroku.com/articles/dyno-metadata
We'd love to see this!
At the moment, our logs get a hostname of a random uuid. Not certain if this is the dyno's UUID or not. But what we'd really like is to filter by dyno name (i.e. web.1, from the DYNO env var). Then we can see if there's more than one physical dyno that may have had that dyno name during the time period, like if it was due to a restart, using the UUID in HEROKU_DYNO_ID.
Is there a straightforward way to add this ourselves, or does it need to come from the library?
HI @bgentry thanks, and noted! We're about to release a big update across all of our libraries. As part of QA we'll be verifying specification adherence which will include this. Thanks for your patience. I'll update this issue as soon as it's released.