Steps to reproduce:

1. Import a non-compliant YAML template
2. Navigate to the data-collection/templates section
3. Click import > choose the yaml file 
4. Click import again > click OK
5. Read the following error `Invalid parameter "/1/uuid": UUIDv4 is expected.`

Result:
Why would anyone consider this error message useful?  I see two issues with it.
1. The "/1/uuid` path... is nonesense. what does 1 stand for? First nested element, or first object, first tab index.  It's not clear.
2. the fact it reads "UUIDv4". A UUIDv4 value would look something like this `36a4c36e-15a8-43dc-9287-99780609f339`, not the required 32-hex-character string, like `36a4c36e15a843dc928799780609f339`.

If you are going to put time into writing error messages into the code, at least make them helpful.

with logLevel=4, i've got millions of lines per minut in my `docker logs zabbix-server-1` console output. I coud waste hours and hours dumping to file-system, grepping through the files... i'd rather find the code that throws this stupid error message and fix it.

Expected:
 - either mention the line-number (raw or parsed), line-text, adjacent-line-text (error near x string), absolute-path (/templates/template(1)...) or or even report on the invalid UUID value that it's complaining about.