[et_pb_section fb_built=”1″ admin_label=”section” _builder_version=”4.16″ global_colors_info=”{}”][et_pb_row admin_label=”row” _builder_version=”4.16″ background_size=”initial” background_position=”top_left” background_repeat=”repeat” global_colors_info=”{}”][et_pb_column type=”4_4″ _builder_version=”4.16″ custom_padding=”|||” global_colors_info=”{}” custom_padding__hover=”|||”][et_pb_text _builder_version=”4.21.0″ _module_preset=”default” global_colors_info=”{}”]This is part 2 of the 3 part series \u201cThe path to your first SLO\u201d.<\/em><\/p>\n

When you have a clear understanding of what metrics to gather for SLO, the next question is how to obtain and gather those metrics. Basically the metrics can be obtained by the following methods.<\/p>\n

Metrics from commercial APM\/ Observability tools,<\/u>
\nCommercial monitoring tools offer one stop shop to gather infrastructure metrics from machine agents, cluster agents or in terms of public cloud platforms, those will be metrics from AWS CloudWatch or Azure Monitor. For application metrics, usually the same APM agent can generate application specific metrics derived from logs or traces. Usually these contribute to the 4 golden signals we discussed in the previous post.<\/a>
\nYou can now build dashboards directly from the commercial APM tools to utilize those metrics. Metrics can also be retrieved through APIs for external consumption.<\/p>\n

Metrics from siloed data sources<\/u>
\nThey are usually from systems in your organization that have no full featured APM tools in place. Today it is common for applications to expose Prometheus compatible metrics ( a de facto standard to allow metrics to be scrapped for monitoring by Prometheus ) to fulfill simple monitoring use cases. Grafana then fills the gap on time series visualization and alerting.<\/p>\n

Metrics from E2E testing and synthetic tools<\/u>
\nSynthetic testing tools can provide valuable insight on service availability, response time and customer experience. These metrics can also be a source of SLO. Commercial solutions include ThousandEyes and SolarWinds PingDom.<\/p>\n

If you have multiple monitoring tools it is wise to consolidate all these metrics into a single dashboard for alerting and visualization. Examples are Grafana and Nobl9 which can help to
\nConsolidate metrics from multiple tools into a single dashboard.
\nOffers pre-built SLO dashboards or flexibility to easily build SLO dashboards
\nAs a summary, the goal is to streamline the process of obtaining the metrics from multiple systems and quickly realize the benefits of SLO tracking. In the next article, we will look at a real example of utilizing Nobl9 for a simple service availability SLO.<\/p>\n

New to SLO?
\n#SLOconf<\/a> is a free, virtual event focused on #SLOs!<\/a> \ud83d\udd25
\nWhether you are doing SRE, SLO, or DevOps, or Ops, or a Dev – SLOconf is the perfect platform to share insights and ideas on the latest trends and developments in SRE\/SLO.
\nVsceptre is a sponsor at SLOconf<\/a> 2023, hosted by Nobl9!<\/a> \ud83d\udce2
\nFor more details & speaker lineup, register here: \ud83d\udc47
\nwww.sloconf.com<\/a>
\n[\/et_pb_text][\/et_pb_column][\/et_pb_row][\/et_pb_section]<\/p>\n","protected":false},"excerpt":{"rendered":"

This is part 2 of the 3 part series \u201cThe path to your first SLO\u201d.
\nWhen you have a clear understanding of what metrics to gather for SLO, the next question is how to obtain and gather those metrics. Basically the metrics can be obtained by the following methods.<\/p>\n","protected":false},"author":1,"featured_media":10720,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_et_pb_use_builder":"on","_et_pb_old_content":"","_et_gb_content_width":"","inline_featured_image":false,"footnotes":""},"categories":[122,93],"tags":[],"class_list":["post-9479","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-blog-cn","category-news-cn"],"acf":[],"yoast_head":"\n