# Kibana Custom Visulaization Session Object

**URL:** <https://discuss.elastic.co/t/kibana-custom-visulaization-session-object/198532>\
**Category:** Kibana\
**Created:** [September 8, 2019, 3:08am UTC](https://discuss.elastic.co/t/kibana-custom-visulaization-session-object/198532 "2019-09-08T03:08:39Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![adityaPsl](https://avatars.discourse-cdn.com/v4/letter/a/e47c2d/32.png) [@adityaPsl](https://discuss.elastic.co/u/adityaPsl)\
**Post date:** [September 11, 2019, 3:46pm UTC](https://discuss.elastic.co/t/kibana-custom-visulaization-session-object/198532/4 "2019-09-11T15:46:45Z")

</div>

Hello Team,

As explained in [Solving Concurrency Issues](https://www.elastic.co/guide/en/elasticsearch/guide/current/concurrency-solutions.html#document-locking) , i am thinking of creating a transaction

user 1 logs in opens UI -\> get lock using API  
`PUT /fs/lock/<index_name>/_create { "lock_type": "exclusive" }`

user1 will perform operations like update/delete etc

and releases lock using API  
`DELETE /fs/lock/<index_name>`

If any other user logs in and tries to access the UI the lock API will try to acquire the lock on the same index but will get error since other user has already acquired an exclusive lock(Checked this by executing APIs from Kibana Dev Tools).

To test the scenario i need to implement it Kibana custom visualization, to understand how can i execute lock APIs using CallWithRequest Client, I have opened a new topic [here]([How to call lock APIs using call with request](https://discuss.elastic.co/t/how-to-call-lock-apis-using-call-with-request/199026)

Thank you,  
Aditya

---

_[View the full topic](https://discuss.elastic.co/t/kibana-custom-visulaization-session-object/198532)._