The document outlines the agenda for a MuleSoft meetup on logging and monitoring. The agenda includes introductions, a technical session on Anypoint Logging and Monitoring, a break for tea and coffee, a Q&A session, and plans for the next meetup. Key points covered are how Mule ESB uses logging strategies and log4j2, customizing log locations, metrics tracked in Anypoint Monitoring including API invocations and implementations, alerts for policies and thresholds, and suggestions for future meetups.

1. 7th SEP,2019: Logging and Monitoring
Hyderabad MuleSoft Meetup

2. All contents © MuleSoft Inc.
Agenda
2
• 2:30 PM Introduction
• 3:00 PM Technical Session
• 4:30 PM Tea, Coffee and Snacks break
• 5:00 PM Q & A
• 5:45 PM Plan for Next Meetup

3. All contents © MuleSoft Inc.
Agenda
3
• Introductions

4. All contents © MuleSoft Inc.
Introduction : Organizer, Speaker and You
4
Santosh Ojha Srilatha Kante
A SHOW OF HANDS:
Who is new to this Meetup?

5. With Anypoint Logging and Monitoring
What’s New

6. All contents © MuleSoft Inc.
Anypoint Logging
6
• Mule ESB uses slf4j, It uses Logging Strategies to pull and discover
the logs from the classpath
– log4j2
– JDK Logger
• By Default Mule includes log4j2, which is configured with a file
called log4j2.xml.
• For any Changes we can configure log4j2 in our application.

7. All contents © MuleSoft Inc.
Where to find?
7

8. All contents © MuleSoft Inc.
Customizing the log location
8

9. All contents © MuleSoft Inc.
Anypoint Monitoring
9
• Module based on API Manager, Analytics, Runtime Manager
• New product: Anypoint Monitoring
– Older products and features remain available
– Module to be updated
• Larger set of metrics for API invocations, API implementations
(Mule applications) and Mule runtimes
– Inbound, outbound, performance, failures, JVM, infrastructure
– Averages, percentiles, ...
• Built-in and custom dashboards and charts
• Graphs can automatically refresh
• Highly configurable time-series graphs, histograms, etc.

10. All contents © MuleSoft Inc.
More Interesting points about Monitoring
10
• Visualization of summary statistics of a single metric
• Auto-color-coded tables summarizing time-series data
• Metrics for chart selected using (SQL-like) query builder
• Alerts based on metrics in charts
– Augment API Manager and Runtime Manager alerts
• Log and event aggregation and search across Mule
• applications in the entire application network
• Data storage and retention depend on subscription level
• Stores data in configurable regions
– Not in region of the Anypoint Platform control plane
• Selected Mule runtime versions on CloudHub

11. All contents © MuleSoft Inc. 11

12. All contents © MuleSoft Inc.
API Invocations
12
• Number of API invocations (requests)
– Successful: [100, 400)
– Unsuccessful due to a client error: [400, 500)
– Unsuccessful due to a server error: [500, 600)
• Mean response time (average latency)
• Request and response payload size
• Properties of the API client:
– Client ID (if registered), geographical location, OS platform, ...
• Properties of the API invocation:
– resource path, HTTP method, ...
• Metrics can be grouped and displayed along various dimensions:
– for one/all API(s) and one/all API client(s)
– custom

13. All contents © MuleSoft Inc.
Alerts in Anypoint Platform
13
• Alerts based on these metrics of API invocations:
– Number of violations of a given policy
– Request count (number of API invocations)
– Response code in given set of HTTP response status codes
– Response time exceeding given threshold in milliseconds
• ● Alert is triggered when the metric
– Falls above/below a threshold
– For a given number of time periods of a given duration
• ● C4E guideline: alerts should at least cover:
– All violations of API policies
– All violations of QoS guarantees not explicitly captured in API policies

14. All contents © MuleSoft Inc.
Alerts for Policy Options
14
• SLA tier exhausted:
– Violation of SLA-based Rate Limiting, severity Info, > 60 violations for at
– least 3 consecutive 10-minute periods
– Alerts when approx. 10% of 1-second intervals are above limit defined
– by SLA tier
– Also alerts on invalid client ID/secret supplied
• ● Client not in Process API subnet:
– Violation of IP whitelist, severity Critical, > 1 violation for at least 3
• consecutive 1-minute periods
– Could add alert for violations of Spike Control

15. All contents © MuleSoft Inc.
Alert for API implementation
15
• Alerts for API invocations and API implementations
complement each other
• If API implementation crashes but no API client invokes that API
then no alert on the level of API invocations will be raised
– But remember auto-restart
• Consistently high CPU usage
• Deployment failures in production and staging environments

16. All contents © MuleSoft Inc.
What’s next
16
• Share:
– Invite your network to join: https://meetups.mulesoft.com/Hyderabad/
• Feedback:
– Contact your organizer Santosh B Ojha to suggest topics
– Contact MuleSoft at meetup@mulesoft.com for ways to improve the program
– Your Feedback is Food for us
• Our next meetup:
– Date: TBD
– Location: TBD
– Topic: TBD

17. All contents © MuleSoft Inc.
Take a stand !
17
• Nominate yourself for
the next meetup speaker
and suggest a topic as
well.

18. See you next time
Please send topic suggestions to the organizer