Elasticsearch Sense chrome plugin is disabled, you need to get dsl-requests written on the console

Question

I am running Google Chrome version 61.0.3163.100. Previously, I used the version of the Sense (Beta) extension 0.9.4, until Google Chrome prevented it as malware on the Extensions tab. Sense author removed it from the Chrome Store, and it was flipped to Kibana and renamed to the console.

The problem is that all the requests that I wrote in the Sense console cannot be restored due to disabling the extension. Previously, every time I opened the Sense (Beta) extension, all of my previous requests were saved and re-displayed in every session. I would like to find the file location where Sense stores my requests for redisplay.

I am running Windows 10. I tried to find my saved data by going to:

C:\Users\Admin\AppData\Local\Google\Chrome\User Data\Default\Extensions 

There is nothing identifiable that I can find that resembles my old data. Does anyone know where I can get it?

Answer 1

It seems that with the Sense extension, its only persistent data was stored in localStorage (the appropriate source ).

Whether it will be easy to recover data mainly depends on when you last used the extension.

• If you last used the extension to Chrome 61 (~ September 2017), you're in luck: the localStorage database is stored in SQLite 3 format.

  You need to find the corresponding chrome-extension_[some_id]_0.localstorage file under Local Storage in your profile; This is a SQLite database. The identifier does not seem to match the extension identifier.

  You can download it in various tools, including sqliteonline.com for the online browser.

• If you need data since upgrading to Chrome 61, you're in a much tougher situation. Chrome 61 switched to LevelDB for localStorage backend , and I couldn’t easily extract data from it.

  See this question for subtleties. The database itself is located in Local Storage/leveldb in your profile.

  It seems that Chrome does not delete old data in SQLite format, so you can recover at least data from the beginning of September.

FWIW, the extension identifier was apparently lhjgkmllcaadmopgmanpapmpjgmfcfig

Answer 2

Download this zip file from my Dropbox and follow the instructions to install it. Please run the file through antivirus to protect yourself. Thanks to this link to help me export the chrome extension.

• List item Download and unzip attachments
• Go to chrome: // extensions
• Remove the current Sense plug-in.
• Check the developer mode and click "Download Unpacked Extension ..." and select the unpacked folder.

Answer 3

You can copy your Chrome profile into your ChromiumPortable profile, then the Sense extension will be included in Chromium with all your history.

Chrome Profile C: \ Users \ xxxx \ AppData \ Local \ Google \ Chrome \ User Data \ Default

Chromium profile (rename an existing profile in Default.bak) C: \ ChromiumPortable \ Data \ Chromium \ UserData \ Default

I had the same issue and the above fix got me my Sense story. I am using Chrome 63 and Chromium 65.

Answer 4

To identify the extension, you need to open chrome: // extensions / and check "Developer Mode" (top right), then scroll down to the extension and you will find the extension ID. The folder in the folder C: \ Users \ Admin \ AppData \ Local \ Google \ Chrome \ User Data \ Default \ Extensions will be called with extension identifiers.