Hangs on Finishing Console Layout After Logging In
I was previously able to access the LEM console but recently it has started to hang AFTER logging in. The different modules appear as they are loading but when the Finishing Console Layout screen...
View ArticleLEM log4net connector to folder
Hiwe have a configured DFSR which collects log4net app.logs from many servers to one server.And we need to analyse these logs. The problem that I met is when I create log4net connector on that server,...
View ArticleRe: Microsoft Failover Clustering
Do you have any idea what the Microsoft ProviderSID might be for these events?
View ArticleRe: LEM Reports Run Endlessly
This has been working much better for us since the upgrade to RC3. I haven't any time-outs when running searches lately. Fingers crossed.
View ArticleRe: Microsoft Failover Clustering
The LEM has a connector for the Windows Application log. It's not part of the default set that the LEM assigns to a connector when it detects a Windows platform, so you may need to add it to the agent...
View ArticleRe: LEM log4net connector to folder
I took a look at that connector, and my guess is that you'd need to do a connector for each sub-folder. As an experiment, can you try building one that points to a specific log for one of your apps...
View ArticleRe: Hangs on Finishing Console Layout After Logging In
You mention that others can get into console. Are they using the same credentials or are you all using separate accounts? You might try going into the CMC shell, and under MANAGER run a STOP and then...
View ArticleRe: Hangs on Finishing Console Layout After Logging In
Thanks Curtis. I deleted my user account from LEM then added it back in and now it works.
View ArticleRe: Microsoft Failover Clustering
I am in the midst of testing and what I have learned so far is as follows... The Windows Application log is default as per 5.7RC3Microsoft Failover Cluster events are in the System log, not the...
View ArticleRe: Microsoft Failover Clustering
An example of a received event is as shown below, the actual event in the Windows Event Log has a lot more data. Is it normal for LEM to truncate a bunch of information out of the log?
View ArticleRe: Re: Microsoft Failover Clustering
Right, you'll have to run through that process to get the LEM prepared to collect the raw logs or message cores. Next, the relevant connectors need to be set to send raw data to the LEM. Either of...
View ArticleRe: Re: Microsoft Failover Clustering
For the normalized alerts, yes. The LEM tries to reduce noise and improve the readability by trimming and formatting data to meet the needs that customers have shared with us. The ability to capture...
View ArticleRe: Microsoft Failover Clustering
Ok, I have done this before and am familiar with the process. Once that is done am I able to search, create rules, etc in all the same ways as I can with the normalized data? P.S. You need to get the...
View ArticleRe: Microsoft Failover Clustering
Shhh! Else everyone will want one! Unfortunately, you can't make rules or filters off the raw data. You can search it in the Explore tab. If we prove the data is coming in though, we might be able...
View ArticleRe: Microsoft Failover Clustering
Okay, few more questions... If I am getting the logs at all doesn't that prove that the data is coming in? Also, if I configure the system for raw logs, is there a way to back that configuration out...
View ArticleRecommend LEM on LinkedIn for 300 points!
Let your colleagues know how impressed you are with LEM on LinkedInand earn 300 pointsyou can use in the thwack store. Simply go to this link, recommend Log & Event Manager, and then message...
View ArticleRe: Microsoft Failover Clustering
Yeah, it does prove you're getting it, but it's nice to confirm that it's our agent truncating the data and not the mysterious network gremlins or something. It creates a database, but that database...
View ArticleRe: Microsoft Failover Clustering
So is that to say that it can't be undone once you turn on the raw log storage capabilities?
View ArticleRe: Microsoft Failover Clustering
You would turn off nDepth under the nDepth options in the SSH shell, and either leave the DB or call the helpdesk and have us drop the database partition for nDepth data.
View Article