En
Ru
Manual DF™ Site Monitor
Help Topics
System settings
Parameters of monitoring the sites group
Displaying and managing a group of sites
Displaying and managing sites
Parameters of monitoring the sites group
Suspend group - Suspending check of group.
Truncate page parameters when checking site uptime? - check site address for uptime without page parameters.
Truncate page parameters when checking site content? - check site address for illegal content without page parameters. These options are used for exclusion of counting bot's hits as real surfers' by third party systems.
Frequency of site check - this parameter defines how often the system will attempt to connect to the site to determine its status.
Interval between site checks - this parameter defines the minimal time (in seconds) between site checks. Real time interval depends on how often the checking script is run ad the number of sites checked. The smaller the interval, the more server resources and bandwidth is consumed. To check a group of sites once, you have to use parameter ‘-1’. Use this when you don’t need to check the sites at regular intervals.
User notification - the user is notified only when the site status changes.
Status change notification:
- Site availability (Uptime)
- Forbidden content
- Required content
Notification method - defining the method of notification when site status changes.
Methods:
1. E-Mail - email message with the site name and its new and old status.
2. URL - sending information to third party site using GET. The following macros are allowed: URL - site URL;
UPTIME - site available(1/0);
FNDBAN - site contains forbidden content (1/0);
FNDPRES - site contains required content (1/0);
CHKTIME - time of last site check (timestamp: PHP=>time(); Perl=>time; C/C++=>time(NULL));
RETHTTP - server response(code number);
STATUS - current site status. This value contains information in bits.
0 bit - site availability.
1 bit - forbidden content.
2 bit - required content.
Possible site statuses:
0 - site not available.
1 - site available.
3 - site contains forbidden content.
5 - site contains required content.
7 - site contains forbidden and required content.
3. Command - command line execution and transferring the site data into the (stdout) stream.
The stream data format:
"URL STATUS f=NFNDBAN p=NFNDPRES c=RETHTTP\n"
URL - site URL;
STATUS - current site status. This is addressed in more detail above.
f=NFNDBAN - number of forbidden content which was found (starting from 0). Is not shown when no forbidden content was found, or no search was made.
p=NFNDPRES - number of required content which was not found. Is not shown if required content was found, or no search was made.
c=RETHTTP - server response(code number);
String sample:
http://google.com 5 1256456854 f=0 p=2 c=200
4. Command after completing - command line execution and sending information concerning site status to the thread after all the sites are checked. Data format is similar to Command notification.
5. None - notification disabled. In some cases notification is not necessary. The user can monitor the site status using the web panel. When DF Site Monitor is used as a module, third party system can receive information regarding the site status using the GET command.
CheckLog - log files for the checks.
Enable checklog - enable check logging. Logging of the site status changes.
Search by masks.
Masks enable you to analyze the HTML code in a deeper way. For instance, with masks you can figure out whether your link is in the document’s body (<body>), whether it is commented out, or whether it has unclosed HTML tags which influence its visibility (<!--…-->,<script>,<textarea>) or disallow SE indexation (<noindex>).
The masks can be:
[~*~] - any text.
[~!~] - any symbol.
Special purpose masks:
[~+'text'~] - 'true' value, if text specified in quotation marks was found.
[~-'text'~] - 'true' value, if text specified in quotation marks was not found.
[~=+'text1',-'text2'~] - 'true' value, if the sum of texts equals zero (for instance, the same number of opening and closing HTML tags). When the sum of texts is counted, presence of text1 increases the sum by 1, while presence of text2 decreases the sum by 1.
[~%+'text1',-'text2'~] - 'true' value, if the sum of text does not equal zero (for example, different number of opening and closing HTML tags).
[~>+'text1',-'text2'~] - 'true' value if the sum of texts is >0 (for example, there were more opening HTML tags than closing ones).
[~<+'text1',-'text2'~] - 'true' value, if the sum of texts is <0.
[~?+'text1',-'text2'~] - 'true' value, if text2 follows each text1 (checking whether HTML tags are closed, where text1 is an opening tag and text 2 is the closing one).
Sample 1.
Detecting a link in site code and determining whether it is in page body (between <body< and </body<).
Required content:
<body[~*~]<a href="http://mydomain.com">My Link</a>[~*~]</body>
Sample 2.
Checking whether your link is commented out (we disallow your link to follow unclosed tags like '<!--', '<script>','<textarea>').
Forbidden content 1:
<body[~?+'<!--',-'-->'~]<a href="http://mydomain.com">My Link</a>
Forbidden content 2:
<body[~?+'<script',-'</script>'~]<a href="http://mydomain.com">My Link</a>
Forbidden content 3:
<body[~?+'<textarea',-'</textarea>'~]<a href="http://mydomain.com">My Link</a>
Sample 3.
Checking whether SE indexation of a page is disallowed through <meta name="robots" content="noindex"> (we disallow <noindex> to be contained in the meta fields).
Forbidden content:
<meta[~-'>'~]noindex
Sample 4.
Checking whether the page links to mydomain.com with "MyDomain.com Site" as link text (we check this with a number of HTML link code variants).
Required content:
<a[~-'>'~]href=[~!~]http:// mydomain.com[~*~]>[~-'</a>'~][~*~]MyDomain.com Site [~*~]</a>
Suspend group - Suspending check of group.
Truncate page parameters when checking site uptime? - check site address for uptime without page parameters.
Truncate page parameters when checking site content? - check site address for illegal content without page parameters. These options are used for exclusion of counting bot's hits as real surfers' by third party systems.
Frequency of site check - this parameter defines how often the system will attempt to connect to the site to determine its status.
Interval between site checks - this parameter defines the minimal time (in seconds) between site checks. Real time interval depends on how often the checking script is run ad the number of sites checked. The smaller the interval, the more server resources and bandwidth is consumed. To check a group of sites once, you have to use parameter ‘-1’. Use this when you don’t need to check the sites at regular intervals.
User notification - the user is notified only when the site status changes.
Status change notification:
- Site availability (Uptime)
- Forbidden content
- Required content
Notification method - defining the method of notification when site status changes.
Methods:
1. E-Mail - email message with the site name and its new and old status.
2. URL - sending information to third party site using GET. The following macros are allowed: URL - site URL;
UPTIME - site available(1/0);
FNDBAN - site contains forbidden content (1/0);
FNDPRES - site contains required content (1/0);
CHKTIME - time of last site check (timestamp: PHP=>time(); Perl=>time; C/C++=>time(NULL));
RETHTTP - server response(code number);
STATUS - current site status. This value contains information in bits.
0 bit - site availability.
1 bit - forbidden content.
2 bit - required content.
Possible site statuses:
0 - site not available.
1 - site available.
3 - site contains forbidden content.
5 - site contains required content.
7 - site contains forbidden and required content.
3. Command - command line execution and transferring the site data into the (stdout) stream.
The stream data format:
"URL STATUS f=NFNDBAN p=NFNDPRES c=RETHTTP\n"
URL - site URL;
STATUS - current site status. This is addressed in more detail above.
f=NFNDBAN - number of forbidden content which was found (starting from 0). Is not shown when no forbidden content was found, or no search was made.
p=NFNDPRES - number of required content which was not found. Is not shown if required content was found, or no search was made.
c=RETHTTP - server response(code number);
String sample:
http://google.com 5 1256456854 f=0 p=2 c=200
4. Command after completing - command line execution and sending information concerning site status to the thread after all the sites are checked. Data format is similar to Command notification.
5. None - notification disabled. In some cases notification is not necessary. The user can monitor the site status using the web panel. When DF Site Monitor is used as a module, third party system can receive information regarding the site status using the GET command.
CheckLog - log files for the checks.
Enable checklog - enable check logging. Logging of the site status changes.
Search by masks.
Masks enable you to analyze the HTML code in a deeper way. For instance, with masks you can figure out whether your link is in the document’s body (<body>), whether it is commented out, or whether it has unclosed HTML tags which influence its visibility (<!--…-->,<script>,<textarea>) or disallow SE indexation (<noindex>).
The masks can be:
[~*~] - any text.
[~!~] - any symbol.
Special purpose masks:
[~+'text'~] - 'true' value, if text specified in quotation marks was found.
[~-'text'~] - 'true' value, if text specified in quotation marks was not found.
[~=+'text1',-'text2'~] - 'true' value, if the sum of texts equals zero (for instance, the same number of opening and closing HTML tags). When the sum of texts is counted, presence of text1 increases the sum by 1, while presence of text2 decreases the sum by 1.
[~%+'text1',-'text2'~] - 'true' value, if the sum of text does not equal zero (for example, different number of opening and closing HTML tags).
[~>+'text1',-'text2'~] - 'true' value if the sum of texts is >0 (for example, there were more opening HTML tags than closing ones).
[~<+'text1',-'text2'~] - 'true' value, if the sum of texts is <0.
[~?+'text1',-'text2'~] - 'true' value, if text2 follows each text1 (checking whether HTML tags are closed, where text1 is an opening tag and text 2 is the closing one).
Sample 1.
Detecting a link in site code and determining whether it is in page body (between <body< and </body<).
Required content:
<body[~*~]<a href="http://mydomain.com">My Link</a>[~*~]</body>
Sample 2.
Checking whether your link is commented out (we disallow your link to follow unclosed tags like '<!--', '<script>','<textarea>').
Forbidden content 1:
<body[~?+'<!--',-'-->'~]<a href="http://mydomain.com">My Link</a>
Forbidden content 2:
<body[~?+'<script',-'</script>'~]<a href="http://mydomain.com">My Link</a>
Forbidden content 3:
<body[~?+'<textarea',-'</textarea>'~]<a href="http://mydomain.com">My Link</a>
Sample 3.
Checking whether SE indexation of a page is disallowed through <meta name="robots" content="noindex"> (we disallow <noindex> to be contained in the meta fields).
Forbidden content:
<meta[~-'>'~]noindex
Sample 4.
Checking whether the page links to mydomain.com with "MyDomain.com Site" as link text (we check this with a number of HTML link code variants).
Required content:
<a[~-'>'~]href=[~!~]http:// mydomain.com[~*~]>[~-'</a>'~][~*~]MyDomain.com Site [~*~]</a>