From 9a5c59aebe12468de560ed23df35062079823161 Mon Sep 17 00:00:00 2001 From: John Cardinal Date: Sun, 31 May 2020 23:56:41 +0000 Subject: [PATCH] --- ayanova/devdocs/todo.txt | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/ayanova/devdocs/todo.txt b/ayanova/devdocs/todo.txt index 0e010e70..bd5e44ee 100644 --- a/ayanova/devdocs/todo.txt +++ b/ayanova/devdocs/todo.txt @@ -43,7 +43,8 @@ todo: OPS view metrics https://stackoverflow.com/questions/53321634/unable-to-print-query-using-miniprofiler https://github.com/MiniProfiler/dotnet/issues/458 https://community.miniprofiler.com/t/can-i-use-mini-profiler-for-asp-net-web-api-and-have-results-still-seen-on-url/365/2 - + https://miniprofiler.com/dotnet/HowTo/ProfileCode + https://miniprofiler.com/dotnet/AspDotNetCore PROFILE VIEWING ROUTES http://localhost:7575/profiler/results-index @@ -58,7 +59,7 @@ todo: Profiling find a way to get the raw data so it can be fed back to the metrics route and limited to what I want to allow to show maybe store just the critical or slowest routes with some db info into the database on schedule from the in memory cache? https://github.com/MiniProfiler/dotnet/tree/master/src/MiniProfiler.Shared/ui - + Full profiling view: but find a way to allow / enable the full suite of profile as it is for just technical support purposes, i.e. a hidden switch or something? some kind of limitation to the route so not anyone can just open it (source IP or domain?, i.e. tech support)