Apache Log4j vs. Splunk Log Observer

There is multiple reasons. All types are logging messages support not only string msg. We can use parametrized variables for logging Support advance filter for logging like (Data, Markers, Regular Expression) Support Plugin Architecture (We just use the dependency and Layout configuration with minimal config, and this will start to work) Integration support with application server Could enable.

Incentivized

Great for organizations that need to centralize different types of logging across integration, qa, sandbox and production environments. Would be less impactful for organizations that don't have complex logging needs.

• Integration with java.
• Configure logging levels.
• Customize logging contents.

Incentivized

• Providing in-depth insights
• A related content feature which really helps us to figure out which service is breaking the infrastructure.
• The Log explorer which helps us to explore the entire log and pin point the errors/issues.
• Fast and powerful log investigation

Incentivized

• Fixed the vulnerability which is reported which affect many big brand.
• There should be security check to check all vulnerability.

Incentivized

• Integrating the system with Slack channels
• Saving the logs in different cloud provider
• Viewing the logs at more fine grained level based on user roles and permissions

Incentivized

I'm a Splunk specialist, and I'm involved in its use and improvement.

Incentivized

It gives access to data features for every level of users: from managers and executives to Analysts, each one with the correct level of observation and analysis.

Incentivized

Splunk support is very quick and efficient. Pre-sale specialists are very skilled and available.

Incentivized

Follow a training before starting.

Incentivized

The ability to customize logging levels and manage log files is superior to other products we have looked at; due to this we selected to go with log4j.

Incentivized

I had not considered other products because Splunk Log Observer was in use in my company before I started working there.

Incentivized

• Good logging tools we can integrate with minimal resource consumption.
• Ease of understanding.
• Plugin play component Architecture.
• Advance filter support can be used to filter all types of logs and events, which can be further analyzed.

Incentivized

• Significantly reduced the MTTR (Mean Time To Recovery), which in turn has improved the end-user experience tremendously.
• Meets compliance requirements of security policies, audit, regulation, and forensics.
• Helps us to track/manage the resource usage on our cloud instances which has a direct implication on the recurring cost.

Incentivized