Historical data not seen.
sandrajones 270000NWW2 Visits (7862)
This set of
Recently had a problem come in where it was reported that customer was getting frequent
Linking these together, it sounded like the data was not being collected from the agents, so filing disk space.
This can be caused by a number of different problems, so next step is to check the WPA logs.
Again in these logs were messages about not being to createRouteRequest.
The type of issues to look at are firewalls having ports closed, and what it was in this case, an issue with KHD_
If there is more than one then the parameter KHD_
For this WPA a list of TEMSes were given, but the names were wrong. It has to be the monitoring server instance name that is given.
In this case the name was given as TEMS1_RTEMS when it should have been RTEMS_TEMS1,
this meant that the ITM code could not find the instances so no route could be found to the WPA.
Make sure if you do a list of TEMS machines for this attribute that the correct name for the TEMS (which is set when you install) is used.
Once this was sent correctly and the WPA restarted, historical information was sent to the warehouse
There has been a number of problems seen where the process of historical collection has not been understood,
It is set at the teps and are sent to the agents in the form of situations that start UADVISOR_* to state what is to be collected.
Historical data files are usually kept on the agent, but can be configured to be saved on the TEMS.
For each attribute there are two files for example: KHDLOADST and KHDLOADST.hdr for one of the WPa collections.
The data is not removed from the agent (or tems) until it has successfully inserted into the warehous database.
Therefore if there are problems getting the data to the warehouse the files on the agent will continue to grow in size.
The historical data files always contains up to 24 hrs of data, so once it is running for over 24 hours it should stay fairly constant is size,
Once the data is in the warehous it is the S&P agent that summarizes and prunes the data.
Therefore knowing which tables have data in the warehous database can help to locate where the issue possibly is.
Subscribe and follow us for all the latest information directly on your social feeds: