Karim Radhouani

If I understand what you are trying to achieve correctly, I would say you don't really need delete events. All you need is knowing that a certain row in your...

I see your point, an additional tag that says `delete=true` can be added when a delete is received.

Added in v0.37.0. You can use the attribute `delete-tag: xyz` under your influxdb output. gNMIc will create entries with tag `xyz: true` for delete notifications.

My issue with implementing this is having to "guess" the unit of the original timestamp. Making it a configurable attribute (`from: ns`) feels a bit too rigid of an option...

Yes, for servers which behave according to the spec. I guess we can ignore misbehaving servers in this case.

If a target goes down you don't see log entries for retrying a subscription recreation because the underlying gRPC client connection needs to be reestablished first. Once the gRPC client...

@ddidziz this sounds like a different issue from the original one. You do see the connection getting reestablished, but no data being available on the output. Do you see data...

Yes it was added just for the default "json" format. I don't see where if would fit in the event format, could you explain how you intend to use it...

The merge by tags is the equivalent of group-by processor.

@bpchoi How would you see deletion to work with a cli origin? The semantics of deletion should be part of the cli command. There is not much sense into using...