Hi Everyone,
Is anyone else having issues with the Client tab not showing the correct Server Classes for the Host Names? For example, we have windows systems that are being labeled as Linux because we have a server class with a filter * but specific to linux-86_64 Machine Type. This almost gave me a heart attack because I thought the apps tied to this server class was going to replace the Windows ones.
However, when I go into the server class itself, the "Matched" tab only shows the devices that match the filter and when I check a handful of Windows devices itself, I don't see the apps that are tied with the Linux server class.
Wondering if anyone is experiencing this as well? And if so, if a fix is found.
There's no workaround for the bug - this issue only affects filtering on machine types, so if it’s possible to arrange some filters which won’t require machine types (like names, addresses, etc), these filters work. Obviously after fix they can return to more convenient machine types filters.
@sylim_splunk It's not just a display problem. Queries using the rest interface also return no results.
But the strange thing is that on some deployment servers it works without problems on the same version, but a large part does not allow rest on /services/deployment/server/clients.
On servers where the rest query don't work, there's also zero results under Forwarder Management/Clients.
Regards Marco
This seems to fix the rest endpoint issue (esp. changes to outputs.conf).
https://docs.splunk.com/Documentation/Splunk/latest/Updating/Upgradepre-9.2deploymentservers
not sure about that, but we are having major issues after the upgrade to 9.2.1 with both of our Deployment Servers (running on Windows Server 2019)
one server is only supposed to show us Servers and the other is only supposed to show us our Workstations but now they are comingled on both, this poses a major problem as apps meant for servers may end up being installed on the Workstations and vice versa
we opened a Technical Support case on this a week ago and will let you know how it goes, so far their work arounds are not fixing anything for us
Any followup on this? I am seeing the same issue.
Splunk team confirmed that is a bug on Splunk version 9.2.x. The Splunk Dev team is working on that. We can wait until they release fix version.
You should create a support/bug ticket to Splunk Support.
** If this helps, please upvote or accept solution. **
Thanks.