Reading the charts

mizifih · 12. August 2013

I mean you, LOL. Really, Can someone help me with the graphs? What kind of information can i get from all this? What should I pay attention?

MEMORY USAGE

Zitat

LOAD AVERAGE

Zitat

CPU USAGE

Zitat

ETH0 TRAFFIC

Zitat

DISK USAGE

Zitat

ryecoaaron · 12. August 2013

The majority of the graphs (memory usage, disk usage) should ideally not be all red. Load average should be well under 1 unless you are doing transcoding or transferring a lot of information over a gigabit connection. eth0 traffic could be anything depending on how much information you are transferring to/from the server.

mizifih · 12. August 2013

Zitat von "ryecoaaron"

The majority of the graphs (memory usage, disk usage) should ideally not be all red. Load average should be well under 1 unless you are doing transcoding or transferring a lot of information over a gigabit connection. eth0 traffic could be anything depending on how much information you are transferring to/from the server.

I don't transcode, but I do unzip/unrar and i think that those load pikes are just that. I was wondering if there is a way to pull out from system how much I have transferred, like daily, weekly and montlhy. Like how much GBs I have downloaded and uploaded.

And I'm a little confused about Disk Usage. I think that those numbers and graphs are telling me how much TB I once had and how much I'm using right now. It's just that, right, I'm not crazy?

ryecoaaron · 12. August 2013

There isn't a graph for transferred data. The ifconfig command will show you the total transferred since last reboot.

The disk usage chart is showing that you are adding data over time. It shows you were using close to zero at the beginning of July (week 29) and now you are using close to 3 TB (week 33). The different charts are just zooming in to show you a small, most recent time period (that applies to all charts).

mizifih · 12. August 2013

Zitat von "ryecoaaron"

There isn't a graph for transferred data. The ifconfig command will show you the total transferred since last reboot.

The disk usage chart is showing that you are adding data over time. It shows you were using close to zero at the beginning of July (week 29) and now you are using close to 3 TB (week 33). The different charts are just zooming in to show you a small, most recent time period (that applies to all charts).

Hum... what about a cron job to save a txt with my daily transfers? Is it possible? Can you help me with that?

davidh2k · 12. August 2013

You could use an init script that is executed on shutdown.

simple script would be like

Code

ifconfig eth0 >> /var/log/traffic.log

Greetings
David

ryecoaaron · 12. August 2013

If you had a router running dd-wrt or tomato, you would have those numbers Here is mine from tomato:

Like David said, I would add a cron job to run at midnight each night. If you want just data, you could narrow it down to:

Code

ifconfig eth0 | grep "RX bytes" >> /var/log/traffic.log

This number will be the total though. If you shutdown or reboot in the middle of the day, it will be reset.

davidh2k · 12. August 2013

Zitat von "ryecoaaron"

This number will be the total though. If you shutdown or reboot in the middle of the day, it will be reset.

And thats why i suggessted an rc.d/init script that runs on shutdown.

Greetings
David

ryecoaaron · 12. August 2013

Zitat von "davidh2k"

And thats why i suggessted an rc.d/init script that runs on shutdown.

He wants daily transfers though. If you write to the log each night at midnight, you just have to subtract the amount from the previous entry to determine that day's usage. If you shutdown each day, then it would work great

davidh2k · 12. August 2013

Bash

#!/bin/sh


traffic=`ifconfig eth0 | grep "RX bytes"`


echo "$(date +%F_%T) | $traffic" >>/var/log/traffic.txt

Greetings
David

ryecoaaron · 12. August 2013

Even better because that will show the date with the usage

davidh2k · 12. August 2013

Thats what I do with the temps of my hard disks that are attached to my 3ware controller.

Greetings
David

mizifih · 12. August 2013

Zitat von "davidh2k"

Bash

#!/bin/sh


traffic=`ifconfig eth0 | grep "RX bytes"`


echo "$(date +%F_%T) | $traffic" >>/var/log/traffic.txt

Greetings
David

I know what it's doing and I know it's a script. I just don't have a clue where to put it.

On a side note, the command saves this:

Code

RX bytes:1437772732395 (1.3 TiB)  TX bytes:247554670363 (230.5 GiB)

Is there a way to make it saves this instead:

Code

RX bytes:1437772732395 (1.3 TiB);TX bytes:247554670363 (230.5 GiB);

This way it can easily get converted into charts and spreadsheets

