1. Data Virtualization Demoette… Logging in CIS
Hello, and welcome to the Demoette series for Cisco Information Server, or CIS.
In this Demoette, we provide an overview of the logging capabilities of CIS.

2. Agenda What is it and why does it matter? A basic demo Summary
Here is our agenda.
We begin by defining Logging and outlining its importance for our customers.
Next we walk through a very basic demo of Logging.
Finally, we summarize the contents of this demoette.

3. Agenda What is it and why does it matter? A basic demo Summary
Let’s begin by discussing what Logging is and why it is important for our customers.

4. What is it?
Logging
Comprehensive and highly configurable event logging
Event types include: Cache, Cluster, Data Source, Request, Resource, Security, Session, Storage, System Overview, Transaction, and Trigger
Event targets include: Database, File, SNMP, Custom
Event logging capabilities in CIS are comprehensive and highly configurable. Many different system events may be logged, but they fall into the following categories: Caching, Clustering, Data Sources, Requests, Resources, Security, Session, Storage, System Overview, Transaction, and Trigger events.
If an event is configured to be loggable, it may be logged to one or more of the following targets. First, it may be logged to the CIS repository database. Second, it may be logged in the CIS Event Monitor log file. Third, it may be logged as an SNMP trap. Finally, it may be logged to a user-written custom event handler. In this demoette, we will look at the first three targets. However, Custom Event Handlers are beyond the scope of this demoette.

5. Why does it matter? Logging Enterprise-grade system administration
Detailed information for Support issues
Logging is important to our customers for two reasons. First, it is a key component of enterprise-grade system administration. Second, it is a valuable source of detailed information that is useful in product Support scenarios.

6. Agenda What is it and why does it matter? A basic demo Summary
Next, let’s walk through a very basic demo of Logging.

7. Demo: Here is the business problem…
CIS
Here is the business problem we illustrate in this demo. CIS requests may be terminated, either manually or programmatically. This is sometimes done to cancel runaway queries, for example. In this demoette, our enterprise wants close monitoring of cancelled requests. Therefore, we will configure CIS to log Cancel events to its database and its log file. We will also configure CIS to create an SNMP trap for Cancel events.

8. Demo: Before you begin…
Import CAR file
Install and configure iReasoning MIB Browser
Load CIS MIB
Run Trap Receiver
This demo uses a stored procedure that executes an infinite loop, simulating a runaway query. It also uses several views of Log data. Before you begin the demo, import the CAR file containing these resources, which can be found in the Additional Resources folder that accompanies this demoette.
<CLICK> In order to show SNMP logging, you will need to install and configure the free MIB Browser from iReasoning. The download for this software includes detailed instructions. The first configuration step is to import the CIS Management Information Base, or MIB. It is named CompositeSoftware-MIB.mib, and is found in the CIS installation directory in the apps/server folder.
<CLICK> The second configuration step is to run the program’s Trap Receiver. Be sure it is set to listen to localhost on the default port. Make sure the iReasoning MIB Browser is running before you begin the demo.

9. Demo: Examine CIS Configuration
We are ready to begin our demo. First, let’s look at the various CIS configuration options that need to be set. From the Studio menu, click Administration, then Configuration.
<CLICK> Under Server/Events and Logging, make sure that the Enable System Events option is set to true. If this is false, no Server logging of any kind will be enabled.

10. Demo: Examine CIS Configuration
Next, let’s open the Logging folder. There are five logging mechanisms. Memory logging is used by CIS Manager. Custom logging is beyond the scope of this demoette. We’ll be taking a closer look at Database, File, and SNMP logging. The amount of data kept in Memory and Database logs is configurable, but generally speaking, Memory holds the least amount of data, Database holds more, and File Logger holds the most.
<CLICK> We open the SNMP folder and see that SNMP events are disabled by default. To create SNMP events, be sure to set this option to True.
<CLICK> Note that CIS publishes SNMP traps on the default port 162.

11. Demo: Examine CIS Configuration
Now let’s look at the specific events that can be generated for logging. As you can see, they fall into a number of categories.
<CLICK> Each event has default log settings, and most are set to log to database and log file. For this demoette, we are going to work with a specific data request event called Request Cancel.
<CLICK> We add SNMP to the list of log targets for this event. Now when a request is cancelled, it will be logged to the system database, the server event log file, and an SNMP trap will be generated.

12. Demo: Generate a Cancel Event
This demoette provides a resource named procInfiniteLoop, which simply runs an endless loop that opens and closes a cursor. Execute this procedure so that we have an example of a runaway query Request that can be cancelled in order to generate the Cancel event we are interested in.
<CLICK> Now open CIS Manager, and navigate to Monitoring | Requests.
<CLICK> Select the runaway request.
<CLICK> To be sure you are selecting the right Request, note that it has no parent ID…
<CLICK> … and the script itself is shown in the Summary column.
<CLICK> Cancel the Request.

13. Demo: Examine the SNMP Trap
Our iReasoning Trap Receiver shows the event. Double-click it and all the details of the trap will be shown.

14. Demo: Examine the Log File
Next, let’s take a look at the Server Events Log file. We could open the file with any text editor, but for this demoette, we have defined the log file as a flat-file CIS data source, with one column per line. We have built a simple View that selects all Cancel events from the log.

15. Demo: Examine the Log File
We have also built a simple parameterized query that will return ALL events related to a specific cancelled request. We enter the Request ID…
<CLICK> and the parameterized query returns the Start, Cancel, and Termination events for the Request.

16. Demo: Examine the System Database
Finally, let’s look at the Cancel event on the System Database. Events are held in a System Table named LOG_EVENTS. We built a View against this table which finds the Request ID and uses it to retrieve all events related to a cancelled Request.
Our demo is complete.

17. Agenda What is it and why does it matter? A basic demo Summary
Let’s summarize what we have seen in this presentation.

18. Summary Logging Comprehensive and highly configurable event logging
Event types include: Cache, Cluster, Data Source, Request, Resource, Security, Session, Storage, System Overview, Transaction, and Trigger
Event targets include: Database, File, SNMP, Custom
Enterprise-grade system administration
Detailed information for Support issues
Event logging capabilities in CIS are comprehensive and highly configurable. Many different system events may be logged, but they fall into the following categories: Caching, Clustering, Data Sources, Requests, Resources, Security, Session, Storage, System Overview, Transaction, and Trigger events.
If an event is configured to be loggable, it may be logged to one or more of the following targets. First, it may be logged to the CIS repository database. Second, it may be logged in the CIS Event Monitor log file. Third, it may be logged as an SNMP trap. Finally, it may be logged to a user-written custom event handler.
Logging is important to our customers for two reasons. First, it is an important component of enterprise-grade system administration. Second, it is a valuable source of detailed information that is useful in product Support scenarios.
Thank you.

19. TOMORROW starts here.