|This is the talk page for discussing improvements to the Network monitoring article.|
|WikiProject Computing / Networking||(Rated Start-class, Low-importance)|
It has been suggested by 220.127.116.11 that the article Deep packet capture be merged into this article, Network monitoring.
- NO - Asolutely not. Deep packet capture means capturing and storing entire streams of data coming into or going out of a server for either real time or later analysis. Think of a data Tivo.
Network monitoring on the other hand, pings a server with a variety of protocols and checks for liveness on a regular basis. If a failure is detected, the problem is reported to the NOC via e-mail, page, etc.
- You offer no proof that Alantekore is employed by Solera Networks. Other users have contributed to this article and you don't offer any proof of their employment there either. Deep packet capture and network monitoring are clearly not the same thing as I pointed out above. Kgrr (talk) 17:50, 1 April 2008 (UTC)
- Disagree - keep seperate, deep packet capture or inspection can be a tool used in network monitoring, however it deserves its own article. It is a much narrower field, that could get a three word mention in Network monitoring, but there is too much other ground to cover to have so much detail here. Graeme Bartlett (talk) 20:35, 1 April 2008 (UTC)
- Bad idea - Can I just say that I think this is a bad idea. Packet capturing is at best a subset of network monitoring. If all the flavors of network monitoring were to be listed in this article, it would have to be separated out again. Please do not bring packet capturing into this article, but instead refer to it. HiTekVagabond (talk) 02:10, 2 April 2008 (UTC)
I'm closing the frivolous merge request of Deep packet capture, now Packet capture with Network monitoring article. 18.104.22.168 is a Jefferey Vernon Merkey sockpuppet. Case closed - No merge. Kgrr (talk) 09:27, 4 April 2008 (UTC)
Scope of network monitoring should be defined better
First of all, network monitoring is not just monitoring "slow or failing components" but also monitoring behavior of traffic(IPFIX/netflow/sflow) and the traffic itself (Wireshark and all other sniffers). I am sure no one will be against to assume netflow monitoring or sniffing as a main part of network monitoring.
At this point, we are facing with a classification and definition challenge. I already tried to do this at here []. The language of the text is not suitable for wikipedia so it should be re-writen. As the owner of the text, I am allowing any editor of wikipedia to re-use re-write this text without any reference to it within wikipedia project.
Of course, Network monitoring layers should be discussed and clarified within community.
Merged content from Internet server monitoring
A strange sentence.
Someone wrote a sentence: Commonly measured metrics are response time, availability and uptime,
and then we read: although both consistency and reliability metrics are starting to gain popularity.
Although? What is it for? What do these two parts have to do with each other? 22.214.171.124 (talk) 18:46, 13 April 2014 (UTC)