#Sumo logic sum count timeslice how to
Learn how to see all metrics available to you. KeyTransactionName, transactionName, transactionTypeĪpm.Įxternal call response time by transaction type Response time for external calls broken out by external host name Response time for database calls broken out by table operations Here are how the original APM metric timeslice metrics are converted into dimensional metrics: If you don't see a metric you're looking for in this section, see Generic queries. The conversion of original APM metric timeslice metrics into dimensional metrics that are available for querying is an ongoing process and isn't complete. This optional clause displays the results in a time-based chart.įor general information on NRQL syntax, including FROM, FACET, and TIMESERIES, see Intro to NRQL.įor more queries, see Query examples. Sets the transaction type to web, meaning that background/non-web transactions won't be counted. This query uses entity.guid, but you can also use appId or appName. You can select a single entity's GUID, as shown here, or you can select multiple sources. You must specify at least one data source. Note that you can use other aggregator functions. This query uses the converted metric names. This math generates a count of errors out of a total count of transaction metrics. For general tips on querying Metric data, see Metric query examples. Metric is one of our core data types, and metric timeslice data is stored as this data type.
0 kommentar(er)