We should put all these constructive discussion on a single thread after we get things done

This is interesting

mizifih · 12. August 2013

Zitat von "davidh2k"

Thats what I do with the temps of my hard disks that are attached to my 3ware controller.

Greetings
David

Can you share that!? I'd love to have a temp chart on top of that.

ryecoaaron · 12. August 2013

This will add the semi-colons you want.

Bash

#!/bin/bash


traffic=`ifconfig eth0 | grep "RX bytes"`
traffic=${traffic//)/);}


echo "$(date +%F_%T) | $traffic" >>/var/log/traffic.txt

You could save it in the /root/ directory.

mizifih · 12. August 2013

Zitat von "ryecoaaron"
This will add the semi-colons you want.
Bash
#!/bin/bash


traffic=`ifconfig eth0 | grep "RX bytes"`
traffic=${traffic//)/);}


echo "$(date +%F_%T) | $traffic" >>/var/log/traffic.txt
You could save it in the /root/ directory.

I save it like what? On windows I would save it as a ".bat" file and use scheduler to run it when I want it, but on Linux, I have no clue...

Sorry to bother you with that. Should I save this as a ".sh" file?

ryecoaaron · 12. August 2013

Here is what you want to do:

- Login via ssh as root
- nano /root/net_usage.sh
- Paste code into file
- ctrl-O to save
- ctrl-X to exit
- chmod +x /root/net_usage.sh
- Login to web interface and go to cron jobs tab
- Pick minute as 0, hour as 0, user as root, command as /root/net_usage.sh
- Click OK

mizifih · 12. August 2013

Zitat von "ryecoaaron"

Here is what you want to do:

- Login via ssh as root
- nano /root/net_usage.sh
- Paste code into file
- ctrl-O to save
- ctrl-X to exit
- chmod +x /root/net_usage.sh
- Login to web interface and go to cron jobs tab
- Pick minute as 0, hour as 0, user as root, command as /root/net_usage.sh
- Click OK

Alles anzeigen

Changed

Code

echo "$(date +%F_%T) | $traffic" >>/var/log/traffic.txt

into

Code

echo "$(date +%F_%T);$traffic" >>/var/log/traffic.txt

But I'm still getting

Code

2013-08-12_17:27:31;          RX bytes:1444736809975 (1.3 TiB);  TX bytes:247789621639 (230.7 GiB);

Lots of space between date-time. Can I remove all that space between date_time and RX or it's just something I gotta live with?

ryecoaaron · 12. August 2013

How's this? The first sed takes out ALL of the spaces. The second sed puts a space back in before each (. You can remove the second one if you don't need a space there.

Bash

#!/bin/bash


traffic=`ifconfig eth0 | grep "RX bytes"`
traffic=${traffic//)/);}
traffic=$(sed -e 's/ \+//g' <<<"$traffic")
traffic=$(sed -e 's/(/ (/g' <<<"$traffic")
echo "$(date +%F_%T);$traffic" >>/var/log/traffic.txt

My output is:

Code

2013-08-12_15:45:10;RXbytes:1816562499 (1.6GiB);TXbytes:2776300280 (2.5GiB);

davidh2k · 12. August 2013

Zitat von "mizifih"

Sorry to bother you with that. Should I save this as a ".sh" file?

Unlike Windows, Unix does not care about the filetype by extension, but due to actual content. *.sh is a good way to save your shell files.

Zitat von "mizifih"

Can you share that!? I'd love to have a temp chart on top of that.

Sure:

smart3ware.sh

Code

for number in 0 1 2 3 4 6 7; do


        temp1=$(tw_cli /c0/p$number show temperature | cut -f2 -d"=" | sed 's/ $
        sum="$sum $number:($(echo ${temp1:-8})Â°)"


done


echo "$(date +%F_%T) | $sum" >>/var/log/pall.txt

Alles anzeigen

Output looks like this:

Code

root@chap:~# tail /var/log/pall.txt
2013-08-12_19:15:02 |  0:(32°) 1:(32°) 2:(32°) 3:(32°) 4:(33°) 6:(8°) 7:(8°)
2013-08-12_19:18:02 |  0:(32°) 1:(32°) 2:(32°) 3:(32°) 4:(33°) 6:(8°) 7:(8°)
2013-08-12_19:21:02 |  0:(32°) 1:(32°) 2:(32°) 3:(32°) 4:(33°) 6:(8°) 7:(8°)
2013-08-12_19:24:02 |  0:(32°) 1:(32°) 2:(32°) 3:(32°) 4:(33°) 6:(8°) 7:(8°)
2013-08-12_19:27:02 |  0:(32°) 1:(32°) 2:(32°) 3:(32°) 4:(33°) 6:(8°) 7:(8°)
2013-08-12_19:30:01 |  0:(32°) 1:(32°) 2:(32°) 3:(32°) 4:(33°) 6:(8°) 7:(8°)
2013-08-12_19:33:02 |  0:(32°) 1:(32°) 2:(32°) 3:(32°) 4:(33°) 6:(8°) 7:(8°)
2013-08-12_19:36:02 |  0:(32°) 1:(32°) 2:(32°) 3:(32°) 4:(33°) 6:(8°) 7:(8°)
2013-08-12_19:39:01 |  0:(32°) 1:(32°) 2:(32°) 3:(32°) 4:(33°) 6:(8°) 7:(8°)
2013-08-12_23:51:02 |  0:(26°) 1:(25°) 2:(25°) 3:(25°) 4:(26°) 6:(8°) 7:(8°)
root@chap:~#

Alles anzeigen

You can grep to see highest tempatures etc. pp.

Code

root@chap:~# cat /var/log/pall.txt | grep 42°
root@chap:~# cat /var/log/pall.txt | grep 41°
root@chap:~# cat /var/log/pall.txt | grep 40°
2013-07-25_18:21:03 |  0:(38°) 1:(38°) 2:(38°) 3:(37°) 4:(40°) 6:(8°) 7:(8°)
2013-07-25_18:24:03 |  0:(38°) 1:(38°) 2:(38°) 3:(37°) 4:(40°) 6:(8°) 7:(8°)
2013-07-25_18:27:02 |  0:(38°) 1:(38°) 2:(38°) 3:(37°) 4:(40°) 6:(8°) 7:(8°)
2013-07-25_18:48:03 |  0:(38°) 1:(38°) 2:(38°) 3:(37°) 4:(40°) 6:(8°) 7:(8°)
2013-07-25_18:51:03 |  0:(38°) 1:(38°) 2:(38°) 3:(37°) 4:(40°) 6:(8°) 7:(8°)
2013-07-25_18:54:03 |  0:(38°) 1:(38°) 2:(38°) 3:(37°) 4:(40°) 6:(8°) 7:(8°)
2013-07-25_18:57:03 |  0:(38°) 1:(38°) 2:(38°) 3:(37°) 4:(40°) 6:(8°) 7:(8°)
2013-07-25_19:00:04 |  0:(38°) 1:(38°) 2:(38°) 3:(37°) 4:(40°) 6:(8°) 7:(8°)
2013-07-25_19:03:05 |  0:(38°) 1:(38°) 2:(38°) 3:(37°) 4:(40°) 6:(8°) 7:(8°)
2013-07-25_19:06:03 |  0:(38°) 1:(38°) 2:(38°) 3:(37°) 4:(40°) 6:(8°) 7:(8°)
2013-07-25_19:09:04 |  0:(38°) 1:(38°) 2:(38°) 3:(37°) 4:(40°) 6:(8°) 7:(8°)
2013-07-25_19:12:04 |  0:(38°) 1:(38°) 2:(38°) 3:(37°) 4:(40°) 6:(8°) 7:(8°)
2013-07-25_19:15:03 |  0:(38°) 1:(38°) 2:(39°) 3:(37°) 4:(40°) 6:(8°) 7:(8°)
2013-07-25_19:18:03 |  0:(38°) 1:(38°) 2:(39°) 3:(37°) 4:(40°) 6:(8°) 7:(8°)
2013-07-25_19:21:03 |  0:(38°) 1:(38°) 2:(39°) 3:(37°) 4:(40°) 6:(8°) 7:(8°)
2013-07-25_19:24:05 |  0:(38°) 1:(38°) 2:(39°) 3:(37°) 4:(40°) 6:(8°) 7:(8°)
2013-07-25_19:27:03 |  0:(39°) 1:(38°) 2:(39°) 3:(37°) 4:(40°) 6:(8°) 7:(8°)
2013-07-25_19:30:04 |  0:(39°) 1:(38°) 2:(39°) 3:(37°) 4:(40°) 6:(8°) 7:(8°)
2013-07-25_19:33:04 |  0:(39°) 1:(38°) 2:(39°) 3:(37°) 4:(40°) 6:(8°) 7:(8°)
2013-07-25_19:36:03 |  0:(39°) 1:(38°) 2:(39°) 3:(37°) 4:(40°) 6:(8°) 7:(8°)
2013-07-25_19:39:04 |  0:(39°) 1:(38°) 2:(39°) 3:(37°) 4:(40°) 6:(8°) 7:(8°)
2013-07-25_19:42:03 |  0:(39°) 1:(38°) 2:(39°) 3:(37°) 4:(40°) 6:(8°) 7:(8°)
2013-07-25_19:45:03 |  0:(39°) 1:(38°) 2:(39°) 3:(37°) 4:(40°) 6:(8°) 7:(8°)
2013-07-25_19:48:04 |  0:(39°) 1:(38°) 2:(39°) 3:(37°) 4:(40°) 6:(8°) 7:(8°)
2013-07-25_19:51:03 |  0:(39°) 1:(38°) 2:(39°) 3:(37°) 4:(40°) 6:(8°) 7:(8°)
2013-07-25_19:54:03 |  0:(39°) 1:(39°) 2:(39°) 3:(37°) 4:(40°) 6:(8°) 7:(8°)
2013-07-25_19:57:03 |  0:(39°) 1:(39°) 2:(39°) 3:(37°) 4:(40°) 6:(8°) 7:(8°)
2013-07-25_20:00:03 |  0:(39°) 1:(39°) 2:(39°) 3:(37°) 4:(40°) 6:(8°) 7:(8°)
2013-07-25_20:03:03 |  0:(39°) 1:(39°) 2:(39°) 3:(37°) 4:(40°) 6:(8°) 7:(8°)
2013-07-25_20:06:04 |  0:(39°) 1:(39°) 2:(39°) 3:(37°) 4:(40°) 6:(8°) 7:(8°)
2013-07-25_20:09:03 |  0:(39°) 1:(39°) 2:(39°) 3:(37°) 4:(40°) 6:(8°) 7:(8°)
2013-07-25_20:12:03 |  0:(39°) 1:(39°) 2:(39°) 3:(37°) 4:(40°) 6:(8°) 7:(8°)
2013-07-25_20:15:03 |  0:(39°) 1:(39°) 2:(39°) 3:(37°) 4:(40°) 6:(8°) 7:(8°)
2013-07-25_20:18:04 |  0:(39°) 1:(39°) 2:(39°) 3:(37°) 4:(40°) 6:(8°) 7:(8°)
2013-07-25_20:21:03 |  0:(39°) 1:(39°) 2:(39°) 3:(37°) 4:(40°) 6:(8°) 7:(8°)
2013-07-25_20:24:04 |  0:(39°) 1:(39°) 2:(39°) 3:(37°) 4:(40°) 6:(8°) 7:(8°)
2013-07-25_20:27:03 |  0:(39°) 1:(39°) 2:(39°) 3:(37°) 4:(40°) 6:(8°) 7:(8°)
2013-07-25_20:30:03 |  0:(39°) 1:(39°) 2:(39°) 3:(37°) 4:(40°) 6:(8°) 7:(8°)
2013-07-25_20:33:04 |  0:(39°) 1:(39°) 2:(39°) 3:(37°) 4:(40°) 6:(8°) 7:(8°)
2013-07-25_20:36:03 |  0:(39°) 1:(39°) 2:(39°) 3:(37°) 4:(40°) 6:(8°) 7:(8°)
2013-07-25_20:39:03 |  0:(39°) 1:(39°) 2:(39°) 3:(37°) 4:(40°) 6:(8°) 7:(8°)
2013-07-25_20:42:03 |  0:(39°) 1:(38°) 2:(39°) 3:(37°) 4:(40°) 6:(8°) 7:(8°)
2013-07-25_20:45:03 |  0:(39°) 1:(38°) 2:(39°) 3:(37°) 4:(40°) 6:(8°) 7:(8°)
2013-07-25_20:48:03 |  0:(39°) 1:(38°) 2:(39°) 3:(37°) 4:(40°) 6:(8°) 7:(8°)
root@chap:~#

Alles anzeigen

Side Note: Port 6 and 7 are no longer attached, but i still grab them as it does not generate any errors.

Greetings
David

PS: I did not wrote the script myself, i made an early version myself and a friend from a LAN Party pimped it a 'bit'.

Jetzt mitmachen!