Updated net.tcp.service key, and the collection stabilize, why?

[cesarsj]

Updated net.tcp.service["http" ,, "80"] key to net.tcp.service [http] and the collection stabilize, why?

Our Zabbix came from a migration from version 1.8.11, so several items continued with certain parameters out of date. A camera host was showing a lot of alerts, so replace the last () <> 1 function with max (5m) = 0, but I also changed the item key, as I said in the title of this post, and after that, not only the alerts decreased, as the collection stabilized, registering only 1 now (up). When it was ["http" ,, "80"] I was recording about fifty '0' (down) a day, which I came to think that the camera or the link could be in trouble with.

[cesarsj]

Are you sure this is due to the key format?
It could be a coincidence. Maybe there were problems. I think you need look to Zabbix logs and target server logs... maybe logs give you a clue

Before:

Name: Is CFTV CCE_ENT_FOYER_02 port 80 alive
Type: Simple check
key: net.tcp.service["http",,"80"]
Type of information: Numeric (unsigned)
Update interval: 5m
History: 3650d

After:

Parent items: Template App HTTP Service
Name: HTTP service is running
Type: Simple check
key: net.tcp.service[http]
Update interval: 1m
History: 1w

The Zabbix Server log does not show me any related information.

[Hamardaban]

It is possible that the root of the problem is the use of incorrect key syntax.
net.tcp.service["http" ,, "80"] - wrong
net.tcp.service[http,, 80] / net.tcp.service[http] - right

[cesarsj]

It is possible that the root of the problem is the use of incorrect key syntax.
net.tcp.service["http" ,, "80"] - wrong
net.tcp.service[http,, 80] / net.tcp.service[http] - right

How then can several cameras still be functioning like this, with net.tcp.service ["http" ,, "80"]? I saw here that there is a camera with this syntax that this year reported only 3x the trigger, with an interval of 5 minutes.

[Hamardaban]

Those who have the source codes will see everything.
As in any deterministic system-do it right and everything will work. May be.....
I saw inaccuracies in your settings and attract your attention to it.....
Did it correctly but it doesn't work? Write to support!