Analytics for API shows no data | Message: no data to display

[IvoIlic95]

Hello

I have a issue:

I have created a API by using a Swagger descriptor. Then I created a API plan and subscribed to it with my application. After that I clicked on the analytics button from the imported API. And it only shows me this (either nothing (no graphs) or no data to display):

Could it be that the API is doing nothing, and because of that it can't show me anything in the analytics panel or is there a another cause for it? But the API is getting requests but not frequently.

The Management-Api is throwing this error in the log:

Management_Api_Log.txt

Update: I looked into my Elasticsearch and there were many indices available. Is it possible that Gravitee.io gets confused with so many indices so that it can't calculate the analytics?

Kind regards, Ivo Ilic

[aelamrani]

Hi @IvoIlic95

Do you have errors on the startup logs?

[IvoIlic95]

Well on the startup there are no errors. The only errors that I am getting are these and the errors from the previous file that I attached to my issue: Management_Api_Log.txt

It says that there is a error with the freemarker template.

[aelamrani]

If you don't have calls on your API, it's normal not to have data. But the error here is strange.

[IvoIlic95]

One of my colleagues said to me, that the API that I have included is only getting new requests, if any. But these requests should get visualized by the Gravitee.io analytics tool or not? I set the time for the past 90 days so that any log data could be found.

Which error: The freemarker template error or the unable to search error or retrieve logs error (Elasticsearch) ? :)

[aelamrani]

I meant the first logs: io.gravitee.repository.analytics.AnalyticsException: Impossible to perform log request...

[IvoIlic95]

I think this error occured because my Elasticsearch and Kibana crashed. I had to restart it and therefore, the possibility is high that this error comes from this cause.

What is this freemarker template error?

Update: I also realized that the log file (gc.log.0.current) from Elasticsearch is empty. Does Gravitee.io read from the log Files from Elasticsearch?

[aelamrani]

ATM, you have no data on your dashboards because you do not have requests passing through the API Gateway. The configuration of ElasticSearch seems to be OK as i can see gravitee-monitor data. But you should have data on the indice gravitee-request for your requests and according to your screenshot that's not the case.

[IvoIlic95]

Hmm okey, but after looking at my Elasticsearch indices I can't see any "gravitee-request" which you mentioned me. How can I get this indice or does Elasticsearch create automatically this indice?

Update: Why does this message always comes up inside the logs of the Management-API: 12:10:10.004 [sync-1] INFO i.g.m.s.d.DynamicPropertiesService - Dynamic properties service is disabled for: Forrest API [1.16] I can't explain why this comes up it irritates me by a lot ^^?

[brasseld]

You already asked the same question in your previous issue.

This log is not relevant and we probably have to change the log level to DEBUG.

[no-response[bot]]

This issue has been automatically closed because there has been no response to our request for more information from the original author. With only the information that is currently in the issue, we don't have enough information to take action. Please reach out if you have or find the answers we need so that we can investigate further.

[lehn-etracker]

I encountered this issue and thought others might be interested in my solution.

I've noticed that APIs created with the 'V4 - Proxy' definition do not provide analytics within the platform overview, whereas definitions of 'V2' do.