Splunk AppDynamics

Setting up for a large enterprise Env

CommunityUser
Splunk Employee
Splunk Employee

AppD Licensing is expensive.. 

Question..

if you have a large Env, are you instrumenting all the servers in a given app layer or just a % of them? Meaning I have 100 servers that run a dependent layer in my enterprise. should I install the agent on all servers or not?

Would be intersted to hear how others have handled this due to the expense of the licenses. in some cases you are running 3-4 apps on each server (.NET App pools) I have to buy a license for each .NET instance, which can make the expense for a single server huge.

Labels (1)
0 Karma
1 Solution

Rajesh_Putta
Communicator

Hi,

Java licensing is per node based. A node is nothing but a JVM process configured with java agent. So depending on how many nodes you want to monitor you need to configure java agent to those many nodes. If you want to monitor 100 nodes then you need to have those 100 JVM process configured with java agents.

And coming to .NET license

.Net license usage is at server level and the count never change if on a single server multiple .net applications are getting instrumented. 

.NET licenses are per machine agent (not app agent) so how many .NET machine agents are reporting could give you count of usage.  So current license usage depends on how many of the .net machine agents are reporting at given point of time. 

Hope that address your questions. If you have any other questions, please let us know

Thanks

Rajesh

View solution in original post

0 Karma

Rajesh_Putta
Communicator

Hi,

Java licensing is per node based. A node is nothing but a JVM process configured with java agent. So depending on how many nodes you want to monitor you need to configure java agent to those many nodes. If you want to monitor 100 nodes then you need to have those 100 JVM process configured with java agents.

And coming to .NET license

.Net license usage is at server level and the count never change if on a single server multiple .net applications are getting instrumented. 

.NET licenses are per machine agent (not app agent) so how many .NET machine agents are reporting could give you count of usage.  So current license usage depends on how many of the .net machine agents are reporting at given point of time. 

Hope that address your questions. If you have any other questions, please let us know

Thanks

Rajesh

0 Karma
Get Updates on the Splunk Community!

[Puzzles] Solve, Learn, Repeat: Dynamic formatting from XML events

This challenge was first posted on Slack #puzzles channelFor a previous puzzle, I needed a set of fixed-length ...

Enter the Agentic Era with Splunk AI Assistant for SPL 1.4

  🚀 Your data just got a serious AI upgrade — are you ready? Say hello to the Agentic Era with the ...

Stronger Security with Federated Search for S3, GCP SQL & Australian Threat ...

Splunk Lantern is a Splunk customer success center that provides advice from Splunk experts on valuable data ...