We're looking at the 502 errors - this is not a sensor disabling issue. Resource-wise our internal monitoring shows the server healthy and responsive. Are you still having this problem?
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
Show posts MenuQuote from: RES217AIII on January 19, 2025, 04:59:58 PMI have the same problem
Is this possibly the answer to the problem?
https://community.emergingthreats.net/t/etpro-telemetry-edition/2355
"For sensors opting-in to sending Proofpoint/ET telemetry so they can receive ETPRO telemetry edition those sensors must have sent event telemetry back to Proofpoint/ET within the last 5 days.
Sensors may go dormant during that period (no heartbeat sent in the last day) and still receive ETPRO Telemetry Edition, but if no events are received for 5 days the Telemetry Edition rule delivery will be disabled and that sensor will simply receive that day's ET Open rules.
That disabling will transition back to active delivery upon resumption of heartbeat and telemetry delivery back to Proofpoint/ET.
Sensors are reviewed as to state every 24 hours."