![]() List of application ids to use for aggregating host level metrics for an application.Įxample: bytes_read across Yarn Nodemanagers. JDBC resultset prefect size for aggregator queries. Time in seconds to sleep on the first run or when the checkpoint is too old. Calculated as follows:Ĥ aggregate metrics/min * 60 * 24: Retrieve aggregate data for 1 day. Max result limit on number of rows returned. This can be changed only before creating tables. schemeĬompression codes need to be installed and available before setting the scheme.ĭefault compression is SNAPPY. block.encodingĬodecs are enabled on a table by setting the DATA_BLOCK_ENCODING property.ĭefault encoding is FAST_DIFF. Lowest resolution of desired data for cluster level minute aggregates. *.disabledĭisable host based * aggregations. The multiplier is configurable for each aggregator. After reading last run time, the aggregator thread decides to aggregate as long as the (currentTime - lastRunTime) < multipler * aggregation_interval. The aggregators store the timestamp or last run time on local FS. Time in seconds to sleep for the day resolution cluster wide aggregator. Time in seconds to sleep for the hourly resolution cluster wide aggregator. Time in seconds to sleep for the minute resolution cluster wide aggregator. Time in seconds to sleep for the day resolution host based aggregator. Time in seconds to sleep for the hourly resolution host based aggregator. Time in seconds to sleep for the minute resolution host based aggregator. Instance B is completed and persisted in the BAM primary import database at 1:04 a.m. For example, instance A is completed and persisted in the BAM primary import database at 1:02 a.m. To send the data every 30 seconds, simply add -i 30 while starting the Logentries Docker container. For example, the aforementioned query would deliver a chart with the results seen below. On wake up the aggregator threads resume from (last run time + interval) as long as last run time is not too old. The TimeSlice property uses time that the data is written to the BAM primary import database to group BAM instance data. timeslice() is particularly useful in revealing previously hidden trends by enabling you to analyze your data with increased granularity. Modifying the aggregation intervals for HOST and CLUSTER aggregators. Note: The precision table at 1 minute resolution stores raw precision data for 1 day, when user queries for past 1 hour of data, the AMS API returns raw precision data. ![]() ![]() daily.ttlĬluster wide daily resolution data purge interval. hourly.ttlĬluster wide hourly resolution data purge interval. minute.ttlĬluster wide minute resolution data purge interval. Host based daily resolution data purge interval. Host based hourly resolution data purge interval. (X = configurable interval, default interval is 2 minutes) Host based X minutes resolution data purge interval.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |