System Data Recorder

 
Thread Tools Search this Thread
Special Forums UNIX and Linux Applications Infrastructure Monitoring System Data Recorder
# 1  
Old 02-18-2009
System Data Recorder

Monitoring the IT infrastructure is an important key to ensure your business continuity and prepare for future grow. SDR is a simple toolkit, containing a number of data collectors, used to record and report data from your Solaris servers. SDR is mainly designed around Solaris operating system due kernel statistics interface but it can be easily expanded to other OSes. Solaris operating environment has already many utilities to debug and observe the entire system or certain individual processes. Third parties software applications can be installed to monitor the system or the applications: BMC Patrol, TeamQuest, Tivoli, Sitescope, Nagios, etc. In this case we are interested in observing and recording: the utilisation of certain resources: cpu, memory, disk, network the saturation of these resources All these numbers will help us in developing a simple capacity planning setup for our site.

More...
Login or Register to Ask a Question

Previous Thread | Next Thread

7 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Recorder number of process per user

Hello Team, I would like to use a shell script that run each 15 minutes in order to recorder the number of process per user I request your help in order to build an awk script under Solaris from the following command or similar: ps -fea -o user | sort | uniq -c | sort -k 2 648 ... (3 Replies)
Discussion started by: csierra
3 Replies

2. What is on Your Mind?

Big Data for System Admins

Hello, I have been working as Solaris/Linux Admin since past 8 years. I am looking options for my profile change, but there is some limitation. I worked as 24x7 support for admin, server support, high availability, etc. But been worked on developing side and scripting part. When I search for Big... (2 Replies)
Discussion started by: nightup2222
2 Replies

3. Red Hat

system activity and information data

Hi all, i need to collect all system activities data(processes running, disk details, memory, etc), system logs and things related. i heard of cfg2html but its not available for my CentOS distro(i may need to install separately but thats not what i wana do). i can use sar for syatem... (1 Reply)
Discussion started by: ajayyadavmca
1 Replies

4. AIX

Resync data on File system

Hi All, I have two mount points have the same data with little changes between them /appabc1 /appabc2 Both of them have the same data, there is some little changes on the data between them I want /appabc2 to has the same data of /appabc1 exactly including to those little changes... (6 Replies)
Discussion started by: Mr.AIX
6 Replies

5. UNIX for Advanced & Expert Users

how to make a full system backup excluding data and restoring it to a new system

Hi, In order to have a sand box machine that I could use to test some system changes before going to production state, I'd like to duplicate a working system to a virtual one. Ideally, I'd like to manage to do it this way : - Make a full system backup excluding the user file system (this... (7 Replies)
Discussion started by: pagaille
7 Replies

6. HP-UX

restore data after system crash

Hi all, I have a server running HP-UX 11i V1 (11.11). We had a problem with the system disk which cannot boot and the recovery with the CD failed too. the only solution was to re-install the system on a new disk. The problem now is to get access to the data which are on other disks, not... (2 Replies)
Discussion started by: aribault
2 Replies

7. Shell Programming and Scripting

how to verify that copied data to remote system is identical with local data.

I have created simple shell script #!/bin/sh echo `date`; echo "Start .... find . -mtime +95 -print > /tmp/files.txt for file in `cat /tmp/files.txt` do echo "copying file - $file" /usr/local/bin/scp -p -P 2222 $file remote.hostname:/file/path echo "copid file -... (3 Replies)
Discussion started by: ynilesh
3 Replies
Login or Register to Ask a Question
IONCONFIG(5)						      ICI configuration files						      IONCONFIG(5)

NAME
ionconfig - ION node configuration parameters file DESCRIPTION
ION node configuration parameters are passed to ionadmin in a file of parameter name/value pairs: parameter_name parameter_value Any line of the file that begins with a '#' character is considered a comment and is ignored. ionadmin supplies default values for any parameters for which no value is provided in the node configuration parameters file. The applicable parameters are as follows: sdrName This is the character string by which this ION node's SDR database will be identified. (Note that the SDR database infrastructure enables multiple databases to be constructed on a single host computer.) The default value is "ion". configFlags This is the bitwise "OR" of the flag values that characterize the SDR database to use for this ION node. The default value is 1. The SDR configuration flags are documented in detail in sdr(3). To recap: 1. The SDR is implemented in a region of shared memory. [Possibly with write-through to a file, for fault tolerance.] 2. The SDR is implemented as a file. [Possibly cached in a region of shared memory, for faster data retrieval.] 3. Transactions in the SDR are written ahead to a log, making them reversible. 4. SDR heap updates are not allowed to cross object boundaries. heapKey This is the shared-memory key by which the pre-allocated block of shared dynamic memory to be used as heap space for this SDR can be located, if applicable. The default value is -1, i.e., not specified and not applicable. pathName This is the fully qualified path name of the directory in which are located (a) the file to be used as heap space for this SDR (which will be created, if it doesn't already exist), in the event that the SDR is to be implemented in a file, and (b) the file to be used to log the database updates of each SDR transaction, in the event that transactions in this SDR are to be reversible. The default value is /usr/ion. heapWords This is the number of words (of 32 bits each on a 32-bit machine, 64 bits each on a 64-bit machine) of nominally non-volatile storage to use for ION's SDR database. If the SDR is to be implemented in shared memory and no heapKey is specified, a block of shared memory of this size will be allocated (e.g., by malloc()) at the time the node is created. If the SDR is to be implemented in a file and no file named ion.sdr exists in the directory identified by pathName, then a file of this name and size will be created in this directory and initialized to all binary zeroes. The default value is 250000 words (1 million bytes on a 32-bit computer). wmKey This is the shared-memory key by which this ION node's working memory will be identified. The default value is 65537. wmAddress This is the address of the block of dynamic memory -- volatile storage, which is not expected to persist across a system reboot -- to use for this ION node's working memory. If zero, the working memory block will be allocated from system memory (e.g., by malloc()) at the time the local ION node is created. The default value is zero. wmSize This is the size of the block of dynamic memory that will be used for this ION node's working memory. If wmAddress is zero, a block of system memory of this size will be allocated (e.g., by malloc()) at the time the node is created. The default value is 5000000 (5 million bytes). EXAMPLE
configFlags 1 heapWords 2500000 heapKey -1 pathName 'usr/ion' wmSize 5000000 wmAddress 0 SEE ALSO
ionadmin(1) perl v5.14.2 2012-06-11 IONCONFIG(5)