The normal alert mechanisms will get the 'results' stream of a search, so the summarization will hide the events stream from the alerts.
The simplest approach would be to run it again, but differently, to get the events.
Probably its slow or you wouldn't be asking this.
The smart way would probably be to have a second search run using the prior search's artifacts. However, I don't know how to have two scheduled jobs communicate such a thing.
One interesting hackable feature is the 'custom condition search' which does run precisely this way. You could have for example a search which produces your events, then you hack the summarization into the 'alert condition' follow-on (warning, 10k default event limit), have that search emit at least one result, which will fire to cause the raw events from the original search to be sent.
A particularly evil method might be to use a custom alert script, and given the path to the results file, modify it to reach the events file, and grab those.
