Automatically monitor your Internet service and provider with alerts to problems
Track Internet disconnections, provider outages with historical data, and automated speed testing.
For Windows, Linux, ARM64, ARMa7. Learn more by visiting www.outagesio.com
Notice: If you created an account on app.outagesio.com, simply use the same credentials to log in here.
  • 1 Votes
    9 Posts
    516 Views

    Maybe we were not understanding each other.
    I reviewed this post and I think what you are asking for is to specify what you'd like to ping.

    If so, this is something we've considered and may implement in the future but I'd like to explain why it's not that way right now.

    The main goal of the service is to let you know if your ISP is having problems. That means source and destination but not specifically with the ISP, only through it. In other words, so long as the destination is outside of the ISP, you'll be able to tell when/if your ISP is having problems.

    If we set the ping destination to a certain hop, then you'll only ever know if that hop becomes unavailable and since packets can take different paths, you may not know about other connections failing.

    This is why we just go through the provider to our own network where we have target servers that let the agents know if they reached or didn't reach the target, logging in between when there are IP outages.

    Now, if you were not even seeing hops coming in, that would mean that ICMP is being blocked somewhere and that would affect one aspect of the agent being able to determine outages. Pings aren't really that important but they play one part. There is a constant test being done for source/destination latency. If pings start showing a certain amount of latency, that will trigger an automatic speed test.

    I hope this helps to explain.

  • Agent Ping graph stopped working

    Solved Linux
    8
    1 Votes
    8 Posts
    394 Views

    Ok, so at least we know that pings can be sent when the agent is able to get them.

    When I checked earlier, the agent had no pings to send which means it wasn't getting any results from the operating system.

    The pings aren't really important in terms of being an accurate measurement. They are mainly being sent as information that could be useful in some situations but mostly to see if there is a substantial change in latency between point A and point B.

    If pings latency goes up by a certain percentage, the agents algorithm considers that this could mean something happening and can trigger a speed test for example and other tests.

    However, if pings aren't being sent, it means the agent is not running right as ICMP is one of several functions used to also determine if there is an IP outages.

    All that to say, it's important that you see pings being sent to the dashboard.

    Since restarting the agent got pings going again, to me, it means maybe there is something on the OS that is monitoring certain behavior and limiting something like ICMP.

    I would rule out the agent as having a bug because we would have seen it by now as there are many others running the same version.

    These can be a bit hard to figure out sometimes. Let's see what happens next.

    In terms of running as a service, I think this is what you are looking for.
    Monitor your Internet with raspberry pi, nanopi and other arm devices

  • 1 Votes
    3 Posts
    185 Views

    Hi, were you able to find the problem?