Skip to content

[alerts] investigate usage of handlebars instead of mustache #84218

@pmuellr

Description

@pmuellr

For alerting, we currently use mustache as our templating library to render strings with variables from the alert execution. We've wondered about switching to handlebars instead, and this issue is to discuss/research that.

Handlebars is basically mustache++. One significant issue we'd have to deal with is whether all our existing customer's templates would still work.

Beyond that, I did just a bit of peeking at handlebars for issue #79371 (comment) , and noted both the complexity issues (on the customer's end) and security concerns. I remember coming away from the investigation feeling that handlebars is very much aimed at providing developers a richer experience than mustache, which it certainly does. But we're not targetting developers - ideally it would be nice to have something in-between mustache and handlebars - a little more function, but not so much that the result is a new programming language.

What led us looking at handlebars again is being able to provide ease-of-use functions for use in a template. And the fact that Dashboard URL templating uses handlebars.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Feature:AlertingFeature:Alerting/RuleActionsIssues related to the Actions attached to Rules on the Alerting FrameworkR&DResearch and development ticket (not meant to produce code, but to make a decision)Team:ResponseOpsPlatform ResponseOps team (formerly the Cases and Alerting teams) t//discussestimate:needs-researchEstimated as too large and requires research to break down into workable issues

    Type

    No type

    Projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions