A metric is a quantifiable measurement whose values are monitored by Metricly and used to assess the performance of an element. Metrics are always associated with one or more elements.
Examples of metrics:
Metricly has collected metrics for every element in the application. Policies can be created using collected metrics to determine if data is missing through alerts, and further configured to fire notifications. After 15 minutes of missing data, the element suspends and the alert stops. At this point, an external event is posted to the event timeline noting that Metricly has not received data.
Example
| Fully Qualified Name(FQN) | Description | Units | BASE | CORR | UTIL |
|---|---|---|---|---|---|
| netuitive.metrics.collected.percent | % of metrics that collected data in the last interval.Computation:((# of collected metrics) / (total # of metrics) * 100) | Percent | yes | no | no |
Computed metrics are metrics that Metricly calculates using the data from multiple metrics collected on a integration. Computed metrics are used to compile utilization reports of your environment and to specify metric behavior in default policies. A metric can be identified as a computed metric if its name begins with “netuitive.”
Example
| FULLY QUALIFIED NAME (FQN) | DESCRIPTION | UNITS | BASE |
|---|---|---|---|
| netuitive.aws.alb.totaltargethttperrors | Total Target HTTP Errors | count | yes |