NetXMS Support Forum

English Support => General Support => Topic started by: cserzs on July 10, 2017, 03:26:50 PM

Title: Request time out issue
Post by: cserzs on July 10, 2017, 03:26:50 PM
Hi,

I configured some table type DCI in our NetXMS system (v2.0.7).
The table settings are the following:

Polling interval: 180s
Retention time: 365days
Number of columns: 11

When I try to request a more than 4h length line chart from any element of this table I get always the "Request timeout" error message.


Do you have any solution for this issue?

Thank you in advance.
BR, Zsolt
Title: Re: Request time out issue
Post by: Tursiops on July 13, 2017, 10:02:22 AM
Hi,

If you have a lot of data, slow database or slow network connection to the server and you are using the management console, that can happen.
The request from a Console results in all relevant data being sent to the client, which then generates the graph (i.e. the server does not generate the graph and sends the image down).
Using the web management console, if installed on the same system as the NetXMS server is usually a lot faster for graphs for that reason.

I haven't had this for a 4 hour time period, but certainly if I request data for a couple of weeks or a month. Simply clicking the refresh button on the graph usually works - possibly because the client cached what it already received?

Cheers
Title: Re: Request time out issue
Post by: cserzs on July 22, 2017, 03:03:48 PM
HI,

Thank you for your support. I have checked the web managemenet console and unfortunately the result is the same (timeout issue) in this case as well. My experience is that this issue is obviusly related with the table type DCI elements because when I request any simple DCI time series (e.g. Polling interval: 180s
Retention time: 365days) for a 1years period (175200 samples) the chart processing time is less than 10-20 seconds. The timeout issue is occure only in case of table type DCI.

Do you have any ideas?

BR,
Zsolt
Title: Re: Request time out issue
Post by: Victor Kirhenshtein on July 25, 2017, 07:51:43 PM
Hi,

it is know issue with table DCI performance when accessing historical data. We change the way how table DCIs data is stored in 2.1, so upgrade may help.

Best regards,
Victor