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
Is your feature request related to a known monitoring hole? Please describe.
Signalfx provide lot of useful internal metrics which could be used to monitor signalfx health itself.
Describe the solution you'd like
Signalfx could abort detector evaluation if there are too many timeseries, we need to detect this.
also there are the number of aws api call for integration.
Additional context
sf.org.numDetectorsAborted - this counter-type metric increments when a detector aborts with over 250,000 MTS
sf.org.abortedDetectors - this event helps you track down the large detector
sf.org.numLimitedMetricTimeSeriesCreateCalls - increase when reach a limit and metrics are dropped (could be also monitored with sf.org.numDatapointsDropped)
The text was updated successfully, but these errors were encountered:
Is your feature request related to a known monitoring hole? Please describe.
Signalfx provide lot of useful internal metrics which could be used to monitor signalfx health itself.
Describe the solution you'd like
Signalfx could abort detector evaluation if there are too many timeseries, we need to detect this.
also there are the number of aws api call for integration.
Additional context
sf.org.numDetectorsAborted - this counter-type metric increments when a detector aborts with over 250,000 MTS
sf.org.abortedDetectors - this event helps you track down the large detector
sf.org.numLimitedMetricTimeSeriesCreateCalls - increase when reach a limit and metrics are dropped (could be also monitored with sf.org.numDatapointsDropped)
The text was updated successfully, but these errors were encountered: