Copia Traducida de Pingplotter - V5manual

21/9/2018PingPlotter
Manual deversión 5
https://www.pingplotter.com/export/manual 1/139
21/9/2018 PingPlotter
Esta documentación es un trabajo en progreso. Si tiene
alguna pregunta que no se haya abordado aquí actualmente,
no dude en ponerse en contacto con nosotros en
support@pingman.com.
© 1998, 2018 Pingman Tools, LLC

Todos los derechos reservados. Ninguna parte de este trabajo puede
reproducirse de ninguna forma ni por ningún medio (gráfico, electrónico o
mecánico, incluidos los sistemas de fotocopiado, grabación, grabación o
almacenamiento y recuperación de información) sin el permiso por escrito del
editor.
Los productos a los que se hace referencia en este documento pueden ser marcas
comerciales y / o marcas comerciales registradas de sus respectivos propietarios.
El editor y el autor no reclaman estas marcas comerciales.
Si bien se han tomado todas las precauciones en la preparación de este

documento, el editor y el autor no asumen ninguna responsabilidad por errores u
omisiones, o por daños resultantes del uso de la información contenida en este
documento o del uso de programas y código fuente que puedan acompañarlo. En
ningún caso el editor y el autor serán responsables de cualquier lucro cesante o
cualquier otro daño comercial causado o supuestamente causado directa o
indirectamente por este documento.
Tabla de
contenido de
Introducción
1.1 Bienvenida
1.2general
Funcionamiento
6.1 Descarga e instalación
6.2 Barra de destino
6.3 Gráfico de seguimiento
6.4 Gráficos de línea de tiempo
6.5 Gráficos de resumen

6.6 Espacios de trabajo
6.7interfaz web
Tareas comunes de la
7.1 Sustitución de variables
7.2 Guardado automático de datos
7.3 Ejecución como servicio
7.4 Manejo de múltiples destinos
7.5 Configuraciones nombradas
7.6 Informes
7.7 Exportación de datos para análisis posteriores
7.8 Cambios de ruta
7.9 Seguimiento de DNS dinámico
7.10 Compartir datos de PingPlotter con otros
https: // www.pingplotter.com/export/manual 3/139
Alertas
8.1 Creación / configuración de alertas
8.2 Configuración de correo electrónico (para alertas)
8.3 Notificación de eventos
8.4 Alertas de resolución de problemas
Eventos de alerta
9.1 Reproducir un sonido
9.2 Enviar correo electrónico
9.3 Registro en archivo
9.4 Cambio de icono de bandeja
9.5 Llamada REST web

9.6 Agregar / quitar del resumen
9.7 Iniciar ejecutable
Comprender la salida
10.1 Descubrir una ruta entre usted y un objetivo
10.2 Interpretar los resultados: una E rápida Ejemplo
10.3 Encontrar el origen del problema
10.4 Encontrar el origen del problema - parte 2
10.5 Interpretar los resultados - Monitoreo a
10.6 Interpretar los resultados - Jugadores
10.7 Interpretar los resultados - Problemas del ISP
10.8 Interpretar los resultados - Mal hardware
10.9 Interpretar los resultados - Saturación del ancho de banda
largo plazo10.10 Voz en offproblemas de IP (VoIP)
10.11 Creación de un caso convincente
Solución dehttps://www.pingplotter.com/export/manual 4/139
Funciones avanzadas
11.1 IPv6 e IPv4
11.2 Sockets TCP sin procesar y WinPcap
11.3 Rastreo desde un servidor remoto
11.4 Los argumentos de línea de comandos
11.5 Opciones del instalador yde MSI
Opciones
12.1 Opciones
12.2 Opciones generales
12.3 Opciones web Server

12.4 Configuración del correo electrónico
12.5 Opciones de visualización
12.6 Opciones del motor
12,7 Auto-Guardar opciones
12.8 Flex almacenamiento
12.9 final Hop Sólo
Menús
13.1 Menú archivo
13.2 Menú Edición
13.3 Espacio de trabajo del menú
Más información
14.1 Soporte
14.2 Compras
14.3 Vínculos relacionados e interesantes
14.4 Acerca del uso compartido y la privacidad

https://www.pingplotter.com / export / manual 5/139 21/9/2018
PingPlotter
Introducción a
1.1 - Bienvenida
Una conexión de red probablemente no es algo en lo que piense sobre una base
regular. Cuando no funciona bien (o deja de funcionar por completo)… bueno, esa
es una historia completamente diferente. En ese punto, es * todo * en lo que
puedes pensar. ¿Lo único peor que su conexión de red no funciona? Tratando de
averiguar por qué no funciona.
Si está leyendo esto, es probable que se haya encontrado (o se esté encontrando

actualmente) con esta situación exacta. O tal vez solo te estás preparando con
anticipación (¡adelante!). Independientemente de su situación de red actual,
PingPlotter puede ayudarlo a llegar al fondo de este tipo de problemas más rápido,
para que pueda encontrar una solución y volver a no tener que pensar en su
conexión.
PingPlotter se creó originalmente en 1998 para solucionar problemas de retrasos

inaceptables en un juego en línea (un problema del que ese ISP en particular no se
responsabilizaba en ese momento). A lo largo de los años, el programa ha crecido y
ha agregado una variedad de características y capacidades. Hoy en día, es una
herramienta de diagnóstico, resolución de problemas y monitoreo de red muy
poderosa, que es utilizada por una variedad de usuarios, desde el “solucionador de
problemas de fin de semana” hasta administradores de red de tiempo completo.
PingPlotter puede ayudarlo con una variedad de problemas relacionados con la

red, y puede ser de gran ayuda para usted si:
Depende de una red o servicio de Internet, que tiene problemas,

como un rendimiento lento, desconexiones aleatorias u otros
problemas similares. .
Usted es un administrador de sistemas, y necesita saber cuándo falla la

conectividad a uno de sus servidores (y quiere alguna evidencia de
dónde / cuándo / por qué cayó).
Un proveedor le dice que no puede ver ningún problema (cuando

claramente usted tiene problemas) y usted debe mostrarle dónde está
realmente el problema.
En general, si es usuario de algo que depende en gran medida de una red o

