Is the Nx Cloud up? Visit our Status Page for the current health and performance of the Nx Cloud.

Status Page

Migrating from Nx Metadata SDK 5.1 to 6.0 — Concerns & Questions

Answered

Comments

1 comment

  • Ichiro
    • Network Optix team

    Hi Subramanian

     

    1. Metadata Format Migration

    • How challenging is the transition from JSON to Protobuf in practice?
    • Are official .proto definitions available for common object/event types, or is custom definition required?
    • Do you have any recommendations for converting existing nlohmann::json C++ logic to Protobuf?

    Currently, we do not utilize gRPC or Protocol Buffers. Our analytics API, for example, expects JSON, as do all other endpoints we are aware of. Therefore, we are unable to provide answers to these questions as these technologies are not integrated into our product.

    2. Injection Mechanism Changes

    • Is gRPC now the preferred method for metadata injection, or is HTTP POST still supported for backward compatibility?
    • For plugin-side injection, what is the recommended approach for streaming Protobuf metadata to the server?

    We currently use JSON-RPC and do not employ gRPC or Protobuf. Both HTTP and JSON-RPC are supported in parallel, ensuring no backward compatibility concerns.

     

    3. Plugin Architecture

    • Are there significant changes in plugin registration or lifecycle management?

    As far as we know, there are no major changes. Please refer to the release notes for further details: https://meta.nxvms.com/download/other/betas#6.1.0.41495

    • Are there any known difficulties when adapting existing C++ plugins to the new SDK headers and Protobuf dependencies?

    Again, as we do not use Protobuf, we cannot provide an answer to this question.

     

    4. Deployment & Compatibility

    • Is SDK 6.0 backward-compatible with Nx Witness 5.x clients?

    In general, backward compatibility is possible. However, if you are developing with SDK 6.0, some features may not be available on older clients. It is generally not straightforward to expect a newer SDK version to support new features on an older client version. Therefore, while generally compatible, this is not an ideal solution.

    Additionally, please note that troubleshooting plugin issues developed with SDK 6.0 on a 5.x client is not supported. As a guideline, we strongly recommend using the same version of the SDK and Desktop Client in all cases to ensure proper compatibility and support.

    • Are there any known issues with ARM builds or edge deployment workflows?

    No, there are no known issues.

     

    5. Testing & Debugging

    • What tools or strategies are used to validate Protobuf metadata injection?
    • Are there any sample plugins or test harnesses for 6.0 that would be helpful for getting started?

    We do not use gRPC or Protobuf.

    • Are insights, migration tips, sample code, online meetings, or educational resources available and required?

    Samples are available within the MetaSDK, which also provides STUB samples for various usages.

     

    We are unsure where you obtained information regarding these changes, as there appears to be a misunderstanding, or significant clarification is required for such an assumption. To reiterate, we do not currently utilize gRPC or Protobuf.

     

    Hope this helps.
    Thanks.

    0

Please sign in to leave a comment.