Hi,
We have several apps calling Indicium, and using the data. This works fine, but sometimes clients complain about performance. We have a feeling that someone is calling the endpoint a bit too often.. or requesting a bit too much data.
What options do I have to see how often someone (an app) is calling certain endpoints, and at what moment?
Thanks!
Blommetje
Hi
You can consider using Application Insights. For more information, please refer to: Monitoring Indicium live.
Let us know if this helps or if you need further assistance.
Hi Jeroen,
I think we've made some progress. We have Insights connected and it logs .. a lot. Now we still need to figure out what we are looking at, and where to look for bottlenecks/issues. Perhaps it possible to have a short session with someone how fully understands Azure Insights, and explains the main points and do's and dont's… ?
I also explored the IIS logs and found a lot of useful information there!
Blommetje
Good to hear there seems to be some progress, and that you’ve managed to find relevant information in the IIS logs. For real expertise around Azure Insights and the do's and don'ts, I’d better refer you to Azure consultants since this isn’t our area of expertise. If your investigation reveals any Thinkwise-related findings, we’d of course be happy to hear about them.
Hi
I was wondering if any Thinkwise-specific matters or findings came out of your research that we might be able to assist with. If so, we’d be happy to hear more. If not, we can probably consider this question closed.
Hi
Are there any options within Indicum or the Thinkwise platform to get this in the logs as it is possible to also run these applications without an Azure setup?
Gr,
Marlon
Hi Blommetje,
While it is not as comprehensive as Azure Application Insights, it is possible to extract API logs from Thinkwise apps hosted in IIS in an on-premise environment. See this topic in the docs. Note that the path to the log files was different in my case. You can find the exact path in IIS > Site > Logging:
Here you can also configure what fields to include in the logging.
An example of a log file looks like this:
2025-07-15 11:45:01 ::1 GET /indicium/sf/<app>/<tab>(<id>) - 443 - ::1 <device> https://localhost/universal/ 200 0 0 203
2025-07-15 11:45:01 ::1 GET /indicium/sf/app/<tab> - 443 - ::1 <device> https://localhost/universal/ 200 0 0 6
If you would like to connect Thinkwise to other telemetry options (such as grafana/jaeger/zipkin), I would suggest creating an idea for this. The more votes the idea gets, the higher the priority!
I hope this answers your question?
Best regards,
Nick Janssen
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.