You may not see data flow into the Elastic Stack right away; that’s normal. The addition of a pod annotation does not trigger an automatic restart. Therefore, existing pods will will not be affected by the APM Attacher. Only new pods—​as they are created via the natural lifecycle of a Kubernetes deployment—​will be instrumented. Restarting pods you’d like instrumented manually will speed up this process, but that workflow is too specific to individual deployments to make any recommendations.