[Metering] During plan update send start event after stop event (#1890)

* During plan update the metering start event was sent before to metering stop event. As a result many instances after plan update got missing from the metering (escaped from charging).
* To fix this issue we have fixed the code to send stop event first and then start event during plan update also made sure that there is a gap 1 ms between each event.

webhooks/pkg/webhooks/manager/event.go

@@ -5,6 +5,7 @@ import (
 	"encoding/json"
 	"errors"
 	"fmt"
+	"time"
 
 	"github.com/cloudfoundry-incubator/service-fabrik-broker/webhooks/pkg/apis/instance/v1alpha1"
 	instanceclient "github.com/cloudfoundry-incubator/service-fabrik-broker/webhooks/pkg/client/clientset/versioned/typed/instance/v1alpha1"
@@ -230,8 +231,10 @@ func (e *Event) getMeteringEvents() ([]*v1alpha1.Sfevent, error) {
 		if err = e.validateOptions(oldAppliedOptions); err != nil {
 			return nil, err
 		}
-		meteringDocs = append(meteringDocs, e.getMeteringEvent(options, c.MeterStart, c.UpdateEvent))
 		meteringDocs = append(meteringDocs, e.getMeteringEvent(oldAppliedOptions, c.MeterStop, c.UpdateEvent))
+		// Sleep for 1 ms to make sure that timestamp of both stop and start events are not same.
+                time.Sleep(1 * time.Millisecond)
+		meteringDocs = append(meteringDocs, e.getMeteringEvent(options, c.MeterStart, c.UpdateEvent))
 	case c.CreateEvent:
 		if err = e.validateOptions(options); err != nil {
 			return nil, err