Install Smokeping On Windows
2021年9月15日Download here: http://gg.gg/vzdbc
Tutorial
*Install Smokeping On Windows 10 Pro
*Smokeping Setup
*Smokeping For Windows 10
*Install Smokeping On Windows Media PlayerIntroduction
SmokePing is a network latency tracking tool. Tracking your server’s network latency can give you a useful picture of the overall health and availability of your server. For example, it can help you determine if your network is overloaded or alert you to packet loss, which may indicate an incorrect router configuration or downed device.
Apt-get update && apt-get upgrade apt-get install smokeping apt-get install apache2 sendmail a2enmod cgi service apache2 restart cd /etc/smokeping/config.d.
*Smokeping is pretty good for this. It’ll show latency as well as packet loss. It’ll show latency as well as packet loss. Edit: Looks like Smokeping needs to be patched to run on Windows.
*See the smokepinginstall document. 1.38 to 1.40 The new navigation feature. The big visible difference between 1.38 and 1.40 is the new browser navigation feature: when clicking on the graphs in detail view you can select different time ranges for the graph. The creation of this feature has been sponsored by BeverlyCorp.com.
SpokePing’s creator, Tobias Oetiker, also created a data logging and time series graphing utility called RDDtool. SmokePing uses RDDtool, so you have access to its sophisticated graphing capabilities too.
This tutorial will show you how to install and configure SmokePing with Apache on FreeBSD.Prerequisites
To follow this tutorial, you will need:
*One FreeBSD 11 server with a root user. On DigitalOcean, the default freebsd user is fine.
A FreeBSD Droplet requires an SSH key for remote access. For help on setting up an SSH key, read How To Configure SSH Key-Based Authentication on a FreeBSD Server. To learn more about logging into your FreeBSD Droplet and basic management, check out the Getting Started with FreeBSD tutorial series.Step 1 — Installing Apache with FastCGI Support
To begin, we’ll install the Apache web server and its FastCGI module, which SmokePing uses to power its web interface.
First, update your server’s repository information.
To install Apache with FastCGI support, you can just tell pkg to install the FastCGI module. pkg will handle all dependencies needed by the module itself, so it will automatically install the main Apache package as well.
Confirm the installation by pressing Y. Once Apache is installed, we’ll need to customize it to get it working.Step 2 — Configuring Apache
There are two small changes we’ll need to make to Apache: updating some server information in httpd.conf and enabling the FastCGI module.
First, open /usr/local/etc/apache24/httpd.conf for editing.
Edit the two directives below. Set ServerAdmin to your email address, and uncomment (by deleting the preceeding #) and edit ServerName to your server’s IP address.
Save and close the file.
FastCGI is not a default module, so we have to add it to Apache’s configuration to load it. To load the module, we’ll need to create a new configuration file in /usr/local/etc/apache24/modules.d/ and add the module information.
The module README, found in /usr/local/etc/apache24/modules.d/README_modules.d, says “files are automatically included if the name begins with a three digit number followed by _ and ending in .conf”. To comply with this, we’ll create a file called 001_fcgid.conf.
Paste the following into the file, which tells Apache to load the module and where to find it./usr/local/etc/apache24/modules.d/001_fcgid.conf
Save and close the file.
Now that Apache with FastCGI is set up, we can install SmokePing itself.Step 3 — Installing and Configuring SmokePing
Installing SmokePing is straightforward because it’s in the package repository.
SmokePing’s configuration is in /usr/local/etc/smokeping/config by default. You’ll need to edit this file to customize a few fields.
You’ll need to edit four fields in the ***General*** section:
*owner, which should have your name
*contact, which should have your email address
*imgurl, which should be updated to use your server’s IP address
*cgiurl, which should also be updated to use your server’s IP address
Here’s what the file will look like when you’re done:
SmokePing has support for a master/slave architecture, to use their terminology. In this tutorial, we’re only setting up SmokePing on one machine. Consequently, comment out the *** Slaves *** section of the configuration by prefacing each line with a #./usr/local/etc/smokeping/config
Keep this file open, as we’ll continue editing it in the next step to set up SmokePing’s targets.Step 4 — Defining Targets
The last thing we’ll add to SmokePing’s configuration file are targets. To paraphrase SmokePing’s explanation, targets are a hierarchical list of hosts which mark the endpoints of the network connections the system should monitor. Every target will specify what kind of probe to use, which integrate an external ping command into SmokePing (like fping).
In this tutorial, we’ll set up a configuration that monitors the latency between your server and two FreeBSD pkg mirrors. We’ll create three graphs: two that shows the latency for each of the two mirror servers independently, and one that shows the latency of both mirror servers at once.
Targets are configured In the *** Targets *** section of SmokePing’s configuration file. There are many variables you can use to customize your targets, but here, we’ll just use the following:
*probe: The ping command to use to probe for latency.
*menu: The default menu to show in the GUI.
*title: The title of the corresponding SmokePing page.
*remark: The text that will appear on the page.
*host: The IP address or hostname endpoint.
First, delete the existing sample configuration so the end of your file looks like this:**Targets** Section on /usr/local/etc/smokeping/config
Then, copy and paste the following configuration under the existing default settings.**Targets** Section on /usr/local/etc/smokeping/config
Let’s explain what this is doing.
Targets are hierarchical, meaning you can nest levels of targets to help with organization. Each nested level of targets will create a new submenu in the SmokePing GUI showing different graphs.
In our configuration, the + targets line means we’re defining a nested level of targets. Nested targets will inherent the values of their parent configuration, so we don’t need to include the probe = FPing line again if we want these targets to use the same probe. However, we updated the title and menu variables for the new subsection, so the page on the site will have a different title and menu.
The ++ pkgmir_xxx lines mean we’re defining a second nested level which includes two targets. These have a host variable for the address of the endpoint, which are our two FreeBSD pkg mirror servers.
The above configuration will create one graph per target. Below it, add one more section to combine multiple targets into one graph.**Targets** Section on /usr/local/etc/smokeping/config
Note that this section uses the two targets we already configured (/targets/pkgmir_nyi and /targets/pkgmir_ydx).
Finally, save and close the file. SmokePing’s configuration is all set up, so let’s connect Apache and SmokePing and start the respective services.Step 5 — Connecting and Enabling the Services
Create a configuration file for Apache in /usr/local/etc/apache24/Includes/ called smokeping.conf.
Here, we’ll add the information Apache needs to handle requests to SmokePing’s web interface. Copy and paste the following into the new file:
This tells Apache where to find SmokePing’s files and makes sure it uses FastCGI.
The default service configuration for Apache and SmokePing will not start the processes at boot. To change that, execute the following two commands.
The output for the aforementioned two commands should look like this:
Now, you can start the Apache service.
If it starts successfully, you will see:
If not, you’ll see an error which you can use to debug any issues in the configuration file. Finally, start the SmokePing service.
Everything is running, so let’s see our graphs in action.Step 6 — Accessing SmokePing’s Web Interface
You can access SmokePing’s web interface by visiting http://your_server_ip/smokeping in your favorite browser. You’ll see a page with the title and remark you specified in step 5. If you didn’t change any of the values, it will look like this:
You can see your graphs by navigating the menu on the left. Notice the Targets and Multi Targets options in the menu; these are the targets we defined in Step 5.
Click on Targets. You’ll see the first two graphs we defined, one for each mirror server. On the left, you’ll see the nested list of targets, which mirrors our configuration file.
Next, click on Multi Targets. You’ll see the combined graph here.
If you run into trouble, you can check the logs for help in diagnosing the problem. Apache records its logs in two files: /var/log/httpd-access.log and /var/log/httpd-error.log. SmokePing has one log file, which is /var/log/smokeping.log. Remember that if you change SmokePing’s configuration, you’ll need to reload the daemon with sudo service smokeping reload.Conclusion
In this tutorial, you set up SmokePing with Apache and created some example probes to test logging and graphing. From here, you can customize your probes and graphs to whatever you’d like to track. SmokePing has a lot of other features, like slaves, alerts, and support for your own mail server. Check out SmokePing’s official documentation for more detail.
Fault diagnosis on Local Area Networks (LANs) can be tricky at the best of times. Things get even more complex when you’re dealing with Wide Area Networks (WANs).
Smokeping is one great tool that can help you deal with the complexity. In this article, we’ll learn how to use Smokeping to identify and fix network problems.Introduction
So, what does Smokeping do and how does it work, you ask? Primarily, Smokeping is used to measure jitter and latency using ICMP echos (in other words, pings). It then uses rrdtool to graph the information for later analysis. You can choose how often you want to ping a destination and how many pings you want to send when you do. Smokeping’s Key Features
*Excellent latency visualisation
*Interactive graph frontend
*Plugins to allow measurement of latency for other protocols
*Master/Slave system for distributed measurement (i.e. multiple locations)
*Alerting system
*Latency charts with the most interesting graphs
*Free and Open-SourceSmokeping Configuration and Best Practices
I recommend these best practices based on my own experience having used Smokeping over a number of years to analyze network latency and illustrate packet loss.
I suggest starting by making sure that 20 pings are sent every 60 seconds. It’s important to consider the relevance of this when you first deploy Smokeping as changes to these parameters will break your RRD graphs and require you to start from scratch. To set this rate, edit the Database file located in Smokeping’s config.d directory:
Next, configure the owner and contact e-mail address of your Smokeping installation by editing the General file in the same directory:Configuring Ping Targets
Now onto the fun stuff!Install Smokeping On Windows 10 Pro
When using Smokeping, you’re going to want to start graphing the latency to a multitude of destinations. I tend to pick servers that I want to monitor and then a few “control” subjects, like Google’s DNS servers or my ISP’s DNS servers. This will allow you to compare any lossy graphs to see if there is a common issue related to your Smokeping network connection or if it’s a specific destination. Indeed, you can also see if there are common issues on certain routed paths by doing this.Smokeping Setup
To configure your ping targets, open up the Targets file in the same directory as mentioned above. There is some default config in here to get you started and it’s quite straightforward to configure. As an example, here is my configuration for BBC News and Google U.K.:
To make this config live, simply restart Smokeping, then head over to your browser to see the changes.Smokeping For Windows 10Understanding the Graphs
Assuming you have configured Smokeping correctly, you’ll see something similar to the following (minus the populated graphs, of course). Allow a few minutes for a line measurement to begin to appear.
To further understand what we’re looking at, click into one of your graphs and you’ll see latency information over the last 3 hours, 30 hours, 10 days and 360 days. The data will be averaged over these time periods.
The graph below indicates excellent latency with a consistent ping time of around 12ms and no packet loss.Install Smokeping On Windows Media Player
If there were packet loss, you’d see a percentage figure mentioned alongside the “packet loss” side heading and a colour relative to the percentage on the graph. An example illustrating some packet loss is shown below (note the bits on the graph in blue):Conclusion
Smokeping is a useful tool that can aid DevOps Engineers and Network Engineers alike in diagnosing packet loss on their networks, or on their ISP’s networks. It can illustrate congestion issues, contention issues and poor routing. Having graphs to provide to your ISP or other service provider when raising a complaint can be very useful point of information to bolster your case, and to assist them in diagnosing a problem.
Although I have tried many other tools for graphing latency, I still find Smokeping to be the best around and would highly recommend it.Useful Links
*Smokeping: http://oss.oetiker.ch/smokeping/
*Different probes: http://oss.oetiker.ch/smokeping/probe/index.en.html
*Online demo: http://oss.oetiker.ch/smokeping-demo/?target=Customers.OP
*Usage statistics for Smokeping: http://oss.oetiker.ch/smokeping/stats.en.html
*Active monitoring system SmokePing https://github.com/oetiker/SmokePing
Download here: http://gg.gg/vzdbc
https://diarynote-jp.indered.space
Tutorial
*Install Smokeping On Windows 10 Pro
*Smokeping Setup
*Smokeping For Windows 10
*Install Smokeping On Windows Media PlayerIntroduction
SmokePing is a network latency tracking tool. Tracking your server’s network latency can give you a useful picture of the overall health and availability of your server. For example, it can help you determine if your network is overloaded or alert you to packet loss, which may indicate an incorrect router configuration or downed device.
Apt-get update && apt-get upgrade apt-get install smokeping apt-get install apache2 sendmail a2enmod cgi service apache2 restart cd /etc/smokeping/config.d.
*Smokeping is pretty good for this. It’ll show latency as well as packet loss. It’ll show latency as well as packet loss. Edit: Looks like Smokeping needs to be patched to run on Windows.
*See the smokepinginstall document. 1.38 to 1.40 The new navigation feature. The big visible difference between 1.38 and 1.40 is the new browser navigation feature: when clicking on the graphs in detail view you can select different time ranges for the graph. The creation of this feature has been sponsored by BeverlyCorp.com.
SpokePing’s creator, Tobias Oetiker, also created a data logging and time series graphing utility called RDDtool. SmokePing uses RDDtool, so you have access to its sophisticated graphing capabilities too.
This tutorial will show you how to install and configure SmokePing with Apache on FreeBSD.Prerequisites
To follow this tutorial, you will need:
*One FreeBSD 11 server with a root user. On DigitalOcean, the default freebsd user is fine.
A FreeBSD Droplet requires an SSH key for remote access. For help on setting up an SSH key, read How To Configure SSH Key-Based Authentication on a FreeBSD Server. To learn more about logging into your FreeBSD Droplet and basic management, check out the Getting Started with FreeBSD tutorial series.Step 1 — Installing Apache with FastCGI Support
To begin, we’ll install the Apache web server and its FastCGI module, which SmokePing uses to power its web interface.
First, update your server’s repository information.
To install Apache with FastCGI support, you can just tell pkg to install the FastCGI module. pkg will handle all dependencies needed by the module itself, so it will automatically install the main Apache package as well.
Confirm the installation by pressing Y. Once Apache is installed, we’ll need to customize it to get it working.Step 2 — Configuring Apache
There are two small changes we’ll need to make to Apache: updating some server information in httpd.conf and enabling the FastCGI module.
First, open /usr/local/etc/apache24/httpd.conf for editing.
Edit the two directives below. Set ServerAdmin to your email address, and uncomment (by deleting the preceeding #) and edit ServerName to your server’s IP address.
Save and close the file.
FastCGI is not a default module, so we have to add it to Apache’s configuration to load it. To load the module, we’ll need to create a new configuration file in /usr/local/etc/apache24/modules.d/ and add the module information.
The module README, found in /usr/local/etc/apache24/modules.d/README_modules.d, says “files are automatically included if the name begins with a three digit number followed by _ and ending in .conf”. To comply with this, we’ll create a file called 001_fcgid.conf.
Paste the following into the file, which tells Apache to load the module and where to find it./usr/local/etc/apache24/modules.d/001_fcgid.conf
Save and close the file.
Now that Apache with FastCGI is set up, we can install SmokePing itself.Step 3 — Installing and Configuring SmokePing
Installing SmokePing is straightforward because it’s in the package repository.
SmokePing’s configuration is in /usr/local/etc/smokeping/config by default. You’ll need to edit this file to customize a few fields.
You’ll need to edit four fields in the ***General*** section:
*owner, which should have your name
*contact, which should have your email address
*imgurl, which should be updated to use your server’s IP address
*cgiurl, which should also be updated to use your server’s IP address
Here’s what the file will look like when you’re done:
SmokePing has support for a master/slave architecture, to use their terminology. In this tutorial, we’re only setting up SmokePing on one machine. Consequently, comment out the *** Slaves *** section of the configuration by prefacing each line with a #./usr/local/etc/smokeping/config
Keep this file open, as we’ll continue editing it in the next step to set up SmokePing’s targets.Step 4 — Defining Targets
The last thing we’ll add to SmokePing’s configuration file are targets. To paraphrase SmokePing’s explanation, targets are a hierarchical list of hosts which mark the endpoints of the network connections the system should monitor. Every target will specify what kind of probe to use, which integrate an external ping command into SmokePing (like fping).
In this tutorial, we’ll set up a configuration that monitors the latency between your server and two FreeBSD pkg mirrors. We’ll create three graphs: two that shows the latency for each of the two mirror servers independently, and one that shows the latency of both mirror servers at once.
Targets are configured In the *** Targets *** section of SmokePing’s configuration file. There are many variables you can use to customize your targets, but here, we’ll just use the following:
*probe: The ping command to use to probe for latency.
*menu: The default menu to show in the GUI.
*title: The title of the corresponding SmokePing page.
*remark: The text that will appear on the page.
*host: The IP address or hostname endpoint.
First, delete the existing sample configuration so the end of your file looks like this:**Targets** Section on /usr/local/etc/smokeping/config
Then, copy and paste the following configuration under the existing default settings.**Targets** Section on /usr/local/etc/smokeping/config
Let’s explain what this is doing.
Targets are hierarchical, meaning you can nest levels of targets to help with organization. Each nested level of targets will create a new submenu in the SmokePing GUI showing different graphs.
In our configuration, the + targets line means we’re defining a nested level of targets. Nested targets will inherent the values of their parent configuration, so we don’t need to include the probe = FPing line again if we want these targets to use the same probe. However, we updated the title and menu variables for the new subsection, so the page on the site will have a different title and menu.
The ++ pkgmir_xxx lines mean we’re defining a second nested level which includes two targets. These have a host variable for the address of the endpoint, which are our two FreeBSD pkg mirror servers.
The above configuration will create one graph per target. Below it, add one more section to combine multiple targets into one graph.**Targets** Section on /usr/local/etc/smokeping/config
Note that this section uses the two targets we already configured (/targets/pkgmir_nyi and /targets/pkgmir_ydx).
Finally, save and close the file. SmokePing’s configuration is all set up, so let’s connect Apache and SmokePing and start the respective services.Step 5 — Connecting and Enabling the Services
Create a configuration file for Apache in /usr/local/etc/apache24/Includes/ called smokeping.conf.
Here, we’ll add the information Apache needs to handle requests to SmokePing’s web interface. Copy and paste the following into the new file:
This tells Apache where to find SmokePing’s files and makes sure it uses FastCGI.
The default service configuration for Apache and SmokePing will not start the processes at boot. To change that, execute the following two commands.
The output for the aforementioned two commands should look like this:
Now, you can start the Apache service.
If it starts successfully, you will see:
If not, you’ll see an error which you can use to debug any issues in the configuration file. Finally, start the SmokePing service.
Everything is running, so let’s see our graphs in action.Step 6 — Accessing SmokePing’s Web Interface
You can access SmokePing’s web interface by visiting http://your_server_ip/smokeping in your favorite browser. You’ll see a page with the title and remark you specified in step 5. If you didn’t change any of the values, it will look like this:
You can see your graphs by navigating the menu on the left. Notice the Targets and Multi Targets options in the menu; these are the targets we defined in Step 5.
Click on Targets. You’ll see the first two graphs we defined, one for each mirror server. On the left, you’ll see the nested list of targets, which mirrors our configuration file.
Next, click on Multi Targets. You’ll see the combined graph here.
If you run into trouble, you can check the logs for help in diagnosing the problem. Apache records its logs in two files: /var/log/httpd-access.log and /var/log/httpd-error.log. SmokePing has one log file, which is /var/log/smokeping.log. Remember that if you change SmokePing’s configuration, you’ll need to reload the daemon with sudo service smokeping reload.Conclusion
In this tutorial, you set up SmokePing with Apache and created some example probes to test logging and graphing. From here, you can customize your probes and graphs to whatever you’d like to track. SmokePing has a lot of other features, like slaves, alerts, and support for your own mail server. Check out SmokePing’s official documentation for more detail.
Fault diagnosis on Local Area Networks (LANs) can be tricky at the best of times. Things get even more complex when you’re dealing with Wide Area Networks (WANs).
Smokeping is one great tool that can help you deal with the complexity. In this article, we’ll learn how to use Smokeping to identify and fix network problems.Introduction
So, what does Smokeping do and how does it work, you ask? Primarily, Smokeping is used to measure jitter and latency using ICMP echos (in other words, pings). It then uses rrdtool to graph the information for later analysis. You can choose how often you want to ping a destination and how many pings you want to send when you do. Smokeping’s Key Features
*Excellent latency visualisation
*Interactive graph frontend
*Plugins to allow measurement of latency for other protocols
*Master/Slave system for distributed measurement (i.e. multiple locations)
*Alerting system
*Latency charts with the most interesting graphs
*Free and Open-SourceSmokeping Configuration and Best Practices
I recommend these best practices based on my own experience having used Smokeping over a number of years to analyze network latency and illustrate packet loss.
I suggest starting by making sure that 20 pings are sent every 60 seconds. It’s important to consider the relevance of this when you first deploy Smokeping as changes to these parameters will break your RRD graphs and require you to start from scratch. To set this rate, edit the Database file located in Smokeping’s config.d directory:
Next, configure the owner and contact e-mail address of your Smokeping installation by editing the General file in the same directory:Configuring Ping Targets
Now onto the fun stuff!Install Smokeping On Windows 10 Pro
When using Smokeping, you’re going to want to start graphing the latency to a multitude of destinations. I tend to pick servers that I want to monitor and then a few “control” subjects, like Google’s DNS servers or my ISP’s DNS servers. This will allow you to compare any lossy graphs to see if there is a common issue related to your Smokeping network connection or if it’s a specific destination. Indeed, you can also see if there are common issues on certain routed paths by doing this.Smokeping Setup
To configure your ping targets, open up the Targets file in the same directory as mentioned above. There is some default config in here to get you started and it’s quite straightforward to configure. As an example, here is my configuration for BBC News and Google U.K.:
To make this config live, simply restart Smokeping, then head over to your browser to see the changes.Smokeping For Windows 10Understanding the Graphs
Assuming you have configured Smokeping correctly, you’ll see something similar to the following (minus the populated graphs, of course). Allow a few minutes for a line measurement to begin to appear.
To further understand what we’re looking at, click into one of your graphs and you’ll see latency information over the last 3 hours, 30 hours, 10 days and 360 days. The data will be averaged over these time periods.
The graph below indicates excellent latency with a consistent ping time of around 12ms and no packet loss.Install Smokeping On Windows Media Player
If there were packet loss, you’d see a percentage figure mentioned alongside the “packet loss” side heading and a colour relative to the percentage on the graph. An example illustrating some packet loss is shown below (note the bits on the graph in blue):Conclusion
Smokeping is a useful tool that can aid DevOps Engineers and Network Engineers alike in diagnosing packet loss on their networks, or on their ISP’s networks. It can illustrate congestion issues, contention issues and poor routing. Having graphs to provide to your ISP or other service provider when raising a complaint can be very useful point of information to bolster your case, and to assist them in diagnosing a problem.
Although I have tried many other tools for graphing latency, I still find Smokeping to be the best around and would highly recommend it.Useful Links
*Smokeping: http://oss.oetiker.ch/smokeping/
*Different probes: http://oss.oetiker.ch/smokeping/probe/index.en.html
*Online demo: http://oss.oetiker.ch/smokeping-demo/?target=Customers.OP
*Usage statistics for Smokeping: http://oss.oetiker.ch/smokeping/stats.en.html
*Active monitoring system SmokePing https://github.com/oetiker/SmokePing
Download here: http://gg.gg/vzdbc
https://diarynote-jp.indered.space
コメント