# Updating Start Event Using Elapsed Plugin After Stop Event Received
**URL:** https://discuss.elastic.co/t/updating-start-event-using-elapsed-plugin-after-stop-event-received/57051
**Category:** Logstash
**Created:** [August 2, 2016, 8:07pm UTC](https://discuss.elastic.co/t/updating-start-event-using-elapsed-plugin-after-stop-event-received/57051 "2016-08-02T20:07:19Z")
**Posts on this page:** 2
**Page:** 1
### Author:  [@camiller](https://discuss.elastic.co/u/camiller)
#### Post date: [August 2, 2016, 8:07pm UTC](https://discuss.elastic.co/t/updating-start-event-using-elapsed-plugin-after-stop-event-received/57051/1 "2016-08-02T20:07:19Z")
Hi,
I am using the elapsed plugin to calculate the elapsed time between start and stop events. I am interested in visualizing start events that are currently running (do not yet have stop events). I have not been able to find a way to visualize this in Kibana. If it's possible that would be my preferred solution, to track events by their elapsed id which have start but not matching stop events.
I am currently looking to solve this problem by tweaking the configuration of the elapsed filter in the logstash config file. Is there a way to add or remove tags to the start event after the end event has been found? The plugin supports adding and removing tags but I need to figure out how to do so with events that already exist. Any help would be really appreciated!
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [July 6, 2017, 4:45am UTC](https://discuss.elastic.co/t/updating-start-event-using-elapsed-plugin-after-stop-event-received/57051/2 "2017-07-06T04:45:13Z")