>>> [!note] Migrated issue <!-- Drupal.org comment --> <!-- Migrated from issue #3329681. --> Reported by: [rr404](https://www.drupal.org/user/3739954) >>> <h3 id="summary-problem-motivation">Description</h3> <p>Some good practice on sending signals : <a href="https://doc.crowdsec.net/docs/next/getting_started/install_softagent#your-signals">https://doc.crowdsec.net/docs/next/getting_started/install_softagent#your-signals</a></p> <ul> <li>The module should allow to push/addSignals easily</li> <li>Signal should come from security modules or plugins listening to security events and generating signals form them</li> <li>A helper is available in CrowdSec's SDK to generate signals</li> <li>The Module could already embed signal generation from existing core security modules like "flood"</li> <li>When Pushing a new kind of signal we should add it to the list of subscribed ones</li> <li>Signals should be buffered before pushed for an optimal usage of the API: every 10 secondes for example by batches of 1 to 250signals</li> </ul> <p>It's important to validate with CrowdSec the scenario names for those signals in order for them to be validated by CrowdSec's expert system</p>