Chart and easy-search options in notebook app

[VivekMalapaka]

Hi Team,

We have a timeseries chart option in "Logs" application as shown below:

Why is such an option not provided in "Notebook"?  I guess notebook has lots of features, but including this feature as well will provide more visualization.

Also, why do we not have the quick filter option in notebook like we have in Logs app?

We are forced to write a query in notebook to get one small string. If you include these two in notebook app, then I think it will make things more handy for us.

Notebook has a lot of beautiful features, but some handy features are not present. Let me know when you are planning to prioritize these two things in notebook. Make them default.

Best Regards,

Vivek Malapaka

[Julius_Loman]

It's basically a DQL for fetch logs + timeseries:

fetch logs | makeTimeseries by:{status, dt.system.sampling_ratio}, count = count(), interval: 1m | fieldsAdd totalCount = arraySum(count), count = iCollectArray(count[] * dt.system.sampling_ratio)

You can use the same query in notebook or adapt it for your case. Don't forget you can use Dynatrace Intelligence and have the tile created for you.

As for the second question, notebooks are designed for analysis (data is persistent in the notebook) and you should filter in the query itself - in DQL or log browser at query time in the notebook. For ad-hoc browsing  you have the Logs application.

[VivekMalapaka]

Hey Julius,

Thanks for helping me with the query. Why would anyone want to write a query for everything. Dynatrace is unfortunately encouraging us to use these queries for each and everything and the result? The systems are too slow. 

You have a slew of visualization options in notebook which depict honeycomb patterns, Donuts, bars, charts etc. etc.. Then why is a chart that is a very important feature omitted? Notebook is colorful, but omits important GUI features.

I came across an answer in Co-pilot that Dynatrace is not encouraging GUI and is heavily dependent on querying to encourage speed. Is that true? But to be frank your notebooks load very slowly and get stuck up very badly. I tried it across different browsers. Nothing works.

Why encourage so much querying? You cannot expect the end user to know so much querying in your language (DQL). It is the GUI you need to encourage. Don't you think? 

[Julius_Loman]

@VivekMalapaka  you don't need to write DQL queries, you can use Dynatrace intelligence instead and use natural language. Just use Prompt in the Notebooks app:

You asked for the query the Logs app uses,