Logdna-Mezmo Name Change

[Piponater]

Hi,

What is the future/plan in the naming of the LogDNA-agent/repo etc with the Mezmo name change? Understandably, I'm sure many have Logdna setup via Infrastructure as code and within a lot of automation, which would require changes if its name were to change to mezmo-agent for example?

Thanks,

Pritesh

[dkhokhlov]

Hi Pritesh We will announce any changes we make beforehand and will give customers ample time to make any necessary changes.

[deepy]

@dkhokhlov there's a short notice in the readme about the name change but would it be possible to clarify it? Specifically: will the package change name from logdna-agent to mezmo-agent? Will 3.7 include both logdna-agent and mezmo-agent?

I'm hoping to avoid a situation where an old scripted logdna-agent install starts failing because the binary changed name.

[gjanco]

Hi @deepy, that is a good question. We are working out the details now so that impact to the customer is minimal. In the intervening 3.x releases we will add the necessary tools to make this transition easy.

We are working out the details of this plan and will attach the final plan to this issue. In the meantime, rest assured we will not make a breaking change to the agent - until we reach the 4.0 release. So as long are you are using the 3.x version you can continue on un-interrupted.

[deepy]

I think an ideal transition here is to make 3.7 contain both binaries but with the agent mentioning the deprecation when invoked and whenever a deprecated environment variable is used. And then stop publishing new logdna-agent packages, and start publishing packages as mezmo-agent. Ideally with a 3.7 with both binaries as well, but just a 3.8 or 4.0 would also work