Please add support for more user configurable index names in the bwlogreceiver, in particular allow using destination index names to not have a datetime stamp in them. Instead it would be 'bwlogs-alias' or some other user configurable string. Implementing this would allow users to leverage the power of the rollover API and pass control of the index names to Elasticsearch. This is beneficial in larger deployments with lots of logs as it would ensure that the shard size does go above a predefined limit, especially in times of unusually activity when log out put maybe increased. The rollover API will make sure that any given index does not grow above a preconfigured size.
Please add support for more user configurable index names in the bwlogreceiver, in particular allow using destination index names to not have a datetime stamp in them. Instead it would be 'bwlogs-alias' or some other user configurable string. Implementing this would allow users to leverage the power of the rollover API and pass control of the index names to Elasticsearch. This is beneficial in larger deployments with lots of logs as it would ensure that the shard size does go above a predefined limit, especially in times of unusually activity when log out put maybe increased. The rollover API will make sure that any given index does not grow above a preconfigured size.