https://community.splunk.com/t5/Monitoring-Splunk/Clarity-on-Splunk-CM-LM-MC/m-p/630536#M9326 <P>Hi&nbsp;<a href="https://community.splunk.com/t5/user/viewprofilepage/user-id/248607">@munang</a>,</P><P>I agree with you that isn't so clear the managing roles division in Splunk, for this reason I voted for a proposal in Splunk Ideas (<A href="https://ideas.splunk.com/ideas/EID-I-48" target="_blank">https://ideas.splunk.com/ideas/EID-I-48</A>) to have a unique console grouping all the managing roles and i's a future prospect.</P><P>Anyway, answering to your questions:</P><P>1. Is it true that the monitoring console exists to check the indexer's health or CPU usage?</P><P><STRONG>no it's a reductive affirmation: this is a part of its features: it can monitor all the activities of your Splunk on-premise infrastructure, because you can monitor all servers health status, indexing, searches, hardware resources usage, license consuption and many other things.</STRONG></P><P>2. If number 1 is correct, I wonder why there is a license usage tab in the monitoring console menu. Does the monitoring console also check the license pool? (Does it also serve as a license master?)</P><P><STRONG>license monitoring is one of the monitoring targets of this App, and it isn't mandatory that the MC is also the License Master.</STRONG></P><P>3. Is it correct to say that the indexer cluster master is a role when divided based on Splunk components, and the monitoring console is a built-in function of the cluster master?</P><P><STRONG>no it's wrong. as I said, using MC you can monitor all your Splunk on-premise infrastructure and it isn't a feature of the CM: the MC is a Search Head that usually it's better to put in a dedicated server or at least shared with a low load role as Deployer or License master, not CM or Deployment Server, except maybe (!) for little infrastructures!</STRONG></P><P>Doesn't the monitoring console and the cluster master instance exist separately?</P><P><STRONG>Yes they should: as I said, you can put them in the same server only in labs or for little infrastrctures.</STRONG></P><P>Ciao.</P><P>Giuseppe</P> Sat, 11 Feb 2023 06:50:53 GMT gcusello 2023-02-11T06:50:53Z https://community.splunk.com/t5/Monitoring-Splunk/Clarity-on-Splunk-CM-LM-MC/m-p/630533#M9325 <P>Hi<BR />I'm Splunk newbie.</P> <P>I'm confused about MC, CM, and LM, so I'm asking a question.</P> <P>1. Is it true that the monitoring console exists to check the indexer's health or CPU usage?</P> <P>2. If number 1 is correct, I wonder why there is a license usage tab in the monitoring console menu. Does the monitoring console also check the license pool? (Does it also serve as a license master?)</P> <P>3. Is it correct to say that the indexer cluster master is a role when divided based on Splunk components, and the monitoring console is a built-in function of the cluster master?</P> <P>Doesn't the monitoring console and the cluster master instance exist separately?</P> Mon, 13 Feb 2023 17:04:51 GMT https://community.splunk.com/t5/Monitoring-Splunk/Clarity-on-Splunk-CM-LM-MC/m-p/630533#M9325 munang 2023-02-13T17:04:51Z https://community.splunk.com/t5/Monitoring-Splunk/Clarity-on-Splunk-CM-LM-MC/m-p/630536#M9326 <P>Hi&nbsp;<a href="https://community.splunk.com/t5/user/viewprofilepage/user-id/248607">@munang</a>,</P><P>I agree with you that isn't so clear the managing roles division in Splunk, for this reason I voted for a proposal in Splunk Ideas (<A href="https://ideas.splunk.com/ideas/EID-I-48" target="_blank">https://ideas.splunk.com/ideas/EID-I-48</A>) to have a unique console grouping all the managing roles and i's a future prospect.</P><P>Anyway, answering to your questions:</P><P>1. Is it true that the monitoring console exists to check the indexer's health or CPU usage?</P><P><STRONG>no it's a reductive affirmation: this is a part of its features: it can monitor all the activities of your Splunk on-premise infrastructure, because you can monitor all servers health status, indexing, searches, hardware resources usage, license consuption and many other things.</STRONG></P><P>2. If number 1 is correct, I wonder why there is a license usage tab in the monitoring console menu. Does the monitoring console also check the license pool? (Does it also serve as a license master?)</P><P><STRONG>license monitoring is one of the monitoring targets of this App, and it isn't mandatory that the MC is also the License Master.</STRONG></P><P>3. Is it correct to say that the indexer cluster master is a role when divided based on Splunk components, and the monitoring console is a built-in function of the cluster master?</P><P><STRONG>no it's wrong. as I said, using MC you can monitor all your Splunk on-premise infrastructure and it isn't a feature of the CM: the MC is a Search Head that usually it's better to put in a dedicated server or at least shared with a low load role as Deployer or License master, not CM or Deployment Server, except maybe (!) for little infrastructures!</STRONG></P><P>Doesn't the monitoring console and the cluster master instance exist separately?</P><P><STRONG>Yes they should: as I said, you can put them in the same server only in labs or for little infrastrctures.</STRONG></P><P>Ciao.</P><P>Giuseppe</P> Sat, 11 Feb 2023 06:50:53 GMT https://community.splunk.com/t5/Monitoring-Splunk/Clarity-on-Splunk-CM-LM-MC/m-p/630536#M9326 gcusello 2023-02-11T06:50:53Z