You mention that this change is non-breaking for metrics users. I don't
know much about protobufs backwards compatibility story. Can you detail a
little more the implications from a compatibility standpoint with this
change? Some questions:

* If I compile the new protocol via protobuf3 can I still communicate with
an old loggregator deployment?
* If I don't use the new protocol can I talk I communicate with a
loggregator that is using the new protocol? (absent the new field of course)

Thanks,
Mike

On Wed, May 11, 2016 at 8:58 AM, Jim CF Campbell <jcampbell(a)pivotal.io>
wrote:

Hopefully it's OK because you're bought into the value of tagged metrics...

On Tue, May 10, 2016 at 5:32 PM, Mike Youngstrom <youngm(a)gmail.com> wrote:

Thanks for the heads up Jim,

I use wire (https://github.com/square/wire) for a number of my
projects. Unfortunately, it appears the map<string, string> syntax is too
new for wire. Looks like I have some rewriting to do. :(

Mike

On Tue, May 10, 2016 at 3:59 PM, Jim CF Campbell <jcampbell(a)pivotal.io>
wrote:

Hi cf-dev,

In support of the epic to add tagging to CF metrics
<https://www.pivotaltracker.com/epic/show/2362529>, we recently added a
map to the dropsonde-protocol
<https://github.com/cloudfoundry/dropsonde-protocol> envelope type.
This is non-breaking to metric users. However if you compile in dropsonde,
this message applies to you. This change forced us to update to a newer
protobuf compiler. If you are using the .proto definitions directly you
will need to update to the new compiler as well. You can find the latest
protobuf compiler release on github
<https://github.com/google/protobuf/releases>.

Thanks, The Loggregator Team
--
Jim Campbell | Product Manager | Cloud Foundry | Pivotal.io |
303.618.0963

--
Jim Campbell | Product Manager | Cloud Foundry | Pivotal.io | 303.618.0963