You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 13, 2020. It is now read-only.
Add the possibility of using Application Insights or other APM to record liveness information events and metrics.
This would allow the possibility of having and history of liveness information, like which are unreliable services, as well as metrics for any pulse milliseconds ellapsed.
This should be added dynamically and support from zero to n trackers.
The text was updated successfully, but these errors were encountered:
Can you explain more "allow the possibility of having and history of liveness information". This tracker track de "service availability" or metrics like "liveness excution time" etc?
With the Application Insights Tracker, you can check whole history of all BeatPulse calls and it's result, making it so easy to have historical information of it, via Application Insights events information:
Also, adding the milliseconds info taken from BeatPulse, and adding it to the event information, we can have custom metrics on which "pulses" are taking more time, also with history info, via metrics on Application Insights:
The whole point of this also, is to add a new extensibility point, which allows developers to create and add his own trackers for other APM like New Relic, to be able to use this info with the whole monitoring info from their own applications.
Add the possibility of using Application Insights or other APM to record liveness information events and metrics.
This would allow the possibility of having and history of liveness information, like which are unreliable services, as well as metrics for any pulse milliseconds ellapsed.
This should be added dynamically and support from zero to n trackers.
The text was updated successfully, but these errors were encountered: