Be careful with very big json-s. preprocessing takes a lot of power... I just had to "call to order" some guys, who were trying to pull some metrics over http, ~8M "file" per host, maybe 80k lines or so... from ~30 hosts every minute... that proxy did not last very long... Maybe if you throw loads of memory and CPU on it, but with 12G mem 2 CPU-s... was exhausted very quickly...
So always try to use "as much as needed and as few as possible". Just as Splitek said above... don't waste resources and throw stuff away, but also.. don't throw too many things at preprocessing also...
Yes. you should modify your template (or clone it and modify that one, if you want to keep original available). Do not worry, if any future update/upgrade has new versions of templates, they will not overwrite your changes. Update of templates is left for you to do then, so you can include those changes, what you need.
Macro length is stated in docs
"Maximum length of a user macro value is 2048 characters (255 characters in versions before 5.2.0)."
If this is too short for you, you can always use JS preprocessing and drop info directly from discovery json. There you are not limited to any length.
So always try to use "as much as needed and as few as possible". Just as Splitek said above... don't waste resources and throw stuff away, but also.. don't throw too many things at preprocessing also...
Originally posted by ElVengador
Macro length is stated in docs
"Maximum length of a user macro value is 2048 characters (255 characters in versions before 5.2.0)."
If this is too short for you, you can always use JS preprocessing and drop info directly from discovery json. There you are not limited to any length.
Comment