You might be able to achieve this with versioning - http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/docs-index_.html#index-versioning
Regards, Mark Walkom Infrastructure Engineer Campaign Monitor email: [email protected] web: www.campaignmonitor.com On 2 October 2014 05:20, Brian Wilkins <[email protected]> wrote: > In Splunk, it is possible to detect tampering of logs. Splunk will take > an event at ingestion time and create a hash value based on the event and > your certificates/keys. You can then write searches that will re-hash the > event to be compared to the original to indicate if anything has changed. > We need something like that. > > How is that possible with elasticsearch? > > -- > You received this message because you are subscribed to the Google Groups > "elasticsearch" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/elasticsearch/3b724745-88ac-4484-9d21-284ec28697a9%40googlegroups.com > <https://groups.google.com/d/msgid/elasticsearch/3b724745-88ac-4484-9d21-284ec28697a9%40googlegroups.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CAEM624Y2mu13pfoQRvcEngY%3DZ3JvXNqrT%2Bc05q3HV3EaOZmrtg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
