![]() ![]() Nobl9 agent for Sumo Logic has a 2-minute query interval. Sumo Logic allows for total of 240 requests per minute to its APIs combined. Contact Sumo Logic customer support to increase your rate limits and prevent conflicts.Keep the number of Sumo Logic Logs objectives in check with your API limits (see Number of Objectives Supported).This does not apply to Directs, having multiple of them doesn't impact rate limiting orchestration. If you're using the Nobl9 Agent for Sumo Logic, stick to a single Agent as your data source (this will allow Nobl9 to orchestrate querying Sumo Logic API).Logs queries should take at most 2 minutes (using Sumo Logic partitions and Sumo Logic scheduled views will help a lot).Logs are at least 4 times more expensive than metrics (see how to convert your logs to metrics) Prefer metrics queries over logs queries.To prevent Sumo Logic Rate Limits issues: The Nobl9 Agent distributes the required requests within the two-minute interval to reduce the number of requests per second. The Nobl9 Agent requests several endpoints to gather data points according to the Process Flow described in the documentation. Sumo Logic's Search Job API requests are rate limited (see Rate limit throttling | Sumo Logic Documentation). The query's Time range is set from the beginning and end of the 2-minute-time window being queried. The maximum resolution of the response must be 4 data points. Nobl9 queries Sumo Logic leveraging the Search Job API or Metrics Query API every 2 minutes with a query delay of 4 minutes. SLOs using Sumo Logic - YAML samples Sumo Logic SLOs - Metrics įor the full specification for building Sumo Logic query, refer to the official documentation. Total query for the Ratio Metric (Logs type):.Good query for the Ratio Metric (Logs type):.The query must contain the keyword timeslice: Total query for the Ratio Metric (Metrics type):įollow the instructions below to create Sumo Logic Ratio metric using Logs type:.Good query for the Ratio Metric (Metrics type):.For the Incremental method, we expect the value of a metric to be the current sum of some numerator.įor more information, refer to the SLO Calculations Guide.For the Non-incremental method, we expect it to be the components of the sum.| if (status_code matches "20*" or status_code matches "30*",1,0) as resp_okįollow the instructions below to create Sumo Logic Ratio metric using Metrics type: | parse "HTTP/1.1\" * * *" as (status_code, size, tail) Sample query for Sumo Logic Threshold metric:.The Query must contain the keyword timeslice.You can also select Alert Policies and Labels on this screen.įollow the instructions below to create Sumo Logic Threshold metric using Logs type: In step 5, add a Name, Description, and other details about your SLO.In step 4, specify the Error Budget Calculation Method and your Objective(s).In step 3, define a Time Window for the SLO.Sample query for Sumo Logic Threshold metric (Metrics type): metric=CPU_usage.Select one of the following values: avg, sum, min, max, count, none.Rollup is an aggregation function Sumo Logic uses when quantizing metrics. For more details, refer to the Sumo Logic documentation.In Sumo Logic, quantization is the process of aggregating metric data points for time series over an interval of time.Select value and units for Quantization.In step 2, select Sumo Logic as the Data Source for your SLO, then specify the Metric.In step 1 of the SLO wizard, select the Service the SLO will be associated with.# If you don’t want the metrics to be exposed, comment out or delete the N9_METRICS_PORT variable.įollow the instructions below to create Sumo Logic Threshold metric using Metrics type: # The 9090 is the default value and can be changed. # The N9_METRICS_PORT is a variable specifying the port to which the /metrics and /health endpoints are exposed. Name : nobl9 - agent - myorg - myproject - sumologicagent # It is not a ready-to-apply k8s deployment description, and the client_id and client_secret are only exemplary values. # DISCLAIMER: This deployment description contains only the fields necessary for the purpose of this demo. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |