[nitpick] The documentation URL https://www.elastic.co/docs/reference/fleet/alert-templates#alert-templates appears to use an unusual format. Elastic documentation typically uses URLs like https://www.elastic.co/guide/en/fleet/{version}/... rather than /docs/reference/. Please verify this URL is correct and will be accessible to users.

this is the correct url. i don't like hard coding the URL here, but not sure what else to do.

You could use linkMap.RenderLink(), and rely on the links_table.yml file. But this should still need to have a fallback in case the file doesn't exist or it doesn't contain the expected url.

There is a linkMap already initialized in renderReadme, you could pass it to renderAlertRuleTemplates.

hey @daniela-elastic, please can you review the preamble content here (lines 26-40).

this is the text that will appear before the list of templates in the readme.

we currently link to the existing docs page, which needs improving, but i think it's the right place long term.

Should we mention that these are templates that you can use to easily create and customize alerts. But are not live alerts in and of themselves.? Something along the lines of "Alert rule templates provide pre-defined best practice configurations that you can use to easily create alert rules in Kibana."

happy to take your version. i think it says pretty much the same thing.

i think we should avoid putting more detail about how these are used in the package readmes, and leave that for the shared docs page that's linked below.

Wonder if it's worth mentioning that you can create an alert based on the recommended configuration in the documentation regardless of the stack version. Ultimately, the main ingredients you need are the threshold. and other rule config - things that exist in all recent versions of the stack. The only thing you cannot do with pre 9.2 is the ability to see the alert rule asset in the asset tab of the integration, click on it and the alert rule is prepopulated with the config. But the hard part, or rather the are where we help the user the most is with the actual content - they don't have to go and do their own research to figure out which metrics to alert on and with what config.

i think this kind of generic information probable belongs on the docs website, not in the package itself.

Nit. Avoid using underscores in Go file or package names.

i followed the existing convention in the repo on this.

You could use linkMap.RenderLink(), and rely on the links_table.yml file. But this should still need to have a fallback in case the file doesn't exist or it doesn't contain the expected url.

There is a linkMap already initialized in renderReadme, you could pass it to renderAlertRuleTemplates.

I'm not sure, should these functions (setupFunc and validateFunc) add t.Helper() ?