About trapti_splunk

trapti_splunk · ‎08-23-2016

Hi, the new VMware version is out. Did you guys get a chance to check? update in case you need any further assistance regarding this issue.

trapti_splunk · ‎05-04-2016

Yes, you will need to make it monitor the correct path in inputs.conf (for vCenter server 6.0) and also in props.conf for proper field extraction. This is a known issue and will be fixed in next release. Let me know if you need any further details regarding the issue.

trapti_splunk · ‎05-03-2016

Is your Data Collection Node added as DCN from multiple schedulers? Or is it acting as DCN for multiple apps?

trapti_splunk · ‎04-26-2016

Once my app (Exchange/VMware) specific indexed data size exceeds my app specific licensing limit, will the reset key work? We typically get a reset key for Splunk Enterprise license violations if we exceeded the daily indexing limit by mistake. Will the similar reset key work for VMware or Exchange specific licenses? Thanks, Trapti

trapti_splunk · ‎04-08-2016

Hi Lee, This is again the SSL issue which we have with Splunk 6.4. This required a change in Hydra. We have a fix for this in our new release.

trapti_splunk · ‎04-07-2016

Yes, we have an issue of SSL with Splunk 6.4 that does not connect to DCN on port 8008. We already have a scheduled release of VMWare where we have fixed this.

trapti_splunk · ‎03-14-2016

Can you check below and update: 1) What is the Splunk version 6.3.x ? 2) Are you getting any error in logs specific to SSL or SSLv2?

trapti_splunk · ‎03-13-2016

Is your Splunk version different on SH/Indexer and DCN?

trapti_splunk · ‎01-12-2016

Hi Renald, then as per suggested by kserra you can create a support case.

trapti_splunk · ‎01-11-2016

Yes, the port for web interface (8000)

trapti_splunk · ‎01-08-2016

Can you check configurations of your DCN machine? - Number of CPU cores defined - Number of worker processes enabled on scheduler. Also try accessing this link: [https://ipaddress:port/en-US/app/splunk_for_vmware/hydra_framework_status ]

trapti_splunk · ‎01-07-2016

Are you still facing this issue?

trapti_splunk · ‎10-27-2015

You can not miss this extra layer of DCN. However you can configure the DCN on same machine where you have your main app. You need to add the same machine details as the DCN node in your collection configuration. As all the required components are already present on main app (SH), so this can be implemented. But this can be used in case of really small environment else you may get performance issues. In this case you will the actual benefits of Data Collection Distribution.

trapti_splunk · ‎10-26-2015

Both the applications will not work on single SH. You can try the above steps of forwarding your indexed ONTAP data to your windows machine (where you have MS Exchange app) and it should work. This works for me in my test environment.

trapti_splunk · ‎10-26-2015

We do not recommend this but however you can try out. Follow the below steps: Unzip the "splunk-app-for-netapp-data-ontap_xxx". Manually drop the 4 folders, "splunk_app_netapp" , "Splunk_TA_ontap" , "SA-Utils" and "SA-Hydra" in your /opt/splunk/etc/apps on the windows machine (where you need ONTAP data). NOTE: Do not configure the app. Just keep the folders in apps directory. Forward your indexed ONTAP data from Linux machine to the windows machine. (forwarding and receiving > configure forwarding > Add NEW > :9997 and save) Configure receiving on port 9997 on your windows machine. (Forwarding and Receiving > Configure receiving > Add port "9997") Restart Splunk. Check under INDEXES, you should get the ONTAP data on windows server.

trapti_splunk · ‎10-23-2015

Here by intermediate forwarder I am assuming the "Data Collection Node". So DCN is always required for collecting metrics. This is where the scheduler sends jobs to collect all data and then DCN forwards it to the indexer.

trapti_splunk · ‎10-12-2015

DCN will not allow you to set more then 8 worker processes. It only requires 4 CPUs to collect data from about 40 ESXi hosts. Please follow the standard guidelines (requirements) to create DCN:

trapti_splunk · ‎09-09-2015

The above error could be caused by incorrect credentials of XtremIO server. Since this app collects data from XtremIO environment through REST API calls, please make sure you are providing credentials of your XtremIO server same as used for web login. Also, once you enter the credentials successfully, you can check an entry in TA-EMC-XtremIO/local/app.conf file. Following is a sample stanza from app.conf : [credential:10.0.1.7:admin:] password = $1$RZ6XaC9K

Posts	18
Solutions	2
Karma Given	0
Karma Received	2
Member Since	‎09-03-2015

Online Status	Offline
Date Last Visited	‎06-05-2020 02:04 AM

Is reset key support available for the Splunk App ...

Re: Splunk App for VMware 3.2.2: Why am I unable t...

Re: Splunk App for VMware 3.2.2: Why am I unable t...

Re: Splunk App for VMware: "ERROR [HydraWorkerNode...

Is reset key support available for the Splunk App ...

Re: Error on NetApp Ontap App | Data Collection N...

Re: Splunk App for VMWare - Hydra gateway not star...

Re: Splunk App for VMWare - Hydra gateway not star...

Re: Splunk App for VMWare - Hydra gateway not star...

Re: Splunk App for VMWare: No Data in Dashboards.

Re: Splunk App for VMWare: No Data in Dashboards.

Re: Splunk App for VMWare: No Data in Dashboards.

Re: Splunk App for VMWare: No Data in Dashboards.

Re: Ontap metrics direct into Splunk Ent

Re: Is it possible to get NetApp logs to the Splun...

Re: Is it possible to get NetApp logs to the Splun...

Re: Ontap metrics direct into Splunk Ent

Re: Splunk App for VMWare DCN - Greater than 8 wor...

Re: EMC XtremIO Add-on for Splunk Enterprise: How ...