Per the provided Splunk reference URL
https://docs.splunk.com/Documentation/Splunk/8.0.5/Data/AboutHECIDXAck
"While HEC has precautions in place to prevent data loss, it's impossible to completely prevent such an occurrence, especially in the event of a network failure or hardware crash. This is where indexer acknolwedgment comes in." Reference https://docs.splunk.com/Documentation/Splunk/8.0.5/Data/AboutHECIDXAck

In Splunk Enterprise, license warnings occur when the daily indexing volume exceeds the licensed quota.
These warnings are tracked from midnight to midnight based on the system clock of the license manager. If the number of warnings surpasses the allowed threshold within a specified period, a license violation ensues, potentially restricting search capabilities.
To prevent a license warning from escalating to a violation, administrators have until midnight to address the issue. The recommended action is toadd a new licenseto the license manager before midnight. This increases the daily indexing volume quota, ensuring that the current day's data ingestion falls within the permissible limits.
It's important to note that deleting data from indexers or the license manager does not retroactively reduce the recorded license usage for the day. Once data is indexed, it contributes to the day's license volume, and its removal does not negate that contribution.
Reference:
About license violations - Splunk Documentation

" You can group your search peers to facilitate searching on a subset of them. Groups of search peers are known as " distributed search groups. " You specify distributed search groups in the distsearch.conf file " Reference: https://docs.splunk.com/Documentation/Splunk/8.0.5/DistSearch/Distributedsearchgroups

https://docs.splunk.com/Documentation/Splunk/9.0.0/DistSearch/Distributedsearchgroups

https://docs.splunk.com/Documentation/Splunk/7.3.0/Data/Specifyinputpathswithwildcards The ellipsis wildcard searches recursively through directories and any number of levels of subdirectories to find matches.
If you specify a folder separator (for example, //var/log/.../file), it does not match the first folder level, only subfolders.
* The asterisk wildcard matches anything in that specific folder path segment.
Unlike ..., * does not recurse through subfolders.