STAT server : my understanding..

[Raja12398]

Hi experts,

From my understanding, t server pass the info to stat server...
1)from cc pulse we can see the real time status from statserver??one logical question, where does it store inside cc pulse? is it some internal mechanism, where cc pulse store the info from stat server..then we can see?
2)if we want to store the some information in some table.. a) we need  db server, dap for stat server..also create a db..run the scripts..which is available inside stat server--> script folder..StatServers can have DBServers connected to them, to pass through specific statistical information to pre-defined Tables; QINFO, LOGIN, AREF and STATUS.
if we use this four table..where does we use those four table..cc pulse use it?? no?then where it use?



Thanks
Raja

[cavagnaro]

Geeee old questions over again.
1. Read StatServer doc, architecture
2. Read ODS/ETL docs
3. For Special SS tables check documentation. NO CCPulse doesn't care about them, is as described, specific info storage.
3. Search the forum

[Adam G]

Extending cav's reply - and most probably repeating information already here on the Forum (please learn to "Search" before you ask a question!);

Stat Server stores nothing.  It passes incremental statistical information to clients, such as CCPulse+, Historical Reporting and Routing.  The clients initiate communications with the StatServer and send a request for a particular statistic, for particular objects, in particular time frames.  The StatServer adds the Request to it's list and sends out the appropriate information, to the appropriate client, at the appropriate time.

QINFO, LOGIN, AREF and STATUS are Database Tables which can be written to [i]from [/i]Stat Server, with the appropriate DBServer/DAP connectivity.  These are mainly out of use, now but were heavily used by Historical Reporting, in the past.  CCPulse+ does not use QINFO, LOGIN, AREF or STATUS at all.

The Workspaces and Templates in CCPulse+ are used to determine how incremental stats are populated from the StatServer - this includes; Intervals, Time Ranges and Time Profiles.  CCPulse+ basically adds stats together as they arrive and then transforms/displays them in whatever format you specify (Table, Graph, etc.)

If you are asking "[i]How can I get the  exact same stats and views I see in CCPulse+, for use somewhere else?"[/i]; you would either need to use the Stat SDK (Platform SDK) to emulate what CCPulse+ does with the stats it gets from the StatServer or build your own 3rd party client to connect to the StatServer.

I think I should get at least 2 stars for effort, here!

[Raja12398]

Thanks a ton all your help..
have a small query then..
as you said, QINFO, LOGIN, AREF and STATUS  can use for historical reporting..how?
as far as my understanding.. statserver --> datasource (DMA)--> ODS --->ETL--> datamart..---------------> ccpulse+ (for historical reporting)

where this table come into picture?are you saying..we can store the stat server info into these four table..later..we can create a report,,based upon these four table..is that correct??
Thanks a lot again..

Raja

[Kubig]

Read the doc You are always asking for question that are answered within documentation.


You cannot use these tables within CCP+ as standard hist.association. You can only directly access to the SS database (where the login, etc tables are located) through the VBS for example and read the data.