Up to 10 attachments (including images) can be used with a maximum of 52.4 MB each and 262.1 MB total.
Sep 01, 2016 at 05:40 AM
This message means, that the AMD did not receive any packet yet. The AMD is considered as fully started when it gets at least one packet for analysis.
We are experiencing the samme issue. We've verified that AMD is receiving packets on the capture interfaces, but still this issue, Any pointers?
As the AMD custom driver is filtering out packets not meant for analysis, you must ensure that either the AMD has Autodiscovery enabled or has some user defined software services configured and sees traffic for those software services.
You are right, Wojciech. Turning auto discovery on certainly proved that the only, so far, Software Service defined was configured with the wrong port. Thank you for your support.
Sep 29, 2016 at 06:12 AM
Sep 29, 2016 at 03:01 PM
To add on this its not always necessary that by Auto-Discovery you will get it working , we also needs to ensure the traffic we are receiving is IP TRAFFIC and if not this has to be look by N/W team.
Learn how Dynatrace Real User Monitoring automatically detects errors that impact your end users caused by erroneous 3rd party or CDNs.December 12, 4:00 pm CET / 10:00 am ETRegister here
Answers and Comments
17 People are following this question.
How can I delete expired and unused SSL encryption keys from our AMD?
More Operations After Setting Up URL Monitoring
Help in Diagnosing Sequence Number Gap Rate issue
AMD protocol analyzer
Symptom of no SSL keys/wrong SSL keys vs the symptom of wrong analyzer