I am using the following search to extract the time usage of the internet by user report:
index = "ciscowsa" SourceType = "ciscowsasquid" | transaction user maxpause = 5m | stats sum (duration) the Duration by CN | sort -Duration | Lookup lightatributos_principais CN OUTPUT User, Company, CostCenter, DepartmentNumber, OR | Duration fieldformat tostring = (duration, "duration") | eval Superintendencia = substr (DepartmentNumber, 0, 2) | search DepartmentNumber = "LTO" | head 10 | sort -Duration | CN rename the Matricula, the Company Company CostCenter the "Cost Center" DepartmentNumber the Department, the OR Management | User table, Matricula, Company, Department, Management, "Cost Center" Superintendencia, Duration
The report is created without problems, but I cannot speed the same, and he acabanão generating the data altogether. what I should do to improve the performance of the report?
See this answer on avoiding the usage of the
transaction command. It is probably the reason your search is going slowly. Normally you could use report acceleration, but this is not a qualifying search because you don't use a transforming command.
See this page to learn more about how search types (dense, sparse, super-sparse, rare) affect search performance. Note the second two are I/O bound while the first two are CPU-bound.
Secondly, if you schedule this search to run, you can have results waiting for you when you load the report (from the last scheduled run's results). This way you don't have to wait for the search to complete in front of you but you still have at least some results. Obviously this is dependent on how often you need to access fresh data.
Open the job inspector, Job > Inspect Job. What is taking the longest ? What is your events scanned to results returned ratio ? Good search performance is around 10k - 20k events returned per second.