EIS/Advanced config for EVAM

Besides default configuration for EVAM described here, some additional configuration are required to enable EVAM to interact with other EIS services.

Config section

In addition to the config parameters described in default configuration, few additional config parameters are needed for EIS deployment.

• "cert_type": "grpc", required so that ConfigMgrAgent can generate certificates for EVAM. These certificates are volume mounted at [EIS_WORKDIR]/IEdgeInsights/build/Certificates/EdgeVideoAnalyticsMicroservice_gRPC

Interfaces

EVAM in EIS deployments communicates with other EIS services using secured gRPC communication. These services must be added in Interface/Clients section list of the configuration.

Here’s a sample interface having Visualizer microservice in its client configuration.

{
    "config": {
    ...

    },
    "interfaces": {
        "Clients": [
            {
                "EndPoint": "multimodal-data-visualization-streaming:65138",
                "Name": "visualizer",
                "Topics": [
                    "edge_video_analytics_results"
                ],
                "Type": "grpc",
                "overlay_annotation": "true"
            }
        ]
    }
}

• "Endpoint" refers to container name and the port where gRPC client is running. When in "network_mode": "host", use IP address instead of container name

• "Types": lists communication protocol. only "grpc" is supported

• "Topics": list of topic name(s). An identifier where messages are coming from. Legacy term from previously supported pub-sub communication.

• "overlay_annotation": Defaults to "false". When set to “true”, it fetches annotation metadata from supported udfs and overlays the annotation on the image frame before publishing. Ensure, the UDF has "visualize"="false", else it would be redundant, and published frames would have annotations regardless.