Architecting Integrations for Observability.pdf
- 1. Architecting Integrations for Observability Manik Magar, Senior Architect, AVIO Consulting
- 2. Forward Looking Statements This presentation contains forward-looking statements about, among other things, trend analyses and future events, future financial performance, anticipated growth, industry prospects, environmental, social and governance goals, and the anticipated benefits of acquired companies. The achievement or success of the matters covered by such forward-looking statements involves risks, uncertainties and assumptions. If any such risks or uncertainties materialize or if any of the assumptions prove incorrect, Salesforce’s results could differ materially from the results expressed or implied by these forward-looking statements. The risks and uncertainties referred to above include those factors discussed in Salesforce’s reports filed from time to time with the Securities and Exchange Commission, including, but not limited to: the impact of, and actions we may take in response to, the COVID-19 pandemic, related public health measures and resulting economic downturn and market volatility; our ability to maintain security levels and service performance meeting the expectations of our customers, and the resources and costs required to avoid unanticipated downtime and prevent, detect and remediate performance degradation and security breaches; the expenses associated with our data centers and third-party infrastructure providers; our ability to secure additional data center capacity; our reliance on third-party hardware, software and platform providers; the effect of evolving domestic and foreign government regulations, including those related to the provision of services on the Internet, those related to accessing the Internet, and those addressing data privacy, cross-border data transfers and import and export controls; current and potential litigation involving us or our industry, including litigation involving acquired entities such as Tableau Software, Inc. and Slack Technologies, Inc., and the resolution or settlement thereof; regulatory developments and regulatory investigations involving us or affecting our industry; our ability to successfully introduce new services and product features, including any efforts to expand our services; the success of our strategy of acquiring or making investments in complementary businesses, joint ventures, services, technologies and intellectual property rights; our ability to complete, on a timely basis or at all, announced transactions; our ability to realize the benefits from acquisitions, strategic partnerships, joint ventures and investments, including our July 2021 acquisition of Slack Technologies, Inc., and successfully integrate acquired businesses and technologies; our ability to compete in the markets in which we participate; the success of our business strategy and our plan to build our business, including our strategy to be a leading provider of enterprise cloud computing applications and platforms; our ability to execute our business plans; our ability to continue to grow unearned revenue and remaining performance obligation; the pace of change and innovation in enterprise cloud computing services; the seasonal nature of our sales cycles; our ability to limit customer attrition and costs related to those efforts; the success of our international expansion strategy; the demands on our personnel and infrastructure resulting from significant growth in our customer base and operations, including as a result of acquisitions; our ability to preserve our workplace culture, including as a result of our decisions regarding our current and future office environments or work-from-home policies; our dependency on the development and maintenance of the infrastructure of the Internet; our real estate and office facilities strategy and related costs and uncertainties; fluctuations in, and our ability to predict, our operating results and cash flows; the variability in our results arising from the accounting for term license revenue products; the performance and fair value of our investments in complementary businesses through our strategic investment portfolio; the impact of future gains or losses from our strategic investment portfolio, including gains or losses from overall market conditions that may affect the publicly traded companies within our strategic investment portfolio; our ability to protect our intellectual property rights; our ability to develop our brands; the impact of foreign currency exchange rate and interest rate fluctuations on our results; the valuation of our deferred tax assets and the release of related valuation allowances; the potential availability of additional tax assets in the future; the impact of new accounting pronouncements and tax laws; uncertainties affecting our ability to estimate our tax rate; uncertainties regarding our tax obligations in connection with potential jurisdictional transfers of intellectual property, including the tax rate, the timing of the transfer and the value of such transferred intellectual property; uncertainties regarding the effect of general economic and market conditions; the impact of geopolitical events; uncertainties regarding the impact of expensing stock options and other equity awards; the sufficiency of our capital resources; our ability to comply with our debt covenants and lease obligations; and the impact of climate change, natural disasters and actual or threatened public health emergencies, including the ongoing COVID-19 pandemic.
- 3. Manik Magar Senior Architect, AVIO Consulting MuleSoft Ambassador and Meetup Leader ManikMagar https://manik.magar.me
- 4. Agenda ● The Story - The Digital Transformation of a Retail Store ○ API-led ○ The Downtime ● Observability Pillars ○ Logs ○ Metrics ○ Traces ○ Synthetic Monitoring ● Design for Observability ● Q&A
- 5. Develop new APIs Create new integration APIs to support digitization of user experience. The Story Digital transformation of a Retail store Re-use legacy APIs Take a phased approach. Some legacy APIs are re-used for the initial phases. Migrate legacy APIs Few critical APIs are migrated to the new platform.
- 6. API-led Approach New API New API Migrated API(s) Legacy API
- 7. One fine evening … systems started to fall apart
- 8. Revenue 53% of the IT leaders said downtime results in lost revenue. Downtime Disrupts Business Productivity 47% of the IT leaders tied loss in productivity to the downtime. Brand Value 41% of the IT leaders agreed to the loss of brand equity or trust happens due to the downtime. Source: Forrester Report “The Real Costs of Planned and Unplanned Downtime” https://www.ibm.com/downloads/cas/L57KW7ND
- 9. Debugging Incidents Monitoring and Metrics based ● Reactive Debugging approach ● Metrics and Alerts are based on system state assumptions ● Requires predefined setup for known error conditions Observable Systems ● Predictive debugging approach ● Capturing multiple data dimensions ● Ask questions about system states and investigate based on captured data ● Understand and explain system states without shipping new code
- 10. Observability is a measure of how well internal states of a system can be inferred from knowledge of its external outputs. *https://en.wikipedia.org/wiki/Observability
- 11. Observability Pillars - Logs ● A log is an immutable and timestamped record of a system event. ● Structured logs enable enhanced machine processing, aggregation, reporting and alerting. ● Open source option for structured logging in Mule - https://github.com/avioconsulting/ mule-custom-logger Log using mule-custom-logger:
- 12. Observability Pillars - Logs Mule Custom Logger See https://github.com/avioconsulting/mule-custom-logger#using-the-custom-logger-processor
- 13. https://docs.mulesoft.com/monitoring/ Observability Pillars - Metrics ● A metric is a single numeric value, optionally with tags appended for grouping and searching. ● Metrics are often aggregated over a period of time and visualized using dashboards. ● Metrics can be used to trigger alerts when certain thresholds are met. ● Anypoint Monitoring and Runtime Manager supports capturing metrics, reporting dashboards as well as alerts. Anypoint Monitoring Dashboards
- 14. Observability Pillars - Traces ● A trace is a representation of interrelated distributed events that describes the end-to-end request flow through a distributed system. ● Traces helps understand interdependencies of services. ● Traces can capture data attributes related to request, service, and environment. Trace Visualization Example
- 15. OpenTelemetry is a set of APIs, SDKs, tooling and integrations that are designed for the creation and management of telemetry data such as traces, metrics, and logs. https://opentelemetry.io/docs
- 16. AVIO’s OpenTelemetry Module for MuleSo ● AVIO-developed, custom module for Mule applications ● Compliant with OpenTelemetry semantic attribute conventions ● Supports OTLP and other exporters ● Trace context propagation for distributed transactions ● Includes CloudHub aware Mule resource provider ● Open source - https://github.com/avioconsulting/mule-opentelemetry-module
- 17. Observability Pillars - Synthetic Monitoring ● Synthetic monitoring tracks the availability and health of required services and endpoints. ● It can generate alerts when services are either unhealthy or down. Uptime Monitoring
- 18. Preparing for Observability Design ● Log Aggregation Tool ● Metrics ● Dashboards ● Tracing Questions to Ask
- 19. See https://www.avioconsulting.com/observability AVIO’s Observability Approach AVIO’s Observability Package for MuleSoft makes it easy to evaluate and take action on your logs, key metrics, and health stats. By utilizing OpenTelemetry traces, AVIO enables you to see complete end-to-end traces of all your MuleSoft applications.
- 21. When the system fails... Trace Logs
- 22. Thank you