Skip to content

Agent Discovery improvement suggestions/discussion #467

@yuhusolutions

Description

@yuhusolutions

Hi,

the current impl of JolokiaDiscoveryMBean.java is based on Multicast using datagram packets.
This practice, while still relevant in certain context, do not age well over time. Yet the need for autodiscovery is more and more relevant in a microservice environment.

Have you shared some thoughts regarding the possibility to provide other type of discovery implementation(s), not relying on datagram, complementary to the existing one?

For instance, a DNS based implementation would provide a good alternative for scenarios when all the IP occurrences of a replica are registered under a single CNAME.
E.g. A K8s headless service will register every pod IP under the common CNAME.


Otherwise (or in addition), providing a clean way to plug a custom IMPL of JolokiaDiscoveryMBean would enable to extend Jolokia to solutions that already have service registry (such as spring-cloud-service-discovery-server/client).

The only way I found, is to re-register another impl of the MBean at runtime under the same object name.
Maybe I missed something.

Hugo

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions