Monitoring WebLogic with WLDF

Transcription

1 Monitoring WebLogic with WLDF Infrastructure at your Service.

2 Infrastructure at your Service. About me Gérard Wisson Delivery Manager Senior Consultant Mobile Page 2

3 Who we are dbi services Experts At Your Service > 30 specialists in IT infrastructure > Certified, experienced, passionate Based In Switzerland > 100% self-financed Swiss company > More than CHF 3 mio. in sales Leading In Infrastructure Services > Over 70 customers in CH, D, & F > 30 SLAs dbi FlexService signed Page 3

4 Agenda 1. Concept 2. Configuration 3. Data Access 4. Demo Page 4

5 Concept Using WLDF diagnostic data can be > Created > Collected > Analyzed > Archived > Accessed Page 5

6 Concept Diagram Used at application and server level - creates monitors - Inserts monitors in the execution flow generate Instrumentation diagnostic Data Creator gathers the most common sources of the key server state can be made available to support technicians consumes Data from Creators monitors publish&data Watch directly to the Archive Notification synchronously generate Data Collector events. (i.e logs) Data Publisher Logger Data provider Harvester events and harvested metrics can be persisted Image Capture On-demand capture with Console,WLST, JMX app automated monitors to observe specific diagnostic states send notifications based on configured rules watch rule to monitor: Accessor - log data - event data - metric data Monitoring Dashboard includes a predefined set of builtin views sampling at regular intervals to harvest current values Archive Accessing Diagnostic Data Accessing Diagnostic Data displays the current and historical operating state made available for historical review In response to the triggering of an associated Harvester watch, Log watch, or Instrumentation watch rule Page 8

7 Agenda 1. Concept 2. Configuration 3. Data Access 4. Demo Page 9

8 General Use configuration Mbeans Persisted in XML configuration files Tools to configure WLDF > Administration Console > WLST > JMX > Edit XML Page 10

9 Diagnostic System Modules Contains the configurations for the module > Instrumentation > Harvester > Watch and Notification Targeting to servers and clusters > zero, one, or more > only one module targeted to it at a time > No need to restart the server instance Resource descriptor referred in config.xml > DOMAIN_NAME\config\diagnostics\"name of the diagnostic module".xml > ARCHIVE_PATH/META-INF/weblogic-diagnostics.xml Page 11

10 Diagnostic System Modules Config.xml excerpt Page 12

11 Diagnostic Images Configuring and Capturing Diagnostic Images > Primarily as a post-failure analysis tool > Little control over what information is captured Configure > Destination for the image > Lockout, period: control how often an image is taken during a sequence of server failures and recoveries > WLDF diagnostics volume (for Flight Recorder) Page 13

12 Diagnostic Images Content of the Captured Image File > Configuration > Log cache state > Java Virtual Machine (JVM) > Work Manager state > JNDI state > Most recent harvested data Page 14

13 Diagnostic Archives Configuring Diagnostic Archives > File-Based Store > default directory is DOMAIN_NAME/servers/SERVER_NAME/data/store/diagnostics > JDBC-Based Store > wls_events and wls_hvst tables must exist > JDBC must be configured to connect to that database > Retiring Data from the Archives > periodically deleting old diagnostic data from the archives > size-based > age-based > log files managed by log rotation feature Page 15

14 Diagnostic Archives Config.xml excerpt Page 16

15 Harvester > Configuring the Harvester for Metric Collection Configured entity A type (only) An attribute of a type (type + attribute(s)) An instance of a type (type + instance(s)) An attribute of an instance of a type (type + instance(s) + attribute(s)) Data collected from All harvestable attributes in all instances of the specified type The specified attribute in all instances of the specified type All harvestable attributes in the specified instance of the specified type The specified attribute in the specified instance of the specified type Page 17

16 Harvester Configure: > Harvester Sampling Period (in ms) > Types of Data to harvest > ServerRuntimeMBean > DomainRuntime (use it only for DomainRuntime specific MBeans) Page 18

17 Harvester diagnostics/module xml excerpt Page 19

18 Watches Situation to trap for monitoring or diagnostic purposes > Analyze > log records > data events > harvested metrics > Watch rule > watch rule expression > an alarm setting > one or more notification handlers Page 20

19 Watches Types of Watches > Harvester > Log > Instrumentation (or Event Data) Options Shared by All Types of Watches > rule expression > notifications associated with the watch > alarm options > trigger repeatedly > trigger once > AutomaticReset > ManualReset Watch can be associated with multiple notifications Page 21

20 Watches diagnostics/module xml Page 22

21 Notification Action that is taken when a watch rule expression evaluates to true Types of notifications: > Java Management Extensions (JMX) > Java Message Service (JMS) > Simple Mail Transfer Protocol (SMTP) > Simple Network Management Protocol (SNMP) > Diagnostic Images Severity options > passed through to the recipients of notifications Enabled Notification can be associated with multiple watches Page 23

22 Notification diagnostics/module xml excerpt Page 24

23 Notification Configure JMS, JMX, SMTP, SNMP modules Use the modules Page 25

24 Instrumentation Add diagnostic code to WebLogic Server instances and the applications running on them Key features > Diagnostic monitors > scope: > system: DOMAIN_NAME/config/diagnostics/"module".xml > application: ARCHIVE_PATH/META-INF/weblogic-diagnostics.xml > type > standard (DyeInjection) > delegating > custom Page 26

25 Instrumentation Diagnostic actions > DisplayArgumentsAction > MethodInvocationStatisticsAction > MethodMemoryAllocationStatisticsAction > StackDumpAction > ThreadDumpAction > TraceAction > TraceElapsedTimeAction > TraceMemoryAllocationAction Diagnostic context > Monitors: (before, after, around) > Flags: (ADDR, USER, COOKIE ) Page 27

26 DomainMBean ServerMBean WLDFServerDiagnosticMBean WLDFSystemResourceMBean WLDFResourceBean WLDFHarvesterBean WLDFInstrumentationBean WLDFWatchNotificationBean Page 28

27 Agenda 1. Concept 2. Configuration 3. Data Access 4. Demo Page 29

28 Access Data Data Accessor Captured information (per-server basis) is segregated into logical data store > HTTP_LOG > HARVESTED_DATA_ARCHIVE > EVENTS_DATA_ARCHIVE > SERVER_LOG > etc. Accessing Diagnostic Data Online > Administration console (for logfiles) > JMX APIs > WebLogic Scripting Tool (WLST) > SSL connection in Prod mode Page 30

29 Access Data Example Example 1: all information Page 31

30 Access Data Example Example 2: with end time (excluded) Page 32

31 Agenda 1. Concept 2. Configuration 3. Data Access 4. Demo Page 33

32 Infrastructure at your Service. Any questions? Please do ask. Gérard Wisson Delivery Manager Senior Consultant Mobile We look forward to working with you! Page 34