de Internet, como:
Un navegador web
Servicios VoIP / chat de video
Juegos en línea
Transmisión de audio / video
Un ASP para su negocio (como nómina, contabilidad, recursos humanos,

etc.)
Productos de automatización del hogar
Si está aquí, es muy probable que uno de los puntos anteriores se aplique a usted.
Sin embargo, existen algunos escenarios en los que PingPlotter puede no ser la
herramienta adecuada; si tiene cientos (o miles) de nodos de red con muchos
servicios que necesita monitorear, si necesita una verdadera capacidad SNMP
(aunque PingPlotter puede activar trampas SNMP a través de alertas
(http://www.pingman.com/kb/31)) o si necesita el descubrimiento automático de
nodos de red.
Si alguna vez tiene alguna pregunta o comentario sobre PingPlotter, esta guía, o si
solo desea enviar un correo electrónico a alguien para decir "hola", no dude en
enviarnos un correo electrónico a info@pingplotter.com (mailto:
info@pingplotter.com ). ¡Siempre estamos felices de responder cualquier pregunta
o brindar cualquier consejo que podamos!
1.2 - Descripción general

Una vez que haya descargado e instalado PingPlotter
(downloading_and_installing.html), comenzar a recopilar datos es muy sencillo.
PingPlotter entonces comenzará a generar información de ruta. Si recibe
un mensaje de "Dirección de destino inalcanzable", eche un vistazo aquí
(http://www.pingman.com/kb/8) para ver algunas posibles soluciones.
preocupado por la pérdida de paquetes que se ve en el salto # 4 y # 10 en la
captura de pantalla anterior? Mientras no parezca estar afectando nuestro
destino final (que no está aquí), entonces no hay nada de qué preocuparse.
Consulte este artículo de la base de conocimientos
(http://www.pingman.com/kb/5) para obtener más información.
21/09/2018
PingPlotter https://www.pingplotter.com/export/manual 11/139
21/09/2018
PingPlotter https: // www. pingplotter.com/export/manual 12/139
09/21/2018
PingPlotter https://www.pingplotter.com/export/manual 13/139
** Algunas de las características que se enumeran en este tema sólo están
disponible en PingPlotter Pro y / o PingPlotter Standard. Consulte nuestra
página de comparación de productos
(http://www.pingplotter.com/featurecomp.html) para obtener más detalles **
Operación de
6.1 - Descarga e instalación
Siempre se puede acceder a la última versión de PingPlotter a través de nuestra
página de descargas (http://www.pingplotter.com/download.html). Si es un
usuario con licencia y necesita descargar una versión anterior del programa, estas
versiones se pueden encontrar accediendo a la página de su cuenta
(https://www.pingman.com/account/).
Windows
Una vez descargado e iniciado, el instalador de PingPlotter inicia una instalación
guiada por un asistente que recorre el proceso de instalación. Sugerimos dejar
todas las configuraciones en sus valores predeterminados (si desea instalar
PingPlotter como un servicio de Windows, eche un vistazo aquí
(running_as_a_service.html)).
Al final de la instalación, se le preguntará si desea "Ejecutar PingPlotter ahora". Si

por alguna razón no desea hacerlo en ese momento, desmarque esa casilla de
verificación. De lo contrario, felicitaciones, ahora debería tener un grupo
PingPlotter junto con el resto de sus aplicaciones instaladas (es decir: menú Inicio,
grupo Programas, carpeta PingPlotter) y ya está listo para comenzar.
Si este procedimiento no funciona para usted por algún motivo (si recibe un error
extraño, etc.), consulte nuestro artículo de la base de conocimientos aquí
(http://www.pingman.com/kb/33). Si aún tiene problemas con la descarga, envíe un
correo electrónico a support@pingplotter.com (mailto: support@pingplotter.com)
describiendo el error específico que está recibiendo y / o cualquier síntoma que
esté viendo.
Desinstalación
Para desinstalar PingPlotter, simplemente ubique el directorio de PingPlotter en el

menú de inicio y ejecute "Desinstalar o modificar la instalación". Una vez que se
inicie el asistente de configuración, haga clic en "siguiente" y luego elija la opción
"eliminar". En la siguiente pantalla, se le indicarán opciones para mantener o
eliminar su clave de licencia de PingPlotter; así como cualquier configuración,
directorio y archivo de registro (nota: si está desinstalando a través de Agregar o
quitar programas, estas opciones solo están disponibles a través de la opción
"Cambiar". La opción "Desinstalar" no proporciona estas opciones). Después de
marcar o desmarcar sus casillas preferidas, haga clic en "Eliminar" y luego en
"Finalizar" para completar la desinstalación.
Si no puede encontrar la opción Modificar o Eliminar en el menú de inicio de

PingPlotter o en Agregar o quitar programas, intente instalar la última versión y
luego desinstalar. Esto también podría ayudar a resolver los errores del instalador
que faltan (como "Archivo {7c7a8eba-cb1a-4626-aa2d 8311b84092ab} .msi no
encontrado") durante la desinstalación.
Mac
21/9/2018Descarga de
PingPlotterPingPlotter para Mac en un archivo .zip. Después de descargar y

extraer el archivo, aparecerá un mensaje que le preguntará si desea mover el
programa a lala
carpeta deaplicación (lo que recomendamos hacer). Una vez que el archivo se
extrae en la carpeta de la aplicación (o en cualquier otra ubicación que haya
elegido para conservarlo), se iniciará automáticamente y estará listo desde allí.
Desinstalación La
desinstalación es un proceso bastante sencillo; simplemente mueva la aplicación

desde cualquier lugar donde la guarde (carpeta de la aplicación u otro lugar) y
muévala a la papelera de reciclaje. Sin embargo, el programa almacena sus
archivos de configuración y datos en una ubicación separada. Para encontrar
estos archivos, abra una nueva ventana del Finder, haga clic en la opción "Ir" en el
menú y elija la opción "Ir a la carpeta". Desde allí, ingrese
"~ / Library / Application Support / PingPlotter" (menos las comillas), que lo
dirigirá al directorio donde PingPlotter almacena toda su información (y también
puede mover todo esto a la papelera de reciclaje) .
6.2 - Barra de objetivos n
. ° 1 - Resumen de todos los objetivosresumen: El"Todos los objetivos"

(summary_graphs.html) siempre está disponible en PingPlotter Pro (solo) y
enumera todos los objetivos a los que está rastreando. Se puede acceder
rápidamente a este en "Espacio de trabajo" -> "Resúmenes" -> "Todos los
objetivos".
# 2 - Pestaña de seguimiento de destino *: las ventanas de destino se pueden

abrir para cualquier destino desde una pantalla de resumen haciendo clic
derecho en un destino y eligiendo "Mostrar ventana de destino" o haciendo clic
en la dirección IP de un destino.
# 3 - Nueva pestaña de seguimiento *: una pestaña en blanco lista para una

nueva entrada de destino. Si intenta iniciar un segundo "Nuevo rastreo", el
antiguo "Nuevo rastreo" se reemplaza por uno nuevo.
# 4 - Botón Agregar nueva traza *: Este botón abrirá una ventana "Nueva traza".
# 5 - Campo de entrada de destino: este campo es donde se puede ingresar un
nuevo destino (ya sea por dirección IP o nombre DNS (ipv6_and_ipv4 .html)). Al
hacer clic en el botón desplegable de este campo, aparecerá un panel de historial
que muestra todos los objetivos anteriores a los que se les ha rastreado.
# 6 - Botón de inicio / pausa: este botón puede iniciar un nuevo rastreo (después
de que se haya ingresado un nombre de destino / dirección IP), o pausar un
rastreo existente. Al hacer clic en la opción desplegable de este botón, también
se ofrecerán opciones para "Restablecer y reiniciar" un objetivo (que comienza
una sesión de seguimiento completamente nueva en ese objetivo y borra todos
los datos de seguimiento antiguos), así como una opción para crear un "Nuevo
Ventana de destino ".
# 7 - Configuración de intervalo de seguimiento: esta configuración dicta la

cantidad de tiempo que PingPlotter esperará entre el envío de conjuntos de
muestras. El menú desplegable proporciona varias opciones diferentes, pero los
valores también se pueden escribir aquí manualmente.
# 8 - Configuración de enfoque: este campo dicta la cantidad de datos recientes

que usa PingPlotter para calcular las estadísticas que se muestran en la cuadrícula
de seguimiento. Si se establece en "auto", el tiempo de enfoque se ajustará
automáticamente a lo que se muestra en los gráficos de tiempo (por ejemplo, si un
gráfico de tiempo se establece en 1 hora, PingPlotter mostrará automáticamente
las estadísticas de la última hora). Si se establece en un valor (es decir, 60
segundos), PingPlotter mostrará las muestras más actuales dentro del período de
tiempo establecido (haga doble clic en el gráfico de tiempo
(time_line_graphing.html) para cambiar el enfoque en modo no automático). Si se
establece en "Auto", PingPlotter basará sus estadísticas en lo que se muestre en los
gráficos de tiempo (y las estadísticas se actualizarán si se desplaza hacia adelante
y hacia atrás en el gráfico de tiempo).
# 9 - Menú desplegable de configuración: si está utilizando Pro y tiene más de

una configuración con nombre (named_configurations.html), también tendrá un
selector de "Configuración" aquí. Esto le permite cambiar un objetivo (o gráfico
de resumen) a un conjunto diferente de parámetros.
# 10 - Leyenda de color bueno / advertencia / malo: muestra los umbrales que se

han establecido para los colores en el fondo del gráfico. Los valores aquí se
pueden ajustar yendo a "Editar" -> "Opciones" -> "Pantalla" (para Windows), o
"PingPlotter" -> "Preferencias" -> "Pantalla" (para Mac).
* Las pestañas actualmente solo están disponibles en la versión de Windows de

PingPlotter (sin embargo, si está ejecutando Sierra en Mac, puede hacer uso de la
función de pestañas)
** Algunas de las funciones enumeradas en este tema solo están disponibles

en PingPlotter Pro y / o Estándar PingPlotter. Consulte nuestra página de
comparación de productos
(http://www.pingplotter.com/featurecomp.html) para obtener más
6.3 - Gráfico de
detalles **
seguimiento
En los gráficos es donde realmente brilla PingPlotter. De un vistazo, puede ver
visualmente dónde radica un problema. En realidad, hay tres áreas discretas: la
cuadrícula de datos de seguimiento, el gráfico de seguimiento y el gráfico de línea
de tiempo. Los dos primeros (Trace Grid y Graph) se conocen principalmente
como Trace Graph, ya que se utilizan juntos. Consulte
a la siguiente imagen (anotada con números) que hemos guardado desde
PingPlotter ("Archivo" -> "Guardar imagen" ) y las explicaciones (haciendo
referencia a los números) debajo de los gráficos.
El gráfico superior se llama Trace Graph. Todas las columnas del gráfico de
trazas son redimensionables. El gráfico horizontal inferior se llama Gráfico de
línea de tiempo.
Todos los números del gráfico de trazas utilizan la"Focus

configuración(theinterfacesettingsandrtchanges.html)" para controlar cuántas
muestras se utilizan en los cálculos. De forma predeterminada, está mirando las
muestras recopiladas más recientemente, pero también puede centrarse en las
muestras que no son las más recientes haciendo doble clic en el gráfico de
tiempo. Esto enfocará el gráfico superior en ese período en el que hizo doble clic
(cubrimos este tema con un poco más de detalle a continuación).
1 - El número de saltos que el dispositivo en la ruta es desde su computadora. Si
aparece un icono de campana junto a él, significa que se está monitoreando el
salto para detectar una alerta (las alertas se tratan en la sección de
configuración avanzada de este tutorial (help_alerts.html)). Se pueden
configurar varias alertas para la misma IP, y las alertas no funcionan a menos
que se esté monitoreando alguna IP en su ruta actual. Si un salto tiene un icono
de gráfico junto a él (como el salto n. ° 11), ese salto se está trazando en un
gráfico de línea de tiempo.
https://www.pingplotter.com/export/manual 18/139 21/9/2018
PingPlotter
2: la Recuento columnamuestra cuántos paquetes se han enviado para el
período de enfoque actual.
3 - La dirección IP columna demuestra las direcciones IP de los enrutadores que

informaron para cada salto.
4: esta columna muestra el nombre DNS del dispositivo para ese salto. Un "----------"
en esta columna indica que PingPlotter no pudo resolver un nombre para la
dirección IP de ese dispositivo. Esto no es una falla en PingPlotter, solo significa
que su servidor DNS no tiene un nombre para esa dirección IP (o esa dirección
simplemente no tiene un nombre DNS, punto).
5 - La Promedio columnamuestra el tiempo de respuesta promedio de las

últimas "X" muestras (donde "X" es el "Tiempo de enfoque"). Los tiempos de
espera / paquetes perdidos no se incluyen en este valor.
6 - La Mín columnamuestra el tiempo de respuesta mínimo para el período de enfoque actual.

7 - La Cur columnamuestra el tiempo de muestra individual de la muestra más
reciente incluida en el conjunto. Si un número se muestra como ERR, eso
significa que el paquete se perdió (es decir, se envió un paquete, pero nunca
regresó).
8 - El PL% indica el número de paquetes que se han perdido en el conjunto de

muestras actual. Si solo incluye las últimas 10 muestras, aquí solo se muestra el
número de paquetes perdidos en las últimas 10 muestras. Si desea saber
cuántos tiempos de espera se han producido durante toda la sesión, cambie el
"Tiempo de enfoque" a "0" o "Todos".
9 - La ida y vuelta línea deestá básicamente ahí para facilitar la lectura. Es el

mismo valor que el último servidor de la ruta. Este es el tiempo que tarda un
ping en llegar desde su computadora al dispositivo de destino y viceversa.
10 - El gráfico de línea de tiempo (TG) es una de las funciones más poderosas de

PingPlotter y es excelente para los proyectos de monitoreo a largo plazo que
pueda estar realizando. Analizamos los gráficos de tiempo un poco más en la
sección "Gráficos de línea de tiempo (time_line_graphing.html)".
11 - Al hacer doble clic en cualquier lugar del gráfico de la línea de tiempo,

aparecerá un Área de enfoque, que enfocará el gráfico de datos de
seguimiento (gráfico superior) a ese punto en particular en el tiempo. Esto es
particularmente útil para investigar picos o tiempos de espera.
Herramientas y otras opciones

disponibles para el gráfico de
seguimiento
. Puede mostrar las columnas Mínimo y Máximo haciendo clic con el
botón derecho en el gráfico de seguimiento superior y seleccionándolos
(a través de la opción "Personalizar vista ..." ).
Puede copiar la dirección IP o el nombre DNS de un salto al portapapeles

haciendo clic derecho en ese salto, seleccionando la opción
Portapapeles y luego haciendo clic en lo que desea guardar.

en PingPlotter Pro y / o PingPlotter Standard. Consulte nuestra página de
(http://www.pingplotter.com/featurecomp.html) para obtener más detalles **
6.4 - Gráficos de línea de tiempo

21/09/2018 LosPingPlotter a
problemas de la redmenudo pueden ocurrir cuando no los está observando.

La función de gráfico de línea de tiempo en PingPlotter nos brinda una forma
rápida de ver una representación visual de nuestros datos de seguimiento.
Esto hace que detectar problemas (o problemas potenciales) sea mucho,
mucho más fácil.
De forma predeterminada, PingPlotter rastreará automáticamente el último salto (el

host al que está rastreando
) en un gráfico de línea de tiempo.
En PingPlotter Standard y Pro también puede mostrar un gráfico de línea de tiempo

para cualquiera de los otros saltos en una ruta haciendo doble clic en ese salto o
haciendo clic con el botón derecho y seleccionando "Mostrar este gráfico de línea
de tiempo". También puede desactivar cualquier gráfico mediante estos mismos
mecanismos.
La cantidad de datos que se muestran en el gráfico también se puede cambiar;

simplemente haga clic con el botón derecho en cualquier lugar del gráfico y
seleccione la cantidad de tiempo que desea mostrar (esto afectará a todos los
gráficos de la línea de tiempo y se guarda cuando apaga PingPlotter).
Navegación
Si hay más datos recopilados de los que podemos mostrar en un gráfico de línea de
tiempo (por ejemplo, si tiene 48 horas de datos, pero tiene la escala del gráfico
establecida en "10 minutos"), puede hacer clic (y mantener presionado ) el botón del
mouse en el gráfico y arrástrelo hacia adelante y hacia atrás. Esto le permite
retroceder en la historia y examinar las muestras durante esos momentos.
En Windows, si hace clic en un gráfico y se desplaza hacia abajo, retrocederá en

el gráfico de tiempo; si se desplaza hacia arriba, el gráfico avanzará. Si hace clic
en la rueda de,
desplazamientodesplazarse hacia arriba o hacia abajo alternará entre las
opciones de período de tiempo en el gráfico (por lo que básicamente puede
acercar o alejar con este método). En Mac, con un mouse mágico puede
mantener presionado un clic izquierdo y desplazarse para acercar o alejar el
gráfico de la línea de tiempo.
Comentarios
PingPlotter
Si está utilizando PingPlotter para el monitoreo a largo plazo, a veces puede
encontrarse con una situación en la que su red se vio afectada por algo que saber
sobre (corte de energía, descarga de archivos grandes, esa vez que arrojó su
enrutador por la ventana, etc.). También
puede encontrarse con situaciones que no controla, pero conoce la causa (o puede
especular). Ser capaz de tomar notas sobre estas situaciones y vincularlas a sus
datos puede resultar muy, muy útil.
Para crear una nota, todo lo que necesita hacer es hacer clic derecho en un
gráfico de línea de tiempo (en un punto en el que desea crear una nota) y
seleccionar la opción "Crear comentario". Aparecerá un mensaje pidiéndole que
cree su comentario, y luego PingPlotter dibujará un triángulo rojo en el borde
inferior del gráfico de la línea de tiempo. Si pasa el mouse sobre el triángulo,
puede ver la nota: al
hacer clic con el botón derecho en el triángulo de comentarios, también podrá editarlo o eliminarlo.
Cuando guarde datos como una imagen de PingPlotter, sus comentarios se

adjuntarán a la imagen (junto con las veces que sucedieron). Si está enviando una
imagen a un proveedor de red, esto puede ser especialmente valioso, ya que ayuda
a explicar los eventos en los datos que les está enviando:
El área de enfoque
Cada vez que hace doble clic en un gráfico de línea de tiempo, un Aparecerá
“Focus Area”, que enfoca el gráfico superior a ese punto en el tiempo. Esta área de
enfoque se basa en el valor de "Tiempo de enfoque" (y esto no funcionará si tiene
este valor establecido en "TODOS").
Si usted tiene sus gráficos establecidos para mostrar las 48 horas de datos, y si
encuentra un período de tiempo que parece que podría Para ser interesante,
puede hacer doble clic en el gráfico de la línea de tiempo en ese punto y el gráfico
de seguimiento también se moverá a ese período de tiempo. Luego, puede
cambiar la escala del gráfico de la línea de tiempo, y los gráficos inferiores
permanecerán enfocados en el período que seleccionó. Esto hace que sea fácil de
detectar y ampliar los problemas.
Cuando termine de revisar el historial de su gráfico, puede restablecer todo para

mostrar sus resultados actuales haciendo clic con el botón derecho en un gráfico
de línea de tiempo y seleccionando "Restablecer el enfoque a actual". Esto
devuelve ambos gráficos a, lo adivinó, la hora actual.

en PingPlotter Pro y / o PingPlotter Standard. Consulte nuestra página de
(http://www.pingplotter.com/featurecomp.html) para obtener más
detalles ** 6.5 - Gráficos degráficos
de
resumen La pantalla deresumen en PingPlotter es una lista de los destinos finales o
saltos intermedios de cualquiera de sus destinos . Este resumen le brinda una
manera de comparar múltiples objetivos y también le brinda un resumen fácil de un
vistazo de todas las partes importantes de su red.
El resumen "Todos los objetivos"resumen

ElTodos los objetivos es un resumen especial. Son todos los destinos finales que
está rastreando / monitoreando. Este resumen es mantenido automáticamente
por PingPlotter: cuando agrega un objetivo, aparece, cuando cierra, se elimina.
Puede cambiar el nombre de la pestaña (y cualquier otro resumen) haciendo clic
derecho en su pestaña, pero siempre se mantiene. Si te escondes, estará allí (en el
menú Espacio de trabajo (workspace_menu.html)) cuando estés listo para volver
a hacerlo.
Agregar objetivos a la pantalla de resumen

Si desea agregar manualmente un objetivo (o cualquier salto intermedio) a un
gráfico de resumen personalizado (que cubrimos a continuación),
simplemente haga clic derecho en ese salto en el gráfico de seguimiento y
seleccione "Mostrar (objetivo) en resumen "-> (luego elija un resumen).

PingPlotter
Desde la pantalla de resumen, puede cambiar al gráfico de seguimiento haciendo clic con el botón
derecho en un
host y seleccionando la opción de menú "Mostrar gráfico de seguimiento , "o simplemente haciendo
clic en
la dirección IP del objetivo. Puede ordenar la lista de objetivos haciendo clic en el encabezado de un
gráfico.
Al hacer clic de nuevo, se invierte el orden de clasificación.
Creación de pantallas de resumen personalizadas

Puede crear varias pantallas de resumen personalizadas, lo que facilita la agrupación de determinados
objetivos. Para crear una nueva pantalla de resumen, simplemente haga clic derecho en un objetivo (o
puede seleccionar varios objetivos manteniendo presionada la tecla "CTRL" (en Windows)
o la tecla Comando (en Mac), y haciendo clic en ellos, y luego haciendo clic derecho ) y en
"Mostrar en la pantalla de resumen", seleccione "(Nuevo resumen)" y se abrirá una nueva pestaña
con su (s) objetivo (s).
Puede eliminar objetivos de una pantalla de resumen haciendo clic con el botón derecho y seleccionando
"eliminar del resumen".
Las pantallas de resumen que se han ocultado siempre se pueden volver a abrir yendo a la
opción de menú "Espacio de trabajo" -> "Resúmenes", que mostrará una lista de lasactivas
pantallas de resumenque estén configuradas. Si desea mantener automáticamente una pantalla de
resumen
según el rendimiento, puede usar una alerta para agregar o eliminar de un resumen
(add_remove-from-summary.html).
Períodos de tiempo en la pantalla de resumen (o

"Focus")
Una pantalla de resumen es una colección de objetivos, posiblemente con diferentes intervalos de
seguimiento,
rangos de latencia o características de problemas / rendimiento. El "Enfoque" siempre se
aplica el mismo período de tiempo a todos los objetivos, incluso si el intervalo de seguimiento es
diferente.
Algunos objetivos pueden estar en pausa mientras otros se están ejecutando; todos se comparan al
mismo tiempo, por lo que sus estadísticas pueden estar en blanco para algunos objetivos y su"Recuento"
columnapuede tener números diferentes para cada objetivo.
Al igual que en la ventana Trace, el modo de enfoque "Automático" es bastante impresionante: puede
desplazarse
por el tiempo y obtener un resumen rápido de lo que está viendo.
Uso de la barra de destino

21/9/2018 PingPlottertheinterfacesettingsandrtchanges.html
() en una pantalla de resumen.

Una excelente manera de ingresar nuevos objetivos es hacerlo desde una pantalla
de resumen. Al hacer esto, se utilizan la configuración y el intervalo de la barra de
destino de resumen, y ese destino se agrega automáticamente a esa pantalla de
resumen. Cuando hace esto, no se abre una pestaña de destino para cada destino
que está agregando, pero los datos se recopilan. Simplemente haga clic en el
enlace azul de la dirección IP para abrir el gráfico de seguimiento completo.
Otra cosa interesante de la barra de objetivos es que puede cambiar fácilmente el

intervalo o la configuración; simplemente seleccione un objetivo (o 10 mediante
selección múltiple) y luego cambie la configuración.
En una nota relacionada, los objetivos multiseleccionados también tienen una

variedad de opciones disponibles en el menú del botón derecho. Puedes cerrar,
empezar, parar. etc todos los objetivos enumerados; el menú del botón derecho le
mostrará el efecto que tendrá.
** La función de este tema es exclusiva de PingPlotter Pro. Consulte nuestra página deproductos
comparación de(http://www.pingplotter.com/featurecomp.html) para
obtener más detalles **
6.6 - Espacios deespacios de

trabajo Lostrabajo capturan información sobre su configuración; incluidos los
objetivos que se están supervisando, la configuración que utiliza cada objetivo, los
intervalos de seguimiento, los tiempos de enfoque y los diseños de pantalla y
resumen.
PingPlotter v5 siempre tiene un espacio de trabajo que se ejecuta de forma

predeterminada. Si se necesita un espacio de trabajo separado (por ejemplo, si
quisiéramos configurar un espacio de trabajo de "casa" y "oficina"), se puede crear
uno yendo a "Espacio de trabajo" -> "Iniciar nuevo espacio de trabajo".
A los espacios de trabajo se les asigna automáticamente un nombre genérico

("Creado" seguido de una marca de fecha / hora de cuando se creó), pero se puede
cambiar el nombre eligiendo la opción "Cambiar nombre del espacio de trabajo" en
el menú Espacio de trabajo. Toda la información del área de trabajo se guarda en
la base de datos PingPlotter en una máquina, por lo que cualquier espacio de
trabajo se puede abrir a través de la opción "Abrir existente":
Mayor Los espacios de trabajo de las versiones v4 de PingPlotter se pueden importar mediante
la"Importar
opciónespacio de trabajo" *. Al buscar el archivo del espacio de trabajo, la opción
"Archivo del espacio de trabajo de PingPlotter 4" debe seleccionarse del menú desplegable en la
esquina inferior derecha: Los
espacios de trabajo también se pueden exportar si es necesario. Es importante tener en cuenta que
en
PingPlotter v5 estos archivos se guardan como archivos .ppws, por lo que cualquier espacio de trabajo
guardado desde
v5 no será compatible con versiones anteriores de PingPlotter.
* La importación / exportación de espacios de trabajo actualmente solo está disponible en las

versionesWindows
dede PingPlotter.
Ejecución como servicio y espacios de trabajo

Cuando se ejecuta como servicio, existen algunas complicaciones con los espacios de trabajo si se
encuentra
en un entorno multiusuario. Al iniciarse, el servicio se inicia automáticamente y cualquier
usuario de esa máquina puede cerrar objetivos, cambiar de espacio de trabajo o agregar nuevos
objetivos.
La lista de objetivos en ejecución se almacena por separado del "diseño" de un espacio de trabajo.
La lista de objetivos está estrechamente vinculada a los datos que recopilamos (auto-save-data.html)
para esos objetivos, y siempre conquistará su espacio de trabajo de diseño. Es posible que al
iniciar PingPlotter se conecte a una lista de objetivos diferente a la última vez; en este
caso, PingPlotter hará todo lo posible para darle algo significativo (como un buenTodos los
resumen deobjetivos (summary_graphs.html)) y sus datos recopilados estar allí,
leer para revisar y analizar.
** La función de este tema es exclusiva de PingPlotter Pro. Consulte nuestra página deproductos
comparación de(http://www.pingplotter.com/featurecomp.html) paramás
obtenerdetalles **
6.7 - Interfaz web

** Nota: la información de esta sección es específica para la versión de Windows de
PingPlotter.
PingPlotter
PingPlotter Pro tiene una interfaz web incorporada, que le permite ver datos y
acceder a bastantes opciones de PingPlotter Pro desde un navegador web - sin tener
que ser local en la máquina que está recopilando datos.
Habilitación de la interfaz web incorporada

Recomendamos utilizar PingPlotter como un servicio de Windows si va a
utilizar la interfaz web. Esto asegurará que siempre se esté ejecutando y hará
que los permisos de seguridad sean un poco más fáciles de configurar.
Para habilitar la interfaz web, vaya a "Editar" -> "Opciones" -> "Servidor web" y encienda el
servidor web (sí, es así de fácil).
Recomendamos dejar el puerto en 7464 (aunque puede cambiarlo), y si

está realizando algunas pruebas locales, es mejor desactivar la marca de verificación "Usar seguridad"
(una vez que finalice la prueba, puede volver y vuelva a habilitar esta opción). Aplique
sus cambios y cierre el diálogo de opciones.
Queremos asegurarnos de que la interfaz web se esté ejecutando correctamente, por lo que en
PingPlotter
Pro, asegúrese de rastrear al menos un objetivo y luego pasar a la siguiente
sección.
Acceso a la interfaz web

Para acceder a la interfaz web desde su máquina local, inicie suweb favorito
navegador(si se pregunta sobre los requisitos del navegador, lo cubrimos más adelante
en esta página) e ingrese la siguiente dirección (o haga clic en ella, si 're reading this on
your computer):
http://localhost:7464 (http://localhost:7464)
This should open your browser to the PingPlotter Pro web interface - which will list
all of your targets. You can click on a target to open a trace graph for it, stop tracing
(and close down a target), add a new target, change some basic settings, and do
some basic examination of data.
Doing Basic analysis

You can do quite a few things from the web interface - but *some* actions do
require the local PingPlotter Pro client. Wondering what's possible to do with the
web interface? Well, we've compiled a list:
Add/remove targets
Create a custom summary screen (and add/remove targets from it)

Add/remove columns, customize widths.
Examine a target's data by:
Changing the focus period
Changing the period of time on the timeline graph
Turn on/off time graphs
Download sample data for more analysis within a local instance

of PingPlotter
Do whois lookups through www.whois.sc (www.whois.sc)
Sharing targets between the Windows GUI

and the web interface
Good news here - everything "just works". If you're running as a service, booting your
machine will start the web interface and load a workspace (based on your
preferences). You can use the main PingPlotter GUI to create alerts, add/remove
targets, create summary screens. Your changes will be reflected on the web
interface (which is a big improvement from V4 of PingPlotter). This means
someone accessing the web interface can close targets created on the GUI and
create targets that show up on the GUI.
Named configurations need to be created with the GUI, but then will show up on the
web automatically.
Browser Requirements
PingPlotter 5's web interface requires that Javascript be enabled. We recommend
using at least IE11, Firefox 10+, or any other browser that is less than a couple of
years old.
Using IIS as a web server

PingPlotter 4's web interface used Classic ASP with VBScript, which is now pretty
old and doesn't make sense to duplicate. The good thing about this tech is that it
worked OK with IIS as a backend web server.
PingPlotter 5 uses a completely different architecture - one that does not work with
VBScript or Classic ASP. Currently, it also doesn't work with IIS. If you need IIS (for
security, stability, scalability reasons), you might want to keep using PingPlotter V4.
If you're using IIS so you can use https, that is coming to PingPlotter 5 (and should
be possible today, although not documented or tested). Support for other web
servers (IIS, Apache on Mac, and others on other platforms) is on the roadmap but
is not immediately possible. Please contact us and let us know how you're using
PingPlotter web and we'll help come up with best solution.
Advanced configurations
Over the years, we know our users have customized the web interface to do things
we didn't really design PingPlotter to do - and we've helped with some of this.
PingPlotter 5 changes what's possible here. If you're using V4 with modifications to
the web interface to allow read-only views, REST calls to add targets, surfacing
custom data and similar, please contact us for help. Many things are possible, but
it's different than V4.
**The feature in this topic is exclusive to PingPlotter Pro. See our product
comparison (http://www.pingplotter.com/featurecomp.html) page for more
details**
Common Tasks
7.1 - Variable Substitution
A number of the alert parameters allow you to insert a variable which will be
substituted for a value when the alert happens. Here is a list.
{{Host}} Host Name & IP Address (no space,
comma terminated)
{{Host.HostID}} Host Identification Number
{{Host.IPAddress}} Host IP Address

{{Host.HostName}} Hostname in DNS
{{Host.AliasName}} Custom hostname alias
{{Host.PreferredName}} First non empty value for: alias, DNS

hostname, IPaddress
{{Host.FullDisplayName}} Preferred name followed by IP

address in parenthesis
{{AlertName}} Name of Alert that fired
{{DestinationHost}} Destination's Host Name & IP Address (no

space, comma terminated)
{{DestinationHost.HostID}} Destination's Host Identification Number
{{DestinationHost.IPAddress}} Destination's host IP Address
{{DestinationHost.HostName}} Destination's hostname in DNS
{{DestinationHost.AliasName}} Destination's custom hostname alias
{{DestinationHost.PreferredName}} Destination's first non empty value for: alias,

DNShostname, IP address
9/21/2018
{{DestinationHost.FullDisplayName}} PingPlotter
Destination's preferred name followed by
IP address in parenthesis
Email Specific Variables
{{#attach_timegraph '{of_last: "60 Timeline image for specified time period

seconds", width: 700, height: 200}' }} drawn tospecified width and height
{{#attach_tracegraph '{of_last: "60 Trace Grid and Latency Graph image for
seconds", width: 700, height: 200}' }} specified time period drawn to specified width
and height
{{#attach_image '{of_last: "60 seconds", Screenshot image of for specified time

width: 700, height: 200}' }} period drawn to specified width and height
(includes Timeline, Trace Grid, Latency
Graph)
{{#attach_data '{of_last: "60 seconds"}' }} Export in PP2 format of data of for specified
time period limited to the specified number of
samples
7.2 - Auto-Saving of Data
PingPlotter v5 saves data automatically. In V4, it didn't save automatically, and
sometimes important data wasn't available when you needed it (unless you did
some configuration that didn't always think the way you do). This is something that
shouldn't happen to you in V5. In PingPlotter 5, it should "just work", saving what
you want, discarding what you don't (if you show it what kind of stuff you don't
want).
PingPlotter 5 writes all data in real-time to its local data store. This helps make sure
that none of your data is lost at any point (for instance - if there is an unexpected
restart, a power failure, or any other event that would put data data at risk).
Long-term sessions (a session is a set of collected data from a trace to a target)

are saved continuously, and when you scroll back in history, the data is retrieved
from disk. Closing and restarting will resume those sessions. Short term sessions
are saved continuously, but if you don't collect data long enough, they are marked
for deletion when closed.
When a session is marked for deletion, it will be fully deleted after you close and
reopen PingPlotter five times. If you closed a session you really wanted to continue,
you can reopen that session within 5 stop/restarts and continue. This behavior is a
direct result of feedback from our users (and us) that prompting to save on close
was frustrating.
Configuring the definition of "short term"
sessions
The auto save settings can be configured in PingPlotter by going to either "Edit" ->
"Options" -> "Auto-Save" (on Windows) or "PingPlotter" -> "Preferences" -> "Auto
save" (on Mac).
There are a few different options for how to recognize a session as one you want to
keep around, or one you want to throw away when done.
"Always" - this will keep every target's data in PingPlotter's datastore. If

you start tracing a target and stop after 3 samples, that "session" will get
marked to keep.
"After:" - this setting will only keep sessions that have met or exceeded the
timeframe that is entered. Use "5 minutes", or "1 hour" or similar.
"Only when selected" - this will result in PingPlotter auto-saving data, but
marking it to discard when you close. This is a great option if you have a
handful of long-term targets that you always want to collect from, but you
want to occasionally mix in some targets that you don't want to stick
around.
Keeping an individual session

If you're collecting data from a target and you decide you want to keep it (and you're
in a mode where it's not yet marked to keep), you can switch to "Keep" mode (or
discard mode) manually at any time. To do this, open a trace window (if it's not
already open, use the "All Targets" summary to find it, then open from there), and
right click on the target tab. Here we have options to "Discard on close," or "Keep
(auto-save)."
The tab's "close" icon will show an "X" to indicate that this data will be discarded on
close, and a checkmark to show that it will be kept.
Finding a session
Once you've collected data but you've closed it, how do you reopen it (or delete it, or
export it, or continue tracing)?
The previous trace sessions can be found in PingPlotter by going to "File" ->
"Manage Sessions." From the session browser, we have the options to reopen or
delete a previous session, as well as the option to export a session (which will save
off a .pp2 file).
There are four different persistence types in the session browser:
Active - any trace sessions that are actively collecting data
Pause - any trace sessions that are open in PingPlotter now, but are
paused
Archived - any inactive trace sessions that have been saved and are
closed
Will Delete - any inactive trace sessions that haven't been set to save.
These will eventually be deleted.
All of the data in PingPlotter is saved to a file titled "sessions.ppdata" in one of two
locations. If we're running PingPlotter as a Windows service the file's default
location is in the C:\ProgramData\PingPlotter 5\ folder. If we're running the program
as an application, then the file's default location is in our user application data folder
C:\Users\**username**\AppData\Roaming where **username** is the username of
the currently logged in user.
There is an option in the Auto-Save to change the default location of the

sessions.ppdata file. If we specify a different location to store the file, we'll want to
make sure to close and relaunch the program to get the changes to take effect. If
we're running PingPlotter as a Windows service, then we'd need to restart the
service (or restart the machine) to store the changes.
Long term monitoring considerations

Now we know that data is being saved automatically, and you can open it, export
it, and delete it from the session browser. Is there anything else to worry about?
Hopefully not!
You might be worried about configuring how much data to hold in memory (this
was a common problem in PingPlotter 4 as more targets were added). One of the
advantages of saving data automatically and real-time is that we can count on it
being there - and we don't need it in memory. PingPlotter automatically keeps a
small amount of collected data in memory - enough for alerts to work, and your
graphs to have accurate statistics. The rest it clears from memory and leaves on
disk. If you scroll back in time, the data will automatically be pulled from disk for
display and analysis. When you're done using data, it will be dropped from memory
automatically.
There are a few things you can do to optimize memory and CPU use if you're tracing
to a lot of targets (we'd call 250 "a lot", although that number is going up as we
optimize more).
If you're tracing a long time to a lot of targets, you might:
Hide target tabs for any targets you're not actively looking at. This
minimizes statistics calculations and memory use.
If you have a lot of targets with a lot of data used, don't scroll back a year
with 200 targets on the all summaries tab. This will feel pretty slow as all
200 targets need to load from disk. When you need this, scroll back on a
single target, or create a summary with just the ones you're interested in.
We are continuing to improve this experience as PingPlotter gains
capabilities.
**Some of the features listed in this topic are only available in PingPlotter Pro
and/or PingPlotter Standard. See our product comparison
(http://www.pingplotter.com/featurecomp.html) page for more details**
7.3 - Running as a service

Note: This documentation covers PingPlotter v5 and higher only. If you're using an
older version, see the documentation that came with that version or upgrade to the
latest version.
PingPlotter v5 can be installed as a service - which allows the program to start

running as soon as a machine is booted up, and continue running (even if a user
logs out). This is a great option if we have a few targets that need to be monitored
continuously, without interruption.
For Windows
This option can be selected on installation (or if you've already installed - you can
run the installer again and choose the option to "Modify"):
Once the installation is finished, the PingPlotter service will automatically start
running. To access the service instance, we just need to launch PingPlotter, which
will automatically connect to the service instance. If a new trace tab is opened, in
the lower right hand corner of the program we'll see a status bar reading "Engine:
local service" - letting us know that we're accessing the service instance of
PingPlotter. If running as an application, this status bar will show "Engine: built-in."
For Mac
The option to install PingPlotter for Mac as a service can be found after the
application has been installed and launched (via the "PingPlotter" -> "Background
Mode" -> "Install Service" option):
Once the option to install the service is selected, PingPlotter will complete the
installation and restart itself. Once it's back up and running, the service status can
be viewed (along with options to restart or reinstall the service) via the same menu
option:
Benefits and Disadvantages

Running as a service in PingPlotter 5 is mostly upside. Good things:
Data collection happens in the background, starting at boot. Logging out
doesn't stop tracing.
Some actions with security implications don't need to be configured - web

server, Raw socket ICMP packet types being great examples.
Super-easy, everything just works.
Disadvantages:
Not many, but the security implications have a negative, too. Some
alerts, like "launch an executable", could be used for evil when running as
a service.
Communication uses TCP port 9636, with no option to change (currently).
7.4 - Handling Multiple Targets

PingPlotter Standard can trace up to 2 targets simultaneously in the same instance.
PingPlotter Pro can be used to trace to multiple different targets within the same
instance (and each target's configuration can be independently managed, too!).
There's no “hard limit” on the amount of targets you can add in PingPlotter Pro - but
we've successfully tested up to 250 here at Pingman HQ.
Adding new targets

There are a few ways to add new targets to PingPlotter. If you've just opened up the
program for the first time, odds are you're on a “(new trace)” tab - and the “Target
Name” field is empty (with a blinking cursor in it):
All you need to do is (if you haven't guessed it by now) enter your target's DNS name
or IP address in the empty field, and hit the big green “Start” button on the left hand
side (the “enter” key on your keyboard works here as well).
Wondering how to get another “(new trace)” window open? You can use the "File" ->
"New Target" option, or, in the Windows version of PingPlotter Pro, just click on the
“+” symbol in the upper left hand corner of the program.
If you're on a summary screen in PingPlotter, you can quickly add targets by

entering them in the “Target name” field, and pressing the start button (or the enter
key on your keyboard). Targets added via this method will automatically start
tracing and are added to your list of all targets (and if you're on a custom summary
screen, they'll be added to that summary as well - we cover this in more detail in the
summary graphs section). A tab *won't* be opened if you're using this method - but
it's a good way to quickly add targets and start tracing to them.
Loading a list of targets

If you've got a list of IP addresses, DNS names, or both, you can “bulk add” them
into PingPlotter Pro as well. You'll want to make sure your list is formatted correctly
to accomplish this. In a text editor (notepad works just fine here) create a list of
your addresses - one target per line. Once you've got everything added in, save the
file with a “*.lst” extension.
Once you've got your list saved, in PingPlotter go to "File” -> "Load Target List File,"
navigate to your list file and open it - and PingPlotter will load up the targets from
the list.
Voila! PingPlotter will start to load your list of targets, one at a time - exactly as
though each target was entered into the “New Target” field. Any invalid targets will
prompt an error - which will prompt *after* PingPlotter gets through your entire list.
Selecting Multiple Targets

You can select multiple targets and apply changes to them (pause, change the
trace interval, use a different configuration, or add them to a summary screen). This
is a pretty easy process, too. Hold down either the “CTRL” (for Windows) or the
Command (for Mac) key on your keyboard, and click on a few different targets. If
the targets you're needing to select are in order, you can click one, hold down the
shift key, and click on the last one in the list to get the whole group.
Once you've got multiple targets selected, any changes made in the target bar
(theinterfacesettingsandrtchanges.html) will be automatically applied to the
selected targets. There are also a few options (pause, resume) available via the
right click menu.
Docking, Floating, etc

Note: the information in this section is specific to the Windows version of the
program
By default, each target in PingPlotter Pro is shown in the “All targets” summary
screen (and doesn't have it's own tab unless you open one for it). This works, but
may not be exactly what you're after. Maybe you want a few targets side by side. Or
maybe you have 8 monitors and want 64 targets up filling your high def “war room
screen” (and if this is the case… we salute you). There is definitely a way to achieve
this!
Once you open a target (or summary) into a tab, that target is living in its own
“dock” control. If you grab the tab and drag it away from PingPlotter, you can
position it somewhere within the PingPlotter widow - or drag it out into its own
“stand-alone” display.
7.5 - Named Configurations
So, we know that PingPlotter Pro allows us to trace to multiple targets in the same
instance. What if, however, we want to use different settings on different targets?
For instance - for one target we want to use TCP packets, but want to use ICMP
packets on another. Or maybe you want to trace a few of your targets from a remote
agent location. PingPlotter Pro can do this through the use of named
configurations.
We can access (as well as create and manipulate) our named configurations in
PingPlotter by going to the “Options” menu (“Edit” -> “Options” on Windows -
"PingPlotter" -> "Preferences" on Mac). When you first install PingPlotter you'll have
one named configuration (appropriately named “Default Settings”). Under the
configuration name we see a number of other “configuration specific” areas (such
as “Display” and “Engine,”). The values that we configure in these areas are all a part
of this specific named configuration. At any time, we can edit the name, or make
chances to any of the values.
To create a new named configuration,

all we need to do is right-click on any
existing configuration, and then select
“New Configuration.” If you've got a
configuration already set up, and need
to set up another that's similar (with
minor tweaks), you can right click on
that configuration and select the “Copy
Configuration” option. Any changes that
you make to a specific configuration
are *not* carried over to any other
named configurations.
Once we've created a new

configuration, it's always a good practice to rename it (and give it a good,
meaningful name). Some example configuration names could be:
TCP Port 80
Auto-Save every 30 minutes
VoIP
Remote via our website

There's also an option to enter a description - which can prove helpful (in case you
come back to a configuration and wonder why it was made, and what it was for).
Once you've got everything set up to your liking, and close down the “Options”
menu, you'll notice a drop-down box in the target bar labeled “Settings.” This field
lists all of the named configurations we have set up.
Changing this drop-down will change the currently running target to use that named
configuration. You can change multiple targets to use a specific configuration by
selecting them on the summary screen, and changing the settings field (the
changes will take effect immediately once selected).
**The feature in this topic is exclusive to PingPlotter Pro. See our product
comparison (http://www.pingplotter.com/featurecomp.html) page for more
details**
7.6 - Reporting
PingPlotter doesn't have any *printing* options (who needs paper anyways?), but it
does have a variety of options available to help output data (which will let you
manipulate it in your favorite software package from there).
There are several methods here:
The graphs
A PingPlotter image (the combination of graphs you see on a target screen) should
be your go-to first report. These images has been used by many, many thousands of
people to communicate their problems to their provider.
If the image you see doesn't seem compelling, or doesn't capture the right picture,
you may need to adjust your view. You can drag the time graph back, and focus is
on a period that shows the problem. Depending on the problem, you might want to
widen your view a bit to show periods of OK along with the periods of problem.
Maybe 12 hours if your problem period is 6 hours, or 2 hours if it's 45 minutes.
Right-click on the time graph to pick the appropriate time, then drag back and forth.
Once you have the time graph focused on the period you want, turn on the
appropriate hop graphs. Hops that have latency or packet loss that isn't represented
in the final destination (a topic we cover in more detail here
(https://www.pingman.com/kb/24)) shouldn't be highlighted, while ones near the
origin should be.
Once you've got that view, you can get the upper statistics to show the part you find
important. You can leave it at "auto", which will have the upper and lower graph
show the same time frame. Or you can switch the upper graph to a time period less
than the lower graphs. If your lower graph is focused on 12 hours, you can set the
upper one to 6 hours, and then double-click on the time graph to move the focus
period. This will let you pick the statistics that show your problem and will also
show the lead-in and exit to the problem.
Now span a picture via Edit -> Copy as image or via File -> Save as Image
This concept is more succinctly covered in our video tutorial

(http://link.pingman.com/stqv9h).
There are ways to export, too, but the analysis tools coupled with the image
creation tool really create a powerful case.
There are a few ways get a picture of your PingPlotter graph(s). The quick way is to
select the “Edit” -> “Copy as image option” (which will copy the graph you're viewing
to your clipboard). The column and graph sizing will match up exactly to what you
see on your screen - so make sure everything you want to show is explained.
Another method is the “File” -> “Save Image...” option.
Statistical text export (inspired by

command line traceroute)
In PingPlotter, you can choose the “Edit” -> “Copy as Text” option to copy the raw
data to your clipboard. This is copied in a format that's similar to *most* text-based
trace route programs. It's important to note: the “Focus” option on the main screen
is used to decide how big of a period to include in this.
Comma delimited text file

This option is built to import into a program like Microsoft Excel - so you can
manipulate the numbers and create output in different formats. To export a comma
delimited text file, use the “File” -> “Export to Text File” option. From there, you'll be
able to specify the file you want to export (and a couple of other options). You can
either export all samples in memory, or the range as specified on the main screen.
The “Include sample times in export file” option will specify whether or not to
include the time each sample was taken at. If you don't have this turned on, all of
the samples will be output, but you won't get corresponding times. Enable this
option to include the times.
We discuss more reporting options in our knowledge base
(http://www.pingman.com/kb/64).
7.7 - Exporting data for further

analysis
If you're looking to export data from PingPlotter, this can done via the "File" ->
"Export to text file..." menu option. This option allows you to take all of the data
currently in memory in PingPlotter and save it to a text file which can then be loaded
into Excel (or a similar tool.
We're going to briefly discuss the options here. If you want more information and an
example Microsoft Excel spreadsheet, check our knowledge base
(http://www.pingman.com/kb) (in particular, this topic
(http://www.pingman.com/kb/18) and this topic (http://www.pingman.com/kb/4)).
Include Sample Times in export file
If left unchecked, the times for each trace don't get saved - only the
data. Samples to Export
Select All Samples if you want to export your whole trace to text. Select Current
Sample Set if all you want to save is the currently displayed sample set shown on
the Time Line graph. The current sample set is the setting you'd use if you're
wanting to email trace data to an ISP, etc. - though just saving a graph would be a
better option.
Export Format
9/21/2018 PingPlott er
PingPlotter gives you two different export formats to save your data in. Both are
shown below (Note: if you're using Excel, the second "1 column per hop" usually
works best).
Examples:
One row per hop, one column per sample
,Sample Times,,9/11/2014 11:13:29 PM,9/11/2014 11:13:30 PM,

9/11/2014 11:13:31 PM,9/11/2014 11:13:32 PM,9/11/2014 11:13:33 PM,
9/11/2014 11:13:34 PM,9/11/2014 11:13:35 PM
1,,,N/A,N/A,N/A,N/A,N/A,N/A,N/A
2,loop1.bois-dsl-gw1.bois.uswest.net,216.161.136.254,10,10,10,10,10,20,10
3,100.fa2-0.bois-agw1.bois.uswest.net,207.108.229.29,30,20,10,10,10,10,10
4, -------------- ,207.108.224.247,20,10,20,10,20,20,10
( .... middle data snipped for brevity .... )
16,192.ATM7-0.GW5.SJC1.ALTER.NET,152.63.54.21,60,51,50,50,50,50,50
17,digexoc12-gw.customer.alter.net,157.130.214.154,50,50,50,50,50,50,50
18,gsr-01-p2-0-a00a02.af.sjc5.digex.com,164.109.130.26,50,50,50,51,50,50,50
19,lc1.com,164.109.154.154,50,50,50,51,50,50,50
One column per hop, one row per sample
Host Information
1,,
2,loop1.bois-dsl-gw1.bois.uswest.net,216.161.136.254
3,100.fa2-0.bois-agw1.bois.uswest.net,207.108.229.29
4, -------------- ,207.108.224.247
( ... middle hosts snipped for bre vity ... )
16,192.ATM7-0.GW5.SJC1.ALTER.NET,152.63.54.21
17,digexoc12-gw.customer.alter.net,157.130.214.154
18,gsr-01-p2-0-a00a02.af.sjc5.digex.com,164.109.130.26
19,lc1.com,164.109.154.154
Sample Information
"9/11/2014 11:13:29 PM",N/A,10,30,20,30 .. snipped .. 60,50,50,50

"9/11/2014 11:13:30 PM",N/A,10,20,10,30 .. snipped .. 51,50,50,50
"9/11/2014 11:13:31 PM",N/A,10,10,20,30 .. snipped .. 50,50,50,50
"9/11/2014 11:13:32 PM",N/A,10,10,10,30 .. snipped .. 50,50,51,51
"9/11/2014 11:13:33 PM",N/A,10,10,20,30 .. snipped .. 50,50,50,50
"9/11/2014 11:13:34 PM",N/A,20,10,20,30 .. snipped .. 50,50,50,50
"9/11/2014 11:13:35 PM",N/A,10,10,10,30 .. snipped .. 50,50,50,50
7.8 - Route Changes

In PingPlotter v5, route changes can be viewed through the use of the program's
dynamic focus period - and any route changes that may be present can be viewed
by navigating through the time graph for a target.
To get started, set the "Focus" field to "Auto":
As the time graph is moved forward/backward in time, the upper trace graph will
automatically be updated to reflect the routes that were in use during that time
period.
There are a few tell-tale signs to keep any eye out for when trying to spot route
changes. The first (and most obvious) would be any length changes in the route (if
it shrinks or expands by a few hops) as you scroll. Another great way to spot route
changes is to keep an eye on the "Count" column in the upper graph. If one (or
more) hops is displaying a count that's off from most of the other hops, it's a good
indicator that specific hop was recently added (or re-added) to the route:
You can drill down even further by double clicking in a time graph to bring up a
focus area (time_line_graphing.html) to see the route that was in use for a more
specific time period.
7.9 - Dynamic DNS Tracking

Dynamic DNS is a popular way of running servers without a static IP address,
and PingPlotter v5.2.9 introduces a feature that allows for tracking dynamic DNS
changes (though, it won't initiate them).
DNS records for a hostname may often contain multiple IP address entries
(especially for those supporting both IPv4 and IPv6). The list that is returned is
generally in the order that the website wants a computer to try first. PingPlotter
uses the first returned IP address to determine what to start tracing to - then its
DNS watcher monitors to see if that IP is ever "dropped" off the list (as in, the
website saying it's not a valid IP for the domain anymore). When an IP is dropped
off, then PingPlotter registers it as a change. This round robin approach is
implemented to avoid excessive IP/route changes for bigger services that
constantly change for load balancing and other reasons. For home users of
Dynamic DNS, this won't have much impact - as it's typically just one entry that gets
changed.
The option to track Dynamic DNS is enabled on any new trace sessions by default.
The option can be turned on or off on Windows versions of the program by going to
"Edit" -> "Options" -> "General," or on Mac versions by going to "PingPlotter" ->
"Preferences" -> "General."
There's also an option to enable/disable tracking on a per target basis by accessing

the session manager ("File"-> "Manage Sessions"):
IP change checks are made every five minutes (PingPlotter does not use the DNS
entry TTL field in any way), every time the sessions is started/toggled, or when the
setting is enabled. When an IP change occurs, a comment is made on the timeline
for that target:
7.10 - Sharing PingPlotter data

with others
PingPlotter 5's "Share" feature provides a quick option to distribute your trace data
to whoever you need, and it's easy to use!
You'll want to get your data displayed in PingPlotter in a way that you'd like others to
see it. Make sure you're showing an appropriate timeframe on your graphs, and
open up any time graphs for intermediate hops that may be useful (having graphs
open for intermediate hops can be very helpful for others trying to help troubleshoot
issues!), and then go to "File" -> "Share to PingPlotter.com":
Once the "Share to pingplotter.com" option is selected, a screen shot is taken of
your current view in PingPlotter, and uploaded along with up to 24 hours worth of
trace data for that session to a private page on PingPlotter.com with an individual
link that can easily be shared with others:
From this page, there are options available to post to the link to social media
(Facebook/Twitter/Google +/Reddit), or share it via email. Other users will be able
to not only view the screenshot, but also download a .pp2 file (to open in their own
instance of PingPlotter Standard/PingPlotter Pro*) for that time frame as well:
If you've shared data multiple times, these pages can easily be referenced by going
back to the "File" -> "Share" menu - which will provide a breakdown of each, along
with information on when the information was shared:
Individual shares can be removed by hovering over them, and clicking on the "X"
that appears to the right side (or the "Clear List" option can be used to remove
everything at once). Shared pages are currently hosted as long as they are viewed
regularly online, or a minimum of 30 days.
* PingPlotter Free is limited to opening .pp2 files created on the machine that it is
running on, but upgrades to Standard or Pro are easy (/products/purchase/trade
license.html).
Alerts
8.1 - Creating / Configuring Alerts
What is an alert?
Alerts basically monitor the conditions of a specific IP address, and then do
something when those conditions exceed a specific range. The things you can do
with an alert are:
Play a sound or .WAV file (event_play_a_sound.html)
Send an email (event_send_email.html)
Log to a text file (event_log_to_file.html)
Change the tray icon / show a message (event_tray_icon_change.html)
Execute a web REST call (web-rest-call.html)
Add/Remove a target from a summary screen (add_remove-from

summary.html)
For example, let's say you need to know when a destination you're monitoring stops
responding. You can attach an alert within PingPlotter to that IP address so that you
receive an email alert if the last 10 of 10 sample requests are lost.
Another possible alert condition to check for is if the average for the last 10
samples is > 500 (or any other number). You can send an email alert, maybe play a
.WAV file (if you're usually within hearing distance) or both. Also, if you're trying to
show your ISP there's a problem, you might log the data to a file so you have
records of every time it happened over a time period.
Setting up an alert.
PingPlotter v5 introduces a new guided alert setup process. To start setting up a
new alert, either select a target from a summary screen, or open a trace window for
a target, and click on the "Alerts" tab - which can be found on the right hand side of
the application.
Once the alert sidebar is opened, we land on a screen that will tell us any alert info
that may be present for the target we've chosen. From here, we're also be able to
create a new alert that will be stored in our alert library - so that we can use it on
any of our targets.
Setting up a New Alert
For this example, we'll be setting up an alert that will play a buzzer sound anytime
our target experiences latency higher that 250 milliseconds for 10% (or more) of a
10 minute timeframe. First, we'll select the "Play a Sound" option from the "Create a
New Alert section, which will prompt us to enter our alert conditions.
There are four different options for setting up alert conditions:
Latency and Packet Loss Over Time - (the option we're using in this
example)
Latency and Packet Loss Over a Sample Count - (which allows us to look
at a certain number of samples, and trigger an alert when a set amount of
samples exceed our desired latency)
Route Changed - (which triggers the alert if any hop within the route
changes)
IP Address in Route - (which triggers the alert when the user provided IP
becomes part of the route)
Once we've set our conditions, click on "Next," and in step 2 we can configure what
sound file we'd like to play, and when we'd like it to play.
There are four different notification preferences:
If we'd like our sound to play when alert conditions start, and then have a different
sound play when the conditions end, this is totally possible (and encouraged!). We'll
go ahead and select "When alert conditions start" for the first part of this alert, and
then choose the sound file we'd like to play and click "Next."
From the alert summary screen, we'll get an overview of what our alert is configured
to do. To set up another sound that will play when alert conditions end, click on the
"Add Action" button.
From this screen, we can select another action type and set the notification
preference we'd like ("When alert conditions end"). Once everything on the alert
summary screen looks to be in order - we can give our alert a name and click on the
"Finish" button.
Once we've finished setting up our alert, we'll land back on the original alert screen,
which will now show our new alert under the "Alerts for this Target" section. If we
want to change anything about the alert (pick a different sound file, adjust the alert
conditions, etc), we can click on the edit button. We can also remove the alert from
a target by clicking on the delete button. Clicking on the delete button in the "Your
Alert Library" section will completely remove the alert from the program (as well as
from any targets it happens to be associated with).
If we've got another target that we'd like to apply our alert to, simply open a trace
window for that target. The alert will be in the alert library, and clicking the green
add button will move it into the "Alerts for this target" section.
Alerting on packet loss.

A common condition to want to alert on is packet loss. The fields you need to
manipulate are in the Alert setup screen is the "Alert conditions" portion.
Example: Let's say you want to notify when packet loss equals or exceeds 40%.
To do this, set "Samples to Examine" to 10, and Alert when "4" or more samples are
over 9999ms. A lost packet always exceeds any number you enter in the threshold
area, so if you want to consider only explicitly lost packets, set this to 9999. If you
want to consider any really high latency packets as well, set this to something lower
(maybe 1000 or 1500).
This only examines the last 10 packets, but let's say you want to examine a higher
period - and notify on a lower packet loss percentage.
Set Samples to examine to 10000 (or some other high number). Alert when "500" or
more samples are over 2500ms. This will alert when you hit 5% packet loss over a
period of a few hours (depending on what trace interval you use).
A note about "average" response times.
Average response times are a problem. The real problem with mean averages is
when a server stops responding - what is the average of the last 10 samples if the
last 10 were timeouts? Because of the problem with this we always do "when X or
more samples is > Y" (this is a median average). You can still get your alert to work
like an average - by saying "when 5 or 10 samples exceeds 300 ms" (this would be
like a mean average over 300ms, but would also fire when there were lost packets).
8.2 - Email Setup (for alerts)
The process of setting up an email alert is mostly the same as setting up any other
alert, with a few exceptions. The first big difference is that we'll be asked to
configure email settings before setting up any other part of the alert.
If we're using a common email carrier (Gmail, Outlook, Yahoo, etc), we can use the
"Quick Fill Settings" dropdown to automatically enter the correct SMTP server name,
and port. Once we've filled everything here out, we can send a test message to
make sure we've gotten everything correct - we'll just enter our email address in the
last field on this screen (where it says "enter a "test" recipient address here") and
click on the "Test SMTP" button. If all goes according to plan, we should receive an
email in our inbox letting us know that we're good to go!
On the screen for step 2, there is an option to edit our email setup if we need to
make some adjustments (just click on the "Email Setup" icon).
Next we'll need to set up our notification preferences, and choose the address (or
addresses) we'd like to send the alert email to. If we need to send the email to
multiple people, we can enter multiple addresses in the "email recipient" field, each
one separated by a comma.
We can also edit the body of the email that's sent by clicking on the "edit template"
button. This will launch a template editor that will provide several different options
for what to include in the body of the email.
Here you can choose from several different options on what to include in the body
of the email, and configure it in either HTML or plain text format. Once everything is
set up, we can click the "save" button and send a test email to make sure that
everything looks like we want it to.
8.3 - Event Notification
Many of the events share a notification mechanism. Here is a list of the types.
Note that any alert can have multiple events of the same type, so you can set up a
single alert to do something at any one or all of these times.
Each time alert conditions are met

(repeating)
The event will happen every time conditions are met. This means the event will
happen over and over again – on each sample that causes the alert to fire. In
previous versions, this was the only supported notification type.
When alert conditions start (enters alert

state)
The first time alert conditions occur, the event will happen. As long as the
conditions continue, though, the event won't be repeated. This is a popular use – as
you find out about new conditions when they happen, but don't have to be bothered
again. As soon as the alert stops happening, then as soon as it starts again, this
event will happen again.
When alert conditions end (leaves alert

state)
This happens when network conditions improve so that the alert is no longer firing.
As soon as the conditions move from bad to good (based on your settings), then
this event will happen. A use of this is to have PingPlotter email you each time
conditions go bad (see above), and then when they improve again – but not to tell
you anything in between.
Each time alert conditions are *not* met

This is the exact opposite of the first notification type above. As long as things are
good on the network, this event will fire each time a sample is collected.
8.4 - Troubleshooting Alerts
If alerts aren't working, there are a number of things you can do to

troubleshoot. Here are some suggestions - and feel free to check out our
support pages (http://www.pingplotter.com/support.html) for more
information.
View the Alert Events Log

The alert events log ("File" -> "View Alert Events Log") provides a summary of any
recent alert activity. This prompt will display the date/time of any alert occurrence,
the target the alert fired for, as well as a description of the alert. This can be a great
help in troubleshooting alerts, as it allows you to see if/when an alert attempted to
fire.
Make sure the alert is tied to the correct
target
By far, the most common reason that an alert isn't working is because it isn't tied to
the correct IP address. If you suspect this may be the case, select the target you're
troubleshooting the alert for, and open the alert panel. Here, you should see any
active alerts for the target (and if there are no active alerts, you can add them from
the alert library from here).
Set up an alert that will fire instantly, with an

event that is very evident.
If you have an alert set up – and tied to a host (see above), but it seems like the
alert isn't working, then changing your alert parameters (or create a new "test"
alert). Set up "Traces to Examine:" to 10. Alert when "1" or more traces are over
1ms. Unless your network is responding in 1ms or less, this alert will fire on the first
collected sample with the alert enabled.
For an event type, use "Play a sound", or "Tray icon change/notification" as both of
these events happen immediately with no wait. In addition, for the "Play a sound",
use "each time alert conditions are met (repeating)", as this will continuously make
sound, rather than just when conditions start / stop. Using this sequence, you
should be able to tie an alert to just about any host and have the alert conditions fire
immediately. Now, add on another event type (IE: email). You can leave multiple
events tied to a single alert – that way you can continue to hear the sound while
you're troubleshooting another event type.
Alert events
9.1 - Play a Sound
One of the most simple event types is to play a sound (ie: .wav or mp3 file) of
some kind.
This event can happen based on the standard notification rules

(event_notification.html), and can play anything that Windows multimedia sound
function wants to play.
Clicking on the "Browse file" option when setting up this alert will lead to a default
directory, which contains a few sound files that are included with the installation of
PingPlotter. Clicking on the "Test Call" button will play the sound file that has been
selected.
9.2 - Send Email

A very popular event type is the "" event.
Before you can create an event to send an email, you must configure your SMTP
server and return email address (email_options.html). Note that your SMTP server
must be accessible on the network to be able to send emails, so it's possible a
network failure may not be able to email you. PingPlotter will continue to try to
send emails once a minute until it is able to get an email out.
Emails are a bit more complicated to set up than most Event types – as it is
dependant on your SMTP server, and you don't want to be overwhelmed with emails
when conditions are bad, but you *do* want to know what's going on.
First off, you can fire emails based on the standard PingPlotter notification
types. See the associated documentation for more details
(event_notification.html).
Send e-mail to:

This can be an individual email address, or a list of addresses separated by either a ,
or a ; (both work equally well). Please do not set this up to be someone at your ISP
unless they have agreed that they want to see this information. A huge portion of
getting problems solved is playing the game right, and overwhelming people with
automated emails is almost certainly going to work against you.
Testing and error messages

Once you have your e-mail set up, use the "test" button to see
what the message will look like (and also to make sure all the
settings are working). Any errors should be displayed here.
Many of the errors that occur during testing can be attributed

to incorrect email setup – so go there and validate your
settings (email_options.html).
Here are some specific knowledge base articles on possible error numbers:
Socket error 10053 (http://www.nessoft.com/kb/39)
Any Socket error is being generated by the SMTP server itself, not PingPlotter, so if
you're getting an error number not listed here, or in our knowledge base
(http://www.nessoft.com/kb), try doing a search on your favorite search engine to
see if you can find more information about the error you're getting.
9.3 - Log to file
The "Log to File" alert writes data to a text file whenever alert conditions are met.
Filename:
The filename is required to have a full path specified (for example:
"C:\ppdata\Alert.log") in order to save the log file properly.
9.4 - Tray Icon Change

Note: this alert event is specific to the Windows version of PingPlotter.
This is a great event to add to most of your alerts. It's helpful to be able to see if
there's an alert condition under way, and a quick glance at the tray can let you know
by using the event.
The notification will do one or both of the following:
Change default icon to red during alert

conditions
If you already have PingPlotter showing in the tray, this will change the existing
green icon and add red to indicate that an alert has fired. If you don't have
PingPlotter in the tray already, then a red icon will be added to the tray. When the
alert condition(s) are over, the icon will change back to blue.
Popup message in tray

This shows a "balloon" message coming out of the tray. Not all versions of
Windows support this message (ie: some versions of Windows 95), in which case
no balloon will show. Only one balloon can be shown at a time, so the newest
balloon always wins (a new balloon message will replace an older one).
9.5 - Web REST Call

The Web REST call event gives you the capability to fire an alert to any service or
program that has the ability to receive REST calls.
When you create a Web REST alert event for the first time, you'll notice that there's a
"place-holder" example already in place:
You'll need to have the specific address for whatever service or program you're
wanting to fire the alert through here. *Most* services will have some sort of
documentation on where to find this address, and what needs to be included in the
body (ie: a security token) in order for things to work.
9.6 - Add/Remove from Summary

This event type gives you the capability to place (or remove) targets into custom
summary screens based off of their performance (which you can specify when
entering your alert conditions). To set up this alert event, you'll want to be sure to
have a custom summary screen already set up.
One of our favorite setups with this alert type is to have two events: one that will
add a target to a custom summary, and another that will remove it. Using this alert,
anytime a target starts to experience high latency (we have the alert set to look at
the last 100 samples, and notify us if 50 or more are over 500ms), that target is
moved into our "High Latency!" summary screen. If the target falls back under that
threshold, then it's then removed from the summary screen. This gives us a quick
view into any of our targets that are currently experiencing issues.
9.7 - Launch Executable

This alert type gives you the ability to run any executable file type when the alert
conditions are met. This allows users to create their own scripts, batch files, etc
that can perform many actions.
Command to launch
This is where users can select what will be executed when the alert fires.
Parameters
If the command to be executed accepts parameters, users can add those here.
Security Advisory
Due to the security implications regarding this alert event, when running PingPlotter
as a Windows service, this alert event must first be enabled by a system
administrator.
Understanding Output
10.1 - Discovering a route
between you and a target
Let's run through a basic scenario where we discover the route between your
computer and an interesting destination (maybe one you're having a problem with).
Normally, when troubleshooting a problem, you want to run PingPlotter against the
server where you're experiencing problems. Maybe that's a web server (in which
case, you'll want to enter that web server's address); maybe it's a game server (in
which case you'll want to enter that game server's address). If you aren't
experiencing problems with your network connection or something you access with
it currently, no worries! Just try and think of something you access regularly with
your Internet connection (such as www.PingPlotter.com
(http://www.PingPlotter.com). or www.Google.com) to use in the exercise below.
We're assuming here that you've downloaded and installed PingPlotter. If you
haven't, please see the Downloading and Installing PingPlotter
(downloading_and_installing.html) section for instructions on how to do so.
So load up PingPlotter, and let's get started!
1. Enter the IP Address (ie 129.41.62.29) or the DNS Name (ie

www.PingPlotter.com) of a destination you may be having problems with into
PingPlotter's Address to Trace: input box. Note: we just want the name of the
destination. You would not enter http://www.problemserver.com/index.html here.
What we want is between the "http://" and the "/index.html."
For now let's leave all the other settings you see on the screen as they are.
2. After you've typed in the address, either press the "Start

(theinterfacesettingsandrtchanges.html)" button, or press the "enter" key on your
keyboard. The trace then starts, and you'll see the upper Trace Graph populate with
the route information to the target you entered. The Timeline Graph for that target
will be displayed also below the Trace Graph.
One thing that is kind of an 'ah ha!' moment for a lot of first time PingPlotter users is
seeing that you really do have that many devices your network traffic passes
through to get to web sites, servers, etc. If you click on a web page link, that 'click' is
passed on by all those hops to that final web server/page, that web server executes
that click, passes the information back to you through all those hops and you see it
on your browser.
It's important to cover the concept of a "Sample Set," because we're going to be
mentioning it a lot. The sample set is defined by the "Focus Time
(theinterfacesettingsandrtchanges.html)" value (which is right under the "Address
to Trace" and "Trace Interval" fields). The "PL%" and "Avg" columns in your trace
graph are all computed off of this number. If this value is set to 10, PingPlotter uses
the last ten samples it's done and bases everything off that number. If it's set to 20,
PingPlotter uses the last twenty traces it's done, etc. As we go through what you're
actually seeing on the graphs, just remember that the "Sample Set" is based off the
value in the "Focus Time" value, and that number represents the number of samples
- starting with the most recent and working backwards.
Some things to consider before we move

on:
We cover what's "normal" for latency and packet loss in a knowledge base
(http://www.pingman.com/kb) entry at http://www.pingman.com/kb/42
(http://www.pingman.com/kb/42)
If you get a "Destination Address Unreachable" message at the last hop in

the trace graph, this means something between your computer and the
final destination isn't receiving and/or returning packets. We cover this in
detail in the PingPlotter section of our knowledge base
(http://www.pingman.com/kb/) at http://www.pingman.com/kb/8
(http://www.pingman.com/kb/8). If some hops are responding, you might
try using a different target address (ie: try www.PingPlotter.com instead
of the address you entered the first time).
If the final destination is working (ie: the Round Trip row is showing), but
some of the earlier hops are not, then don't despair! This could be normal.
See knowledge base articles http://www.pingman.com/kb/24
(http://www.pingman.com/kb/24) and http://www.pingman.com/kb/29
(http://www.pingman.com/kb/29) for possible causes of this behavior.
If you're entering an IP address and would like to "label" that address, or

give it a "friendly name" to make it easier to find in history later, you can do
that by entering the IP Address, then a space, and then the label. For
instance, if you have a core router that you'd like to see displayed in
PingPlotter as "Core Router" (minus the quotes), you'd enter it as
"192.168.0.1 Core router" (omitting the quotes and substituting the
192.168.0.1 for the IP Address for the actual IP Address for your router).
For more details on this, see http://www.pingman.com/kb/23
(http://www.pingman.com/kb/23)..
10.2 - Interpreting Results - A

Quick Example
So let's get into some specific examples of how to interpret the results from
PingPlotter.
For the first example, you're getting intermittent packet loss to www.nessoft.com.
What can we determine from the graph below?
First off, the final destination (hop 16) shows 9% packet loss. There's a problem
someplace in the route, but we need to determine where....
Hop 4 shows 5% packet loss. Hop 5 doesn't show packet loss, though, so you know
that the problem in hop 16 isn't because of hop 4. Hop 4 is likely just a router using
a different CPU path for TTL=0 packets than it does for routing data through.
Hop 9, however, shows 9% packet loss, and this packet loss is carried on through to
the final destination. This is a huge indication of where the problem lies.
Now, all we know from this is that the problem happens after hop 8. We don't know
if it actually happens because of CPU overloading in hop 9, a router problem in hop
9 (or even on the exit side of hop 8), or if it's the connection between hop 8 and 9. A
little bit more troubleshooting is needed for this.
Digging deeper, we can see (from the domain names) that hop 8 is in the rr.com
domain, while hop 9 is in the alter.net domain. Also, the IP addresses show
decidedly different ranges. This is a strong clue that it's actually the connection
between hop 8 and 9 that's causing the problem. It's likely that there's not enough
bandwidth between those two locations.
10.3 - Finding the source of the

problem
We learned how to do a basic PingPlotter trace in the previous exercise
(discovering_a_route_between_yo.html). What we want to do now is take a pre
prepared save file that contains about 2 ½ days worth of fictional data and do more
hands-on work with PingPlotter.
First off, you need to get the data file downloaded for this exercise. The file you
need to download is at www.pingplotter.com/gsg/www.nessoft.com.pp2
(http://www.pingplotter.com/gsg/www.nessoft.com.pp2). Save this file to your
desktop so it will be easy to find (of course you can select another location - just
remember what you specified).
Load up the save file in PingPlotter by going to "File" -> "Load Sample Set," and then
browse to your desktop (or wherever you saved the nessoft.pp2 file) and select the
www.nessoft.com.pp2 file, then click the "Open" button. ¡Ta da! Two and a half days
worth of data for us to play with.
Let's go over some concepts concerning

the Timeline Graph.
Let's start out with this concept – red on a graph is bad. All those red lines you see
on the Timeline Graph indicates Packet Loss for that particular time period.
Remember, that means that PingPlotter didn't get an answer back. There are
times where you could have a flaky router, or even a server that is de-prioritizing
ICMP packets. If you'll remember from the How PingPlotter Works
(howitworks.html) section, this is how PingPlotter gets its information. You
could have a perfectly fine connection through that router, but PingPlotter will
show it at 100% packet loss. For the most part though, when you see red on the
Timeline Graph it means PingPlotter wasn't able to get to that server.
The black line on the Timeline Graph is average latency for the time period you're
looking at. When you zoom in on the graph throughout the next two steps you'll
be able to see the individual pixel-wide points on the graph.
The default Timeline Graph scale is 10 minutes - but what if we want to see
more? Right-Click with your mouse button on the Timeline Graph, and you'll see
that you can show anywhere from 60 seconds on up to 48 hours worth of data
within the Timeline Graph. Go ahead and select 6 hours. Notice that you're now
looking at six hours worth of trace data.
Feel free to select different time periods and see how the contents of the Timeline
Graph reflect what you select. What we want to illustrate here is that via the
Timeline Graph's right-click mouse menu, you can easily zoom out to look at a trend
for a day, and then zoom in to a spot that looks interesting – down to 60 seconds
worth of data.
The "focus area" on the Timeline Graph (which is brought up by double clicking
anywhere on a timeline graph) shows you the current sample set that you're
viewing.
Remember that value is set in the "Focus Time" value. When you first load up this
save file, PingPlotter is starting at the last trace done before the data was saved,
going back 10 traces, and then calculating the values for the Trace Graph based on
that value. Note also that PingPlotter shows you the date and time information for
the sample set that you're looking at in the area up above the Trace Graph.
You can change the focus of the Timeline graph, and subsequently the data in the
Trace Graph, by double-clicking on any area of the Timeline Graph you want to look
at. In case you're wondering, you can have an active trace going while you move
around the Timeline Graph. You do not need to save the data, stop the trace or do
anything else for that matter. Just double-click on the area you want to see.
Now change the Focus Time to 150 samples. See how the values in the Trace Graph
change to reflect those additional 150 samples/traces? Change the Focus Time to
ALL, or 0 (0=ALL in this context). ¡Guau! If you look at the Sample Set Time above
the Trace Graph you'll now see that you're looking at a lot of data. In fact, you're
looking at all 44,843 traces, or ALL of the traces that were in the file we loaded. Your
PL% and Avg columns in the Trace Graph now reflect all those traces. Now you can
change it back to something smaller (100 is generally a good value to use).
If you're not there already, right-click on the Timeline Graph and set the time
you want to see to 6 hours. To move back through the data you click-drag, or
left-click, and while the left button on your mouse is held down you move the
graph to the right. To move forward in time, you click-drag to the left. Are things
starting to “click," as far as how you can move back and forth through time on
the Timeline Graph? If you have a lot of samples to move through, do yourself a
favor and set the graph scale accordingly (again, by right-clicking and choosing
a time) before you do. For instance, if you've zoomed in to where you're looking
at 5 minutes worth of data and then need to go back twelve hours – set your
graph scale to something like 3 or 6 hours before you start.
Tip: You can also use the keyboard to navigate backwards/forwards, as well as
quickly get to the beginning or end of Timeline Graphs. The shortcut keys used to
do this are covered in the Interface Graphs (theinterfacegraphs.html) portion of this
manual.
Hopefully by now you've been clicking all over the Timeline Graph, and seeing that
the Timeline Graph does indeed change when you select a new sample set to look
at. So how do you get back to the current ti me/date? Bring up the Timeline
Graph's right-click menu and select "Reset Focus to Current." If you don't see that
listed in your right-click menu….well, then, you're already current.
At this point if you're thinking, “Hmmm, this Timeline Graph stuff is cool, but I want
to see a Timeline Graph for Hop 1 too!”, then today is your lucky day. You can do this
by double-clicking on that (or any) hop - or by right-clicking and selecting "Show this
Timeline Graph." Double-clicking again will hide that same graph. If you have a lot of
Timeline Graphs open, clicking once on the hop for that Timeline Graph will cause
that Timeline Graph to flash briefly so you can pick it out of the list.
Checkpoint
So let's summarize what we've done, and what we know at this point about the
Timeline Graph.
You can change the scale by right-clicking and selecting one of the values
listed.
The focus area on the Timeline Graph shows you the current sample set,
and you can change it easily to reflect the time period you want included
in the Trace Graph.
You can move around within the Timeline Graph by click-dragging or using
the shortcut keys.
By changing the graph scale, click-dragging then changing the scale back,
you can zoom in and out of different time periods you want to analyze.
PingPlotter tries to keep your "focus period" in view on the timeline graph,
and you can use this if you're zooming in on a period. Focus the period
you're interested in (double click on it), and then zoom in.
If you want to get up to the very last sample set in a save file, or the last
sample done if PingPlotter is actively tracing a target site for you, “Reset
Focus to Current” on the right-click menu for the Timeline Graph will get
you there.
If you want to turn on or off visibility for a Timeline Graph for a hop, you
can do so by double-clicking that hop, or by right-clicking on that hop and
selecting “Show this Timeline Graph”.
To quickly find a Timeline Graph for a particular hop, if you have a lot of
Timeline Graphs showing for instance, click once on that hop and the
associated Timeline Graph will flash.
10.4 - Finding the source of the

problem - part 2
Let's apply and build on what we've
learned and dig deeper.
The black line on the Timeline Graph shows you the latency over time. As you
zoomed in on the graph earlier you saw that really what you're seeing is pixel-wide
entries that represent the round trip time, or latency for the host/device who's
Timeline Graph you're looking at.
Red, on the other hand, represents packet loss (PingPlotter didn't get anything
back). We have numerous articles that go over different reasons why you could see
packet loss in the Knowledge Base at www.pingman.com/kb
(http://www.pingman.com/kb). Our goal here is to help you understand at a basic
level how PingPlotter can help you figure out why that loss is happening.
Packet loss, of course, isn't the only thing that can cause poor performance for your
particular application. The other big factor is latency. For online games, for
instance, latency is a killer. Let's review our sample data, and look at a trouble spot
so we can learn more how to interpret what PingPlotter gives us that no other tool
can.
Let's look at the time period between 11am and 12pm on February 14, 2015. Let's
take the approach that we were browsing the web at that time and were running
pcAnywhere into our computer at work. The pcAnywhere session goes to pot.
1. Set "Focus time" to somewhere between 30-60 minutes (we're using 60 minutes
here because it's easy to see the focus period on the 24 hour graph).
2. Change the Timeline Graph scale to 24 hours (remember: right-click then pick 24
hours), and then scroll all the way to the beginning of the graph
3. Take a look around at that time between 11:00 am and 12:00 pm. Double-click a
time period somewhere around the 12:00 pm time. You'll notice the focus lines
appear on the time graph, and the upper graph will show packet loss.
4. Wow, look at that packet loss! 13% at hop 9, 14% at hop 16. Notice how the
packet loss is added at hop 9, and then all the downstream hops also show high
packet loss. This is a strong (compelling, in this case) indicator that hop 9 (or the
link between hop 8 and hop 9) is the reason we're seeing packet loss.
5. Notice the packet loss trending over time. This indicates some kind of time
based load problem. Also, the fact that the packet loss starts at the junction point
between rr.com and alter.net indicates a possible problem at the connection
between these two providers. It's possible that rr.com doesn't have enough
bandwidth to service needs.
6. Let's turn on a couple more timeline graphs. Double-click on hop 9 and hop 8.
Notice the difference in packet loss. Notice, too, that the latency is still relatively
high, even at hop 8, and it's also showing time-based problems. Double-click on hop
1, and notice that that *to* also shows a time-based latency problem. This is a
separate problem from what we're seeing at the hop 8 to hop 9 junction point!
Looks like we should contact rr.com and find out if they can help us solve this
problem!
7. Try zooming in on a problem-period by changing the timeline graph scale to

something lower. When you see an interesting period, double-click on it to "focus" it,
and then change the timeline graph scale to zoom in or out. This gives you a close
up view of the data with more detail.
Now, it should be noted that spikes on your graph may not be really high latency. A
spike in the graph is high latency for that period displayed on the graph. The
Timeline Graph auto-scales itself, so to see what that high spike is you need to look
to the left-most part of the Timeline Graph. In this case the value we're looking for is
87ms.
This was a really quick example of moving around within PingPlotter and digging
out information about not only what's going on with a connection, but really
focusing in on a problem. Let's move on now and talk about collecting this data
over time and preparing a good case for your ISP (or someone able to solve this
problem!).
10.5 - Interpreting Results -

Longterm Monitoring
PingPlotter allows you to use the timeline graphs to zoom in on any particular time,
so even if you weren't there (or didn't save an image) when something was
happening, you can still recover that exact image later. You shouldn't ever have to
be sitting in front of your computer when an outage happens, or you experience
other problems on your network, to get the data you need from PingPlotter.
The Scenario:
You're having outages (or situations you want to communicate to your ISP)
randomly throughout the day (let's say twice a day). The problem is that you can't be
there every time an outage happens so you can save a graph image
(theintefaceeditmenu.html).
For this example, you're keeping 24 hours of data in memory or even more. We
suggest that you normally use 2.5 second trace intervals and keep 200,000 samples
in memory (this is almost a week's worth of data). You can change the number of
samples to keep in memory in the Auto-Save (advancedoptionsautosave.html)
section under the Edit/Options menu selection (theintefaceeditmenu.html).
Using PingPlotter's timeline graph (theinterfacegraphs.html), you can see over the
past X time period (see below) to identify a time period where there was problems.
Problems will demonstrate themselves as packet loss (red), or high latency.
Now you want to show the route, and the packet loss/latency in the upper graph for
that time period. Since that time has already passed, you need to change the focus
of the upper graph to that time in the past.
First off, you need to make sure your "Focus Time"

focuses in on just the period in question, so let's
change that to 100 (it's important to not have it set to 0/all, but to have it be a
number smaller than the number of samples in memory to be able to focus the
upper graph). Right click on the timeline graph and pick a reasonable period of time
to set the viewable time period. For instance, you may want to set it to six hours so
you're not scrolling forever. You can then "click and drag" the graph to the left to go
back to the time period you want to focus on and drag it to the right to go forward in
time.
Double-click on the "problem period" in the lower graph. You'll see a focus rectangle
appear on the lower time graph, and the upper graph will change to represent the
data you have "focused" in the lower graph. Once you've done this, you might want
to change the scale of the lower graph to show more detail. Right-click on the lower
time graph again and change the scale to an hour (or maybe even 30 or 10 minutes
depending on how long the outage was). The focus rectangle should still be visible.
You can fine tune the data being displayed in the upper graph by double-clicking on
the lower graph again.
Using these techniques, you should be able to zoom in on exactly the right data to
best illustrate the problems you're seeing. You can look at the data after the
problem occurs and get the perfect picture and not have to sit there watching
PingPlotter all day and night.
You can auto-save that data by for instance having the auto-save
(advancedoptionsautosave.html) function in PingPlotter create new files every day,
and then load up a prior day to do the same thing you did above for a particular
time. This gives you the capability to have pretty close to 100% coverage of your
network performance and be able to zoom in on any particular outage, period of
slow response, etc.
The options in the alert setup (help_alerts.html) do allow you to have the .PP2 file
(trace data) emailed, and then you can use these same capabilities to zoom in on
that data.
10.6 - Interpreting Results -

Gamers
For this example, let's assume you're an online gamer - specifically, a Quake III
player (though the following is representative of any online game really - MMORPG,
RTS, racing sims, fighting games, etc.). You've got two servers that are running the
same maps you like to play, so the only issue you have is which one out of the two
is going to give you a better connection. We realize some folks aren't going to be so
patient as to use the method below to decide which server they're going to play on...
but bear with us here. We're learning! The same topics we go over in this section, as
far as graph interpretation, are also applicable if you were trying to figure out why a
connection to a specific server you were just playing on is so cruddy.
The first thing you need is the IP addresses or DNS names for the two servers.
You'll launch PingPlotter, enter the IP address of the first server into the Address to
Trace (theinterfacesettingsandrtchanges.html) box and click the Trace button. 2.5
seconds is a good value for the trace interval
(theinterfacesettingsandrtchanges.html), and the # of times to trace
(theinterfacesettingsandrtchanges.html) should be unlimited (we're gonna watch it
for awhile). Then, start a trace to your second server's IP address using the same
settings you used for the first server.
You then go get yourself a Diet Pepsi, do some stretches or whatever in preparation
for a night of gaming. When you get back to your computer you'll have two graphs
that look similar to the ones below. Let's analyze both and see which server you
want to play on.
Hmm. This doesn't look too bad until you get to hop 15 and start looking at the
history graph. Let's take the time line graph (time_line_graphing.html) first.
Red is bad. Every time you see red on the history graph you had a timeout
(howitworks.html), or in other words there's dropped packets. Packet loss is the
bane for most online games. When you're running across a big open area and then
all the sudden *blip,* you're on the other side (and most likely dead), that was more
than likely caused by timeouts, or packets you didn't get to (or back from) the
server. Besides the red lines on the history graph, you can also see your packet loss
in the PL% column and, if you look at hop 16, the horizontal red line contains your
packet loss value.
Digging a bit deeper, you can see that you're running under 100ms all the way down
until you hit hop 15. Notice that you move off of LevelX's backbone into BestPeer
between hops 8 and 9. No problem there, there's plenty of bandwidth between those
two providers since the time doesn't really go up. From the DNS on hop 8, we can
see that hop is a gateway (thus the "dsl-gw7" part of the name) to some DSL
customers. Where we start running into problems is when we get off of BestPeer
and hit the Mediagods domain that's hanging off the DSL link. All the sudden your
latency goes up to 400+ms at hop 15. That DSL connection is busy. Once you make
it to the server at hop 16, not only is your latency still way up there, but you're
getting 9 to 10% packet loss. That server is a busy bee also it seems. So busy that
he's not keeping up. Combined with the bandwidth saturation we're getting on the
DSL line itself, it's best to try later. We don't want to play here.
Now let's look at our second server.
Now this is more like it. Really, anything under 150 ms is a great connection. We
don't even make it over 40ms until hop 12. Sweet.
Let's look at that connection between hops 11 and 12. Notice from the DNS names
that you actually go from Seattle across Global Crossing's backbone to Cleveland.
When you factor in speed of light latency, you can account for about 40-50ms of
your latency to hop 17 with that hop across the backbone between hops 11 and 12.
So you've got a 120-130ms ping to hop 16. That's pretty good. If you didn't have that
fat pipe installed (and were instead running a modem) you'd probably be running at
about 220-230ms for your latency.
"What about that 11% packet loss at hop 15?", you ask. Judging from the numbers
for that hop and hop 16, what we're most likely dealing with here is a router that
probably has a low priority for ICMP packets. A lot of network admins will set a
router up to drop ping/ICMP packets first if it starts getting busy - have a look here
for more details (http://www.pingman.com/kb/5)
So which server are you going to play? Obviously it's the second server above.
Other considerations
Your graph results can be affected by a number of things that are out of
PingPlotter's control.
In the analysis of the second graph above, we mentioned that hop 15 is more
than likely just a problem with that router not giving us back good information.
Many routers put a low priority on ICMP traffic (howitworks.html). Others don't
even echo back ICMP requests (this will show up as a blank entry for that hop).
Obviously, PingPlotter has no control over these situations.
PingPlotter can't track the route that your traffic takes on the return trip from
the server back to you. If your inbound traceroute traffic is taking a different
route back to you than the outbound traffic to the server, this is called an
asymmetrical route. By definition traceroute doesn't take these types of routes
into account and, unfortunately, PingPlotter isn't going to be able to tell you
about problems with the return route in these cases. One clue that this is
happening is that you'll have a great trace up until the last one or two hops on
your trace. In other words, you don't have an easily identifiable problem at hop
X further up the route that is mucking up the rest of the route downstream.
One thing you can do is save your trace data to a text file and post it up on a
support message board for the particular game that you're playing. Even better,
save off a graph and post it instead. Many savvy game server admins will actually
do a traceroute (or even better a PingPlotter trace... *smile*) back to you and be
able to tell you if there's problems with a route back to you when asymmetrical
routes are involved.
There are some sites that can do traceroutes back to you if you want to investigate
on your own. They can be found here (http://www.pingman.com/kb/3).
In closing, we can't emphasize this enough: latency is the bane of online gaming.
Much more so than bandwidth limitations. The good thing is that PingPlotter can
tell you this latency, and provide you with ammo in the way of trace and graph data
when you're beating up on your ISP.
10.7 - Interpreting Results - ISP

Problems
For this example, we're assuming the role of a user that's having problems with a
broadband connection. What we'll be taking a look at is a few days worth of trace
data.
Before continuing, if you're not familiar with how the graphs work in PingPlotter
please make sure you've read the introduction to graphs (theinterfacegraphs.html)
earlier in this tutorial.
One common mistake we see folks make is that they'll trace to their ISP's border
router. This is a bad thing. If you're tracing to the border router and your route
changes (ie they take that router down for maintenance or you get load balanced
onto another router) you really have no idea what happened. If you want to keep
your traces local to your ISP, trace to an address that isn't going to change on you
like you're ISP's mail server. This is actually a good thing to do if you're having mail
problems and it's your ISP's mail server going down. Otherwise just pick a
destination that you know has a reasonably good chance of always being up. This is
a better choice since routes within your ISP can change, and PingPlotter keeps
track of those route changes. The cool thing is that you're doing a traceroute here,
not a ping, so even if that destination host goes down you can drill down on the
timeline graph and see if it's your connection, or if it's just the destination being
down (as in all hops but the destination don't show timeouts).
Another problem with tracing to your ISP's border router is that your ISP will not
respect the data that you collect this way. No application targets a border, so they
have no reason to trust this data. For best results, you want to pick a target that is
one you use and are having problems with.
Note: For clarity, all the graphs below show us ignoring Hop 1
(theintefaceviewmenu.html) which you to can do from the View Menu. All the
graphs were saved with the File/Save Image command within PingPlotter then
converted to .gif for this tutorial.

Copia Traducida de Pingplotter - V5manual

Cargado por

Copyright:

Formatos disponibles

Copia Traducida de Pingplotter - V5manual

Cargado por

Información del documento

Título original

Derechos de autor

Formatos disponibles

Compartir este documento

Compartir o incrustar documentos

Opciones para compartir

¿Le pareció útil este documento?

¿Este contenido es inapropiado?

Copyright:

Formatos disponibles

Copia Traducida de Pingplotter - V5manual

Cargado por

Copyright:

Formatos disponibles

21/9/2018PingPlotter

© 1998, 2018 Pingman Tools, LLC

Si bien se han tomado todas las precauciones en la preparación de este

6.2 Barra de destino

6.3 Gráfico de seguimiento

6.4 Gráficos de línea de tiempo

6.5 Gráficos de resumen

7.2 Guardado automático de datos

7.3 Ejecución como servicio

7.4 Manejo de múltiples destinos

7.5 Configuraciones nombradas

7.7 Exportación de datos para análisis posteriores

7.8 Cambios de ruta

7.9 Seguimiento de DNS dinámico

7.10 Compartir datos de PingPlotter con otros

https: // www.pingplotter.com/export/manual 3/139

8.1 Creación / configuración de alertas

8.2 Configuración de correo electrónico (para alertas)

8.3 Notificación de eventos

8.4 Alertas de resolución de problemas

9.2 Enviar correo electrónico

9.3 Registro en archivo

9.4 Cambio de icono de bandeja

9.5 Llamada REST web

9.7 Iniciar ejecutable

10.2 Interpretar los resultados: una E rápida Ejemplo

10.3 Encontrar el origen del problema

10.4 Encontrar el origen del problema - parte 2

10.5 Interpretar los resultados - Monitoreo a

10.6 Interpretar los resultados - Jugadores

10.7 Interpretar los resultados - Problemas del ISP

10.8 Interpretar los resultados - Mal hardware

10.9 Interpretar los resultados - Saturación del ancho de banda

largo plazo10.10 Voz en offproblemas de IP (VoIP)

10.11 Creación de un caso convincente

Solución dehttps://www.pingplotter.com/export/manual 4/139

11.1 IPv6 e IPv4

11.2 Sockets TCP sin procesar y WinPcap

11.3 Rastreo desde un servidor remoto

11.4 Los argumentos de línea de comandos

11.5 Opciones del instalador yde MSI

12.2 Opciones generales

12.3 Opciones web Server

12.5 Opciones de visualización

12.6 Opciones del motor

12,7 Auto-Guardar opciones

12.8 Flex almacenamiento

12.9 final Hop Sólo

13.2 Menú Edición

13.3 Espacio de trabajo del menú

14.3 Vínculos relacionados e interesantes

14.4 Acerca del uso compartido y la privacidad

Si está leyendo esto, es probable que se haya encontrado (o se esté encontrando

PingPlotter se creó originalmente en 1998 para solucionar problemas de retrasos

PingPlotter puede ayudarlo con una variedad de problemas relacionados con la

Depende de una red o servicio de Internet, que tiene problemas,

Usted es un administrador de sistemas, y necesita saber cuándo falla la

Un proveedor le dice que no puede ver ningún problema (cuando

En general, si es usuario de algo que depende en gran medida de una red o