Author Archives: ryltechadmin

« All posts

OS Tools – Network Analysis

Monitoring your network transportation from time to time is important in order to know that your network equipment is functioning properly, that your machines are only accessed by authorized IP addresses and that there’s no suspicious data transfer to undesirable destinations or unnecessary data transfer within your network.

Usually users and managers only check the network performance when they notice slowness in upload and download processes and perform thorough analysis only when they have a strong suspicion of an intrusion. Avoiding regularly monitoring the network transportation might be harmful for your organization, therefore you need a tool to regularly monitor your network and allow you to view all the relevant information about what’s happening in your network.

AimBetter enables you to easily analyze your network performance and transportation in real time and for past issues, as it saves logs of your systems’ data for as long as you set.

In AimBetter, the Network section of OS Tools is divided to 4 subsections: TCP, Interface, IP and UDP.
The Network section of the OS Tools is a complementary to the Network section of the performance screen as it gives you detailed information about the inbound and outbound traffic in your network, TCP statistics, Network interface metrics, IP metrics and UDP metrics.

The TCP subsection presents the following information for TCP: TCP outbound traffic, TCP inbound traffic, TCP version 4 metrics and TCP version 6 metrics.





The interface subsection presents the following information for the network interface counters: Counter name, Instance name, Mean value, Minimum value and Maximum value. All values are for the most recent round minute.


The IP subsection presents the following information for IP counters: Counter name, Mean value, Minimum value and Maximum value. All values are for the most recent round minute.



The UDP subsection presents the following information for UDP counters: Counter name, Mean value, Minimum value and Maximum value. All values are for the most recent round minute.


As shown above, the following metrics are monitored: Connection failures, connections active, connections established, connections passive, connections reset, segments received/second, segments retransmitted/second, segments sent/second, total segments/second, bytes received/second, bytes sent/second, total bytes/second, current bandwidth, offloaded connections, output queue length, packets outbound discarded, packets outbound errors, packets/second, offloaded connections, output queue length, datagrams forwarded/second, datagrams outbound discarded, datagrams outbound no route, datagrams received address errors, datagrams received delivered/second, datagrams received discarded, datagrams received header errors, datagrams received unknown protocol, datagrams received/second, datagrams sent/second, total datagrams/second, fragment re-assembly failures, fragmentation failures, fragmented datagrams/second, fragments created/second, fragments re-assembled/second, fragments received/second, datagrams with no port/second, datagrams received errors, etc.

AimBetter provides thorough information about your network transportation and metrics and displays every detail that has a meaning regarding your network transportation, performance, metrics, etc. and it also helps you monitor the security of your network. With AimBetter you can be sure to have all the important information you need regarding your network to keep it well functioning and secure and easily troubleshoot it whenever needed.

« All posts

Identifying Server Problems with Trend Analysis

One of the first questions that must be answered when beginning to perform tests on SQL servers or operating systems is to identify the minimum activity of the system, or, in other words, to establish the Baseline. Understanding and documenting the normal functioning of the system will be make it easy to spot unusual behavior should it occur. Likewise, one must know how the system parameters behave during certain hours and on special days (such as paydays, monthly fluctuations in activity and increased momentum around holidays and festivals).
Messages to the system increase awareness of unusual activity in the service and encourage proactive measures to inhibit potential problems. Among the abnormal activities that should be monitored are increased CPU consumption, consumption of drive space, swelling or overuse of the log database, connection errors and others.

The Big Problem

Recently, with the help of AimBetter, a serious blunder was avoided when a developer ran a report created by unusual activity in TEMPDB; within a half hour the drive lost 50GB. Though such a lack of space on the drive could bring things to a grinding halt, but in this case, the problem wasn’t that the IT team left too little space to run the report. Instead, the error was potentially caused by a developer who ran a complex report with secondary data, and he forgot to date the report.

The Quick Resolution

First, we received an alert by email.

We entered the system and realized that the problem began within the past half hour.


We reviewed the logs and discovered the problem


Eventually we alerted the developer to the serious nature of his error the report requires normal date parameters in order to run properly. We then reduced the TEMPDB without any resulting downtime and returned the system to optimal function.
Without a proper tend analysis and documentation of the source of the decline we would not have been able to identify the problem or its starting point so quickly. As it turned out, a mere half hour to evaluate, inspect and repair prevented significant damage, downtime and frayed nerves.

« All posts

New module – SQL Server event log

One of the biggest problems in detecting faults in SQL is the monitoring of the error LOG SQL SERVER which is often, but not always, built as a sequence of errors. In many cases, the error can occur over several lines, making it difficult to quickly identify the problem, even when using the Search screen. Identification of errors before the users do or before the system collapses is imperative, and proactive server management is the only way to ensure that errors are prevented.

Proactive management of servers

The AimBetter system was developed to address these challenges with a reliable approach that includes several steps, including:

  • Scanning the system logs and removing irrelevant logs and non-error information
  • Counting system errors by the amount of real errors and not by the amount of errors that the system itself produces

  • Cataloging system errors and displays them with a convenient and simple UI, so that at one glance users can see which errors occurred and at what time they occurred
  • Allowing for analysis and comparison of the errors on a daily, monthly or weekly basis to build a deeper understanding of when the errors occur and whether they are serious, and to highlight abnormalities in the system that have formed or may be in the process of forming
מבט על הלוג A look at the log arranged by category

A look at the log arranged by category

Analysis and comparison of errors throughout Daily/Weekly/Monthly comparisons

Analysis and comparison of errors throughout Daily/Weekly/Monthly comparisons

A look at the actual error record as it appears in the ERROR LOG – Every error can occur over multiple lines

A look at the actual error record as it appears in the ERROR LOG – Every error can occur over multiple lines