Testing PINPOINT 3.0.3 with mirrored production applications

[snmsmanager]

Hi,

We are currently using Pinpoint 2.5.x in production with hundreds of application servers, including Kubernetes-deployed microservices.

We’ve set up a Pinpoint 3.0.3 staging cluster with Pinot support, and we want to test our existing production application servers against this new 3.0.3 cluster without changing or restarting the agents. To do this, we mirror all TCP packets for selected agents (ports 9991, 9992, 9993) to the new 3.0.3 collector.

What we see:

Spans are successfully stored in the staging cluster’s HBase tables (ApplicationTraceIndex, TraceV2).

However, ApplicationIndex and AgentInfo rows are not created for those applications.

Details:

Port 9992 (span data) → correctly populates ApplicationTraceIndex & TraceV2.

Port 9991 (agent handshake + metadata) → does not populate AgentInfo or ApplicationIndex.

Because of this, we can’t see the application map in Pinpoint Web for these mirrored applications.

If we restart the production application, then ApplicationIndex and AgentInfo records are created and the application map becomes visible in the 3.0.3 cluster.

Question:
Is there any method, configuration, or workaround to re-register applications in Pinpoint 3.0.3 (populate ApplicationIndex and AgentInfo) without manually restarting the applications / agents?

Thanks in advance!

[emeroad]

When migrating to another HBase instance, data migration or replication may be required for metadata-related tables.

https://hbase.apache.org/book.html#hbase.replication.management

Exclude data tables such as ApplicationTraceIndex and TraceV2,
and replicate only critical metadata like AgentInfo.

Similarly, there are also approaches like CopyTable or Snapshot and Export