Improve usability of Oracle sensor to diagnose problems

I had an interesting conversation with a customer regarding Oracle monitoring.  Customer is Radial.  I’m going to open an Idea, but wanted to pass along the info.

The customer has other tools today that they use for monitoring Oracle.  He described a very common usecase.

Frequently, developers or in some cases rogue applications connect to the database and run some very inefficient and/or long running queries.  Those queries sometimes slow down other applications or they lock tables and cause application performance issues.

What the customer is looking for is a way to identify the following whenever they see one of these inefficient queries or table locks:

Where did the lock originate?  What server is it running on?

What user account is running the query?

What is the session ID

Instana application transaction is slow.  How do I correlate that back to the things happening on the Oracle server (for example a table lock or cache hit ratios).

It looks like we gather a lot of this information, but doing the diagnostics is not very easy or intuitive.   I think we should take a look at how we display our data.   I also think it might be useful to create a short video showing how we use our Oracle sensor to diagnose problems.  Unfortunately, we don’t really have good data in our demo environments to demonstrate this because our Oracle database is not part of a business app that has problems.