EDM provides the ability to create views for displaying lists of objects in the UI. By creating views you can select the columns that will be displayed, and also specify filtering characteristics (conditions) for the items to be displayed or excluded from the display. EDM 3.3 includes the ability to create sub-views, to further classify the items that you want to display.
Alerting is one of the core capabilities of EDM, providing a collection of thresholds that are evaluated by EDM for each incoming data block, and defining the actions to be taken (email notifications, run external application, etc) for each of them in case a metric’s value violates the parameters of the configured alert.
EDM gives managers a quick way of viewing the efficiency of the IT operations team by providing the Average Alert Duration on the Triggered Alerts tab. This is calculated by view so it can be displayed for the entire IT organization, at the service level, application level or system level.
Notice the Acknowledged and Assigned User columns on the right of the Triggered Alerts display. Alerts can be acknowledged by individual users, who then take ownership of the issue for investigation and resolution. Check the Display Acknowledged box to list the alerts that have been claimed. You can make notes directly into the alert record, so that results can be documented for future reference; click the note icon to view notes and make updates.
Alerts are grouped into Alert Groups; each Alert Group contains a set of configured alerts that can be assigned to one or more connections. How do you know whether an Alert Group has been assigned to a connection? In EDM, you can display this information by selecting the server icon in the Alert Groups display. This seems like a simple thing, but it can be a real time-saver when you need to double-check the your alert settings!
Questions? Comments? Suggestions? Ask John! If we use your input in a future newsletter, we’ll send you a $10 Amazon gift card.
This week’s Ask John question is from Oscar Jiminez at Megadata Information Solutions in Costa Rica. Thanks, Oscar!
Question: In an EDM high availability hypothetical scenario (2 EDMs working as active/active nodes), can both EDMs can share the same EDM DB? Under this scenario, I can put this database in a SQL cluster and provide it also high availability.
Answer: Certainly. This implementation is supported; click here for an example of configuring JBoss with Apache HTTPD.
There are three basic components to the Sightline Software Solution: data collection, data storage, and turning that data into meaningful information. Last week we looked at data collection. This week we will look at how Sightline stores the data.
After we collect the data we store it centrally in the Sightline Big Data Repository. Our Big Data Repository, like the rest of our software, is policy driven. We designed it this way to give you full control to determine what you do with the data after we collect it. You can easily configure how long to keep the data, when to dump it and when to archive it, to give you full control of your environment.
Summarization is done at the same time – you determine the summary interval and how long to keep the data at that interval. In fact, you can have multiple summary intervals, with different retention periods for each one. Remember that we only collect the data one time, so we only need to store it one time. We do this to keep the overhead down and not burden your systems with unnecessary waste. You can also feed the data to RDBMS or your message platforms for ticketing and other uses.
Security is always a concern for IT teams. Sightline EDM has you covered by providing support for Secure Socket Layer (SSL) which secures your browser communications with the EDM Server. Click here for configuration details.
Sightline Enterprise Data Manager (EDM) includes many chart formats for displaying and analyzing your performance and capacity data. Using the zoom line chart, you can show thousands of data points at a time, and then either zoom in to examine a subset of that time span or “pin” a shorter time span and compare it to non-adjacent time periods.
Switch to Pin mode in the zoom line. You can then highlight a section of the chart to visually compare to other sections of the chart. In this example, we selected the day of February 3, from midnight to midnight.
The Sightline Power Agent for Linux Systems is required to be installed from a user with full root access. However, this is not always possible. This document provides steps to grant root privileges to non-root users, so that they can install and run the Sightline Power Agent on Linux systems.
Linux uses RAM memory for disk caching to speed up the system. This means that the Mem % Free metric will consistently be low, perhaps 5%, when the system is actually only using 50% of the RAM. In Sightline, this real usage can be monitored and alerts can be created to alert you if the amount of real memory goes too low.
In addition to the in-depth operating system metrics that Sightline collects for virtually all platforms, Sightline can collect and analyze performance metrics for many Java J2EE servers including IBM WebSphere Application Server and RedHat JBoss. This allows alerting, analysis and reporting of all the critical metrics related to EJBs, JMS Queues, Connection Pools, memory and threads. Find issues faster and track them down using the advanced analytics found only in Sightline. Click here for details.
Q: Can I display the sum of a metric across multiple data sources?
A: Yes. Visualization in EDM includes a sum across data sources feature. When you create a chart, click the Sum Across Data Sources checkbox. Add the chart to a template, then create a report using that template and assign multiple data sources to the report. When the report is displayed, the target metric(s) will be summed for all of the data sources selected in which it appears.