Thank you for the Varonis File Monitoring connector.
Thanks, just need to get these connectors added. Just dropped into a network utilizing old dell N series switches and I want to get them monitored in LEM.
How can I get additional connectors added?
You can raise a Technical Support ticket in order to request an additional connector. Your Support Engineer will ask you a number of questions on the logs you wish to support and will also request a log sample. We can then assess the feasibility of building a connector.
How am I supposed to know how each of the connectors are supposed to work? Some have some information about them but many just have generic text explanation? The ones of primary concern to me right now are even the linux 64 bit agent and Solaris agent ones. My current machines may not be logging the way the agent expects... how do I know how to log correctly on the OS for agent to work?
I'd like to try the VMware vCenter 6.0+ VPXD Logs connector, but I do not see it under the Appliance's connectors. It's only available on Agent Nodes.
Does this mean it was only developped for a vCenter Server installation on a Windows Server with a LEM Agent installed ? Because if you are running it as a virtual appliance, you should be able to add it as a Syslog node when you forward the logs to LEM...
Thanks for the update and the connectors!
Any plans to add juniper srx support?
What is the difference betweenSolarWinds LEM MSSQL Auditor and Microsoft SQL Server Audit?
Is SolarWinds LEM MSSQL Auditor obsolete now? If so, is there a KB saying how to deploy Microsoft SQL Server Audit?
Thank You
Steve
The SQL Auditor requires SQL Profiler to monitor traces and pump that data into SEM. Microsoft have issued a deprecation notice for SQL Auditor and it is now in maintenance mode. Our SQL Auditor is still fully supported, but we want to give customers some flexibility when monitoring SQL audit events.
The new SQL Server Audit connector doesn't have any reliance on SQL Profiler traces, it monitors SQL Audit events from the Windows Application or Security logs. I found this article quite useful when configuring SQL Audit to send events to the Windows Security log.
Hi jhynds on this comment:
Our SQL Auditor is still fully supported, but we want to give customers some flexibility when monitoring SQL audit events
The SolarWinds MSSQL Auditor does not support SQL Server 2016. This was a big issue that came up earlier.
If you could add support for SQL Server 2016 in SolarWinds MSSQL Auditor, it would benefit us much better.
While Extended events are also recommended by Microsoft, SQL Traces still work in SQL 2016 and getting logs through MSSQL Auditor was much more efficient than through SQL Extended events, due to several reasons:
Have you tried the new MS SQL Audit connector? I know you were previously using the MSSQL Application Log connector, but we've made some improvements to the parsing and released the MS SQL Audit connector. Would love to know if you find an improvement on the parsing with our newer connector.
Yes I installed the new connectors and then enabled the new SQL Audit connector (SQLAudit.xml connector file) in few of our DB nodes.
All the events under the new connector (Tool Alias) are coming as UnmatchedData from the InternalNewToolData event.
I also opened a support ticket #00380287 to look on this.
Edit: to add to this, since the issue from screenshot is a problem, I had to install a previous set of connectors so that MSSQL events are again logged into SEM through the MSSQL Application Log connector (mssqlapplicationlog.xml connector file)
SolarWinds solutions are rooted in our deep connection to our user base in the THWACK® online community. More than 150,000 members are here to solve problems, share technology and best practices, and directly contribute to our product development process.