# Elapsed plugin missing start events
**URL:** https://discuss.elastic.co/t/elapsed-plugin-missing-start-events/109848
**Category:** Logstash
**Created:** [November 30, 2017, 10:29pm UTC](https://discuss.elastic.co/t/elapsed-plugin-missing-start-events/109848 "2017-11-30T22:29:52Z")
**Posts on this page:** 2
**Page:** 1
### Author:  [@joconner](https://discuss.elastic.co/u/joconner)
#### Post date: [November 30, 2017, 10:29pm UTC](https://discuss.elastic.co/t/elapsed-plugin-missing-start-events/109848/1 "2017-11-30T22:29:52Z")
Processing potentially several thousands of events per second, the `elapsed` filter plugin seems to miss about 10% of my start/end tagged events. The tag message I often see in the "end" events is `elapsed_end_without_start`.
Maybe you have a suggestion for why I'm missing start events? Here's the relevant logstash filter:
```auto
filter {
csv {
separator => ","
columns => ["timestamp", "environment", "program", "pid", "dbcode", "event", "resource_type", "primary_id", "secondary_id", "action"]
}
date {
match => ["timestamp", "ISO8601"]
}
if [resource_type] == "timecard" and [resource_id] {
if [event] =~ /BEGIN$/ or [event] =~ /END$/ {
mutate {
add_field => {
"transaction_id" => "%{resource_id}_%{environment}_%{pid}"
}
add_tag => ["%{event}"]
}
elapsed {
start_tag => "CALC_FOO_BEGIN"
end_tag => "CALC_FOO_END"
unique_id_field => "transaction_id"
timeout => 600
}
elapsed {
start_tag => "CALC_BAR_BEGIN"
end_tag => "CALC_BAR_END"
unique_id_field => "transaction_id"
timeout => 600
}
elapsed {
start_tag => "CALC_BAZ_BEGIN"
end_tag => "CALC_BAZ_END"
unique_id_field => "transaction_id"
timeout => 600
}
}
}
}
```
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [December 28, 2017, 10:30pm UTC](https://discuss.elastic.co/t/elapsed-plugin-missing-start-events/109848/2 "2017-12-28T22:30:16Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.