Elasticsearch Audit should not rely on sequence for logentry id

The cost of an external sequence for the an entry id is high.

It is commons to log hundreds of events in a row, this create an ES bulk insert command but each entry need an id cost hudnreds of roundtrip with ES (or Redis depending on the sequence impl).

A fist step is to see how much we rely on logentry id to be sequence.

The possible solution are:

• using an uuid
• rely on ES automatic id generation
• use a timestamp + Nuxeo node id
• extend sequence service to reserve block of sequence
  ...