4 ms·

Shameless is exactly right. Any inclination I may have had to even consider looking at your product just evaporated.

dkhenry 14y ago
I am curious as to why that would be ? I think that the product that I helped develop would provide immediate value for someone in this situation, and I think it would be unethical to suggest it without at least a cursory acknowledgement of my bias. Or does the fact that I work at a company solving these problems preclude me from participating in the conversation ?
- mfringel 14y ago
  At a guess, it's because you don't describe how it would help. "Just do a TopN report" is not a diagnosis, analysis, or furtherance of the discussion. If you want to do an effective shameless plug, write a few sentences about how your product would have helped from the beginning of the incident, through its resolution. Show how it would have saved time/effort and given more visibility into the problem. This was a multi-hour incident with code-level escalation to the network hardware vendor; assume complexity.
  - dkhenry 14y ago
    So I see. I think I didn't take the time to define my terms, or give the full sales pitch around them. I am not going to give the sales pitch, but TopN is a style of report that can query in real time every metric across every performance metric available and find not only find and alert on ones outside of normal operating parameters, but predict which ones will go haywire in a given time frame. This means no going around to all your switches to figure out which ones are causing problems. In this specific instance if you had an indicator on an OID .1.3.6.1.2.1.17.4.3.1.1 you could see how big the MAC table was and have noticed when it dropped below the expected value. This would have alerted immediately letting you know not only that you had a problem, but on which switches there were issues. Alternatively you could have set alerts on any number of packet level indicators.
- nixgeek 14y ago
  Would you be able to describe how a TopN report helps here?
- imbriaco 14y ago
  I would have been less offended if your initial comment wasn't as presumptuous. You most certainly have a right to participate in the conversation, but there was no useful content in the post. It came across in exactly the same was as the email messages I get from colocation providers whenever the one I host with has a problem. It frankly smacked a little bit of "ambulance chasing", and that turns me off. If you had bothered to provide more actual information about what your software could have done for us, I would have reacted very differently.

I am curious as to why that would be ? I think that the product that I helped develop would provide immediate value for someone in this situation, and I think it would be unethical to suggest it without at least a cursory acknowledgement of my bias. Or does the fact that I work at a company solving these problems preclude me from participating in the conversation ?

mfringel 14y ago
At a guess, it's because you don't describe how it would help. "Just do a TopN report" is not a diagnosis, analysis, or furtherance of the discussion. If you want to do an effective shameless plug, write a few sentences about how your product would have helped from the beginning of the incident, through its resolution. Show how it would have saved time/effort and given more visibility into the problem. This was a multi-hour incident with code-level escalation to the network hardware vendor; assume complexity.
- dkhenry 14y ago
  So I see. I think I didn't take the time to define my terms, or give the full sales pitch around them. I am not going to give the sales pitch, but TopN is a style of report that can query in real time every metric across every performance metric available and find not only find and alert on ones outside of normal operating parameters, but predict which ones will go haywire in a given time frame. This means no going around to all your switches to figure out which ones are causing problems. In this specific instance if you had an indicator on an OID .1.3.6.1.2.1.17.4.3.1.1 you could see how big the MAC table was and have noticed when it dropped below the expected value. This would have alerted immediately letting you know not only that you had a problem, but on which switches there were issues. Alternatively you could have set alerts on any number of packet level indicators.
nixgeek 14y ago
Would you be able to describe how a TopN report helps here?
imbriaco 14y ago
I would have been less offended if your initial comment wasn't as presumptuous. You most certainly have a right to participate in the conversation, but there was no useful content in the post. It came across in exactly the same was as the email messages I get from colocation providers whenever the one I host with has a problem. It frankly smacked a little bit of "ambulance chasing", and that turns me off. If you had bothered to provide more actual information about what your software could have done for us, I would have reacted very differently.