Is your feature request related to a problem? Please describe.
I have a large number of environments which require individual acembot deployments and to monitor failures/renewals, I have configured a webhook across all the deployments that point to the same endpoint. This is all working as expected but due to the large number of deployments, the payload details are lacking in detail to quickly pinpoint which acmebot is in question.
Describe the solution you'd like
Ideally, I would like to include the name of the function resource as well as the key vault name.
Describe alternatives you've considered
I initially attempted to parse the log analytics logs via an azure automation runbook before I realized acmebot had a builtin webhook function.
Is your feature request related to a problem? Please describe.
I have a large number of environments which require individual acembot deployments and to monitor failures/renewals, I have configured a webhook across all the deployments that point to the same endpoint. This is all working as expected but due to the large number of deployments, the payload details are lacking in detail to quickly pinpoint which acmebot is in question.
Describe the solution you'd like
Ideally, I would like to include the name of the function resource as well as the key vault name.
Describe alternatives you've considered
I initially attempted to parse the log analytics logs via an azure automation runbook before I realized acmebot had a builtin webhook function.