Raising Intelligence - Viewpoint DCS Usage

Blog
The best minds from Teradata, our partners, and customers blog about whatever takes their fancy.
Teradata Employee

After a spectacular Teradata Partners Conference, I'm back to do another cool Viewpoint features blog. I want to start out on this one with a little background on how this feature came about. In our first two Viewpoint releases, we focused on Teradata Management and Teradata Self Service aspects. Our customer base increased and with that, so did the importance of Viewpoint in the Teradata customer infrastructure. With that increased base and importance, it became clear that we needed to improve on the management aspects of the Viewpoint Appliance itself. So this became a major theme for us in our June 2009 Viewpoint 13.0.1 release. With that release, we introduced the new "Viewpoint Monitoring" portlet providing visualization of resource utilization (CPU, memory, etc) for one or more Viewpoint servers; released a data collection clustering solution providing a High Availability solution; and offered a new Admin Configuration menu for assisting with Teradata Systems, Data Collectors, Managed Servers, LDAP, and Backup configurations. The result was a dramatic improvement in ease of use, high availability, and the overall management capabilities for Viewpoint.

For this article, we are going to look at one particular aspect of the improved management capabilities, specifically regarding the Data Collection Service (DCS) disk usage.

The DCS is an internal Viewpoint data repository where each data collector stores the information it pulls from the Teradata systems being monitored. This information is housed locally to offload Viewpoint user activity from Teradata as well as providing current and history information for rewind, trending, and analysis even when the associated Teradata system may be unavailable. As the DCS is currently a RAID V configuration of four 300GB drives (~1TB of useable space), it does have its limits to the amount of data it can house. Even though each data collector has its own configurable collection and retention rate per Teradata system, there was no easy way to know exactly how much space your Teradata system was using nor how much a particular data collector consumed. However this all changed for the good in the Viewpoint 13.0.1 release with the introduction of the "Disk Usage" visualization feature. This can be found as part of the Data Collectors option in the Admin - Configuration menu and looks like this:

The mapping of the disk space provides an easy visual overview of the DCS available and used space. It also allows one to mouse over various areas to get information balloons with additional details to show the free space (480G here) or the amount of DCS space used by each Teradata system being monitored. In this example, we have three Teradata systems (biggulp, ram, th) sharing the DCS. Take note of the sparkline at the top that provides the past three months data trend for the DCS usage. Nice but there's more. One can then drill down on each Teradata system to see how much data space each data collector for that particular system is using. For instance, drilling down on biggulp would show:

This provides the breakdown of each data collector usage for each Teradata system being monitored. Those tricky Viewpoint developers even added another level of drill down for each data collector box that will take you directly to that data collector configuration screen. So if you found one Teradata system in particular using the majority of DCS space and found that the Sessions collector was the main culprit, then by simply clicking on that box, you would go right to the data collector configuration where you could adjust the collection or retention rate accordingly ... like so:

Viola, DCS data space management made easy. 

So if you have Viewpoint but aren't at release 13.0.1, hopefully you're convinced you need to get there. Not enough? Well there is also three new Teradata Management Portlets in that release ... Lock Viewer, Remote Console, and Space Usage but we'll save discussions on those for another day. Thanks for listening.

"Learning is a treasure that will follow its owner everywhere" - Chinese Proverb

5 Comments
Enthusiast

Gary,

Very nice ariticle.

In our current system, we defined 10 GB to purge session data in data collector. Due to that it is holding only 1 month of production session history data. i am recommending management to hold minimum 6 months of session data which can assist us in any analyisis.

My question is, Is there any recommended retention nbr to set for session history data or it is totally the client requirement to set the size limit based on the space availability?

Thanks,

Harsha.

Teradata Employee

There is no recommended retention because it is specific to the customer environment and not only the desired length of data retention but how much data is generated per collection, what is the frequency of collection and how many systems is the Viewpoint instance monitoring. I think a setting of 3-6 months is the norm. 

Enthusiast

Gary,

Thanks for immediate response.

I too agree that it is totally client requirement. But as you mentioned i am recommending the client to set the value based on time period (set to 6 months) instead of size, but challenge here is which is the ideal time period to set so that Viewpoint server wont ”run out of space problem”.

Here is the requested details:

Viewpoing instance monitoring: DEV, DEV2, QA & PRD

current disk space usage in Viewpoint is 34%

How much data is generated per collection?

Can you please elaborate on how to calculate it and is there a way to calculate how much apprx. space it is consuming for a session data per month instead of monitoring the data for a period of time.

Based on current data, we are seeing 10 GB space consuming by PRD Session history for one month. So can i assume 60 GB space (apprx.) for 6 months. Is my interpretation right or wrong, can you please confirm.

Thanks,

Harsha.

Teradata Employee

The amount of data generated is dynamic based on the system query activity and how often it is being collected. I was going to suggest the easiest way would to determine the space consumption would be to divide the amount of space being collected today over the duration of which you have. As you've done that already, I think your approximation of 60GB for 6 months is a good estimate. Note that with Viewpoint 15.11, we now offer an alert for the Viewpoint disk space usage for a proactive notification when nearing space capacity. 

Enthusiast

Thank you, Gary.