Management of event lanes¶

Event lanes can be modified and deleted by a user.

Modifying event lanes¶

Event lanes can be modified in the Library declaration /EventLanes/tenant/eventlane.yaml. For example, different parsing rules can be selected for that data stream, or it can be provided with a new set of dashboards.

Read more about event lane declarations here.

Deactivating and deleting event lanes¶

Event lanes can be deactivated and deleted.

Deactivating an event lane¶

To deactivate an event lane, follow these steps:

Stop all instances of LogMan.io Parsec by setting the number of instances in the event lane declaration to zero:
```
parsec:
  instances: 0
```
Ensure all LogMan.io Parsec instances are stopped and removed in the Maintenance > Services section.
Inactivate the event lane by changing the define/type option in the event lane declaration:
```
define:
  type: lmio/event-lane-inactive
```
Stop the LogMan.io Elman instance to prevent it from creating a new event lane. Stop all instances of LogMan.io Receiver as well.
```
docker stop lmio-receiver-1
docker stop lmio-elman-1
```

Enter the Kafka Docker container. Manually delete the received and events topics of the event lane you want to remove.

docker exec -it kafka-1 bash
/bin/kafka-topics --bootstrap-server localhost:9092 --delete --topic received.tenant.stream
/bin/kafka-topics --bootstrap-server localhost:9092 --delete --topic events.tenant.stream

Restart LogMan.io Elman.
```
docker restart lmio-elman-1
```
Perform a rollover in Elasticsearch for the event lane index.
```
POST /lmio-tenant-events-stream/_rollover
```
Delete the Discover data source for the event lane in Configuration >> Discover >> lmio-tenant-events-stream.
If you want to only inactivate the event lane but keep its data, restart all instances of LogMan.io Receiver. If you want to delete the event lane and its data, continue further.
```
(node-1) $ docker restart lmio-receiver-1
(node-2) $ docker restart lmio-receiver-2
(node-3) $ docker restart lmio-receiver-3
```

Deleting an inactive event lane¶

Stop all instances of LogMan.io Receiver. Go to Zoonavigator, open lmio/receiver/db, and delete the record of the data stream.
Ensure that the Kafka topics received and events are deleted. Delete the event lane declaration in the Library /EventLanes/tenant/stream.yaml.
If you want to delete the event lane data, read further. If not, restart all instances of LogMan.io Receiver.

Warning

After an event lane is deleted, no data is deleted from the Archive or Elasticsearch database, but it cannot be accessed from the TeskaLabs LogMan.io web application.

Deleting event lane data¶

Danger

Deleting data from TeskaLabs LogMan.io is possible, but strongly not recommended.

Open Kibana >> Stack Management >> Index Management. Delete all indices starting with lmio-tenant-events-stream.
Open Kibana >> Stack Management >> Index Management >> Index Templates. Delete the index template starting with lmio-tenant-events-stream.
Open Kibana >> Stack Management >> Index Lifecycle Policies. Delete the ILM starting with lmio-tenant-events-stream.

Ensure all instances of LogMan.io Receiver are stopped. Delete all stream data from the hot, cold, and warm phases on all cluster nodes.

rm -rfv /data/ssd/lmio-receiver-x/hot/<stream>
rm -rfv /data/hdd/lmio-receiver-x/warm/<stream>
rm -rfv /data/hdd/lmio-receiver-x/cold/<stream>

Restart all instances of LogMan.io Receiver.