Flink’s REST API including metrics is usually exposed on port 8081. However, depending on your Flink setup, the metrics might not be exposed or could be listening on a different port. Verify the actual port and path in your Flink configuration ( flink-conf.yaml) and make sure its what you’ve set in the OTEL receiver.

Check that the version of the OpenTelemetry Collector you’re using is compatible with your Flink version. The flinkmetrics receiver may have specific version requirements or may behave differently based on the Flink version

Look into the logs of the OpenTelemetry Collector for any error messages related to the flinkmetrics receiver. It will often provide clues. If running on Kubernetes, you can fetch the logs using

kubectl logs <otel-collector-pod-name>

Validate your OpenTelemetry Collector configuration thoroughly. Make sure there are no syntax errors and that all required fields are properly set. Also, check that the service name is correctly set if needed elsewhere in your configuration.

Check for network issue between the OpenTelemetry Collector and your Flink service. If both are running in the same EKS cluster, they should be able to communicate using the DNS name service running in the same local cluster. However, network policies, security groups, or other network configurations could still interfere.

Depending on the version of the OpenTelemetry Collector you’re using, the configuration format or available options for the flinkmetrics receiver might have changed. So you want to make sure you are configuring according to the correct versions.

These are some things you can check. Good luck resolving it!