Re: [Hawkular-dev] Tag concept in metrics and alerts

----- Original Message ----- > > Subject: Re: [Hawkular-dev] Tag concept in metrics and alerts > > > > Hi Lucas > > > > Not sure the alert or definition will be appropriate - assuming that the > > definition is a static representation of the trigger? > > > > The information (business transaction id) I am referring to is per > > business > > transaction instance - i.e. it is unique for each invocation of a > > business > > transaction. So this can only be obtained from the information being > > evaluated by the trigger. > > > > Let me know if I have misunderstand what you meant as definition. > > > > No, I think you were right. > > Then the BT id is mapped into the data being processed by the engine. > > So, then I guess that BT id should be mapped just in the data that alerts > use > as input for processing. > > The Alert model stores this info by default. Each alert has a list of the > evaluations (conditions definitions + specific data responsible of the > trigger). > > Then perhaps I understand that you need to code the BT info into the > incoming > data, right ? Yes that is correct. So just to check - if I include the BT id in the metric being supplied to the engine, then the 'tag' (name/value pairs) information for that metric will be carried into alert as part of the evaluation information?

Regards Gary