Skip to content

[Request]: Clarify APM server status #3979

Closed as not planned
Closed as not planned

Description

What documentation page is affected

On https://www.elastic.co/guide/en/apm/server/index.html, APM Server is described as 'legacy'. This documentation seems to have been deprecated from 8.x.

On https://www.elastic.co/guide/en/observability/current/apm-getting-started-apm-server.html, the 'standalone' APM server binary, and fleet-managed APM server (running within an Elastic Agent) are positioned as equals.

However, after setting up a 'standalone' APM server, Kibana says:

You are currently using APM Server binary. This legacy option is deprecated since version 7.16 and is being replaced by a managed APM Server in Elastic Agent from version 8.0.

I assume "managed APM Server in Elastic Agent" refers to a "fleet-managed APM server".

What change would you like to see?

The situation described above is incredibly confusing: the two options are positioned as equals, but after setting up the standalone option, Kibana marks it as deprecated, which is mentioned in now deprecated documentation, but it's impossible to tell whether 'standalone' APM server binary is something different than 'legacy' APM server...

The status of APM server install options should be clarified.

Additional info

No response

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions