Hi,
The organisation in which I am working is replacing Kibana with OpenSearch. This has been going on for some time, and one of our environments has moved from v2.6 to v2.16.
This has become a disaster for me, as I use Discover more than Dashboards (sorry, I am a bit unclear if you refer to Discover as a dashboard, but I assume it is not).
The problem I have is that I need to see the ‘messages’ clearly.
When testing functionality, I may need to quickly copy a message and paste it (eg into Jira).
Important Note: Even using Kibana and previous versions of Opensearch, copying a Diameter message (as an example) was annoying, but it was possible from column view.
I had to carefully position my mouse pointer near the bottom right, and drag to the top left. An alternative would be to expand the row and select the message from within the document. This is easier to highlight the text, but slower due to the steps involved … I then had to paste into an Excel cell to keep the formatting, then copy the cell and paste into a document (eg Jira, or MS Word). If I didn’t go through these convoluted steps, the Diameter message would appear on a single line.
Now, using v2.16, I appears I cannot (carefully) copy a selected field/column, or expand the row into the documents ‘component parts’, it just has ‘Click or enter to interact with cell content’, which opens a small popup that cannot be expanded. You can’t even press Ctrl-A to select ‘inside’, having to select a start position and drag to the end!!!
Also, if I select fields to view as columns, it appears each row becomes a single line, making it very difficult to see which rows I actually want.
I hope I have explained why the new layout does not adequately work for me, but my basic question is ‘can I revert to the old Discover style’?
I would also like to go back to old typeface (Courier?), as it is much easier to read ‘logs’ with fixed-pitched/monospaced.
NB I am an end user, and there are support people who implement the system. I may, or may not, have access to the necessary configuration. You can also deduce that I am unfamiliar with the setup to OpenSearch (or the underlying stack). It may be that I have to direct support staff with any suggestions.
…also, today is my first morning trying to use this new GUI, and I am already desperate to reach out to the community.