I don't see many apps requiring install additional dependencies previously. If you create a modular input, and users install your app, they can access the modular input from Splunk web (https://docs.splunk.com/File:Mod_inputs_splunk_web.png a screen shot in the doc, https://docs.splunk.com/Documentation/Splunk/7.2.5/AdvancedDev/ModInputsBasicExample). As far as I can tell, many users will not read your manual to run npm install before installing your app (check out http://www.readthefuckingmanual.com), they will simply install it and see the modular input fails to work. In that case, one approach is commenting them out so that they don't see it and will have to start reading the manual. ... View more

@splunkian this means your app is a partial app requiring further update to work, and this makes the verification fail to work. Since you already ask your app users to manually install some dependencies to work, can you try comment out some parts of your app, like the modular input you have, and add an additional step for your users, saying something like "once you install the dependencies, uncomment these lines in inputs.conf to enable it"? ... View more

Hi splunkian, The AppInspect API is slightly different with AppInspect CLI and it has more checks, including some runtime checks requiring installing the app into a running Splunk instance and verify the given app's conformance. They are not included in AppInspect CLI for the sake of ease of distribution. At the same time, AppInspect API service may use a more recent version of AppInspect library (used by the AppInspect CLI as well), and this may cause some difference. You can trust the result of AppInspect API service since it is more complete and more recent. In your case, the difference is because of the runtime checks included in AppInspect API. If you remove the node_modules folder, could you confirm if it (after removing the node_modules folder) still works for generating a valid modular input scheme (http://dev.splunk.com/view/python-sdk/SP-CAAAER3) after installing it into Splunk Enterprise? ... View more

According to what I understand, it means the third meaning you mentioned, "one per actual client running the software". I think this is only needed if you use the indexer acknowledge, and you can read more details from here: http://dev.splunk.com/view/event-collector/SP-CAAAE8X#aboutchannels ... View more

I assume using the default stanza should work, your second approach (the code may handle the null value as "on" in this case): [default] auto_disable = false Doesn't this work for you? ... View more

Splunk Mobile Access Server is deprecated and now a first party Splunk add-on called "Splunk Add-on for mobile access" is recommended for mobile access purpose, and it should be easier to install and configure since it is a Splunk app essentially. You may give it a try instead. https://splunkbase.splunk.com/app/2887/ ... View more

Yes, this is a known issue and will be addressed in our next minor release. Thanks. ... View more

Got it, thanks. ... View more

Sorry for the inconvenience, this is because the APN certificate got expired for mobile access server, and you have to update the APN certificate to make it work. Unfortunately we don't provide a standalone distribution for the APN certificate, and you can try to install the Splunk add-on for mobile access, which ships with a renewed APN certificate and can be used to replace the mobile access server. You can download it here: https://splunkbase.splunk.com/app/2887/ ... View more

Do you have any more detail about the "Traffic LIght Visualizations app" you mentioned? ... View more

Tarek1977, you could drop me a mail via sni AT SP!UNK D0T C0M and I could try to invite you to join a beta program if you want to and maybe the new release of the server component can address your issue. ... View more

There is a way I can think of to get the debug log for these libraries but this is more difficult than it should be, and if you like, you can give it a try by following the steps below: 2.1) Start the server by running server.sh start 2.2) Run killall Splunkm to kill all node.js processes but keeps the mongodb running 2.3) Enter the 'server' directory in your mobile access server installation folder 2.4) You need to install 'debug' node module (https://www.npmjs.com/package/debug). This module is not shipped with mobile access server, and npm is not shipped with mobile access server. To install this module, you probably have to either install npm in your Linux machine and then install the debug module by running npm install debug in current 'server' folder, or install this module in another machine and copy the entire 'debug' module installation folder to 'server/node_modules' folder. 2.5) Run NODE_DEBUG=request node --debug --harmony server.js 2.6) Navigate to the above status page, and you should be able to see debug log in the console: REQUEST response end https://android.googleapis.com:443/gcm/send 200 { 'content-type': 'application/json; charset=UTF-8', date: 'Thu, 17 Sep 2015 03:30:07 GMT', expires: 'Thu, 17 Sep 2015 03:30:07 GMT', 'cache-control': 'private, max-age=0', 'x-content-type-options': 'nosniff', 'x-frame-options': 'SAMEORIGIN', 'x-xss-protection': '1; mode=block', server: 'GSE', 'alternate-protocol': '443:quic,p=1', 'alt-svc': 'quic=":443"; p="1"; ma=604800', 'accept-ranges': 'none', vary: 'Accept-Encoding', connection: 'close' } REQUEST end event https://android.googleapis.com:443/gcm/send ... View more

About the logging. With debug level logging enable, in the server.log, you should be able to see something like "debug: category=incoming_request, requestId=74802066f72e8514144273fa1f585ab8, method=GET, originalUrl=/m/console/home/status/gcm", which means a request is sent to mobile access server to retrieve the GCM status, but you probably cannot find anything useful besides this. This is because for APN and GCM, we use third party libraries for communication with APN and GCM servers, and they don't log to log file but log to stdout and stderr, which you cannot see because the server is daemonized. ... View more

"npm config set https-proxy http://username:password@proxy.company.com:8080" will only work for npm instead of node. ... View more

1) "npm config set https-proxy http://username:password@proxy.company.com:8080" will only work for npm instead of node. 2) About the logging. With debug level logging enable, in the server.log, you should be able to see something like "debug: category=incoming_request, requestId=74802066f72e8514144273fa1f585ab8, method=GET, originalUrl=/m/console/home/status/gcm", which means a request is sent to mobile access server to retrieve the GCM status, but you probably cannot find anything useful besides this. This is because for APN and GCM, we use third party libraries for communication with APN and GCM servers, and they don't log to log file but log to stdout and stderr, which you cannot see because the server is daemonized. There is a way I can think of to get the log but this is more difficult than it should be, and if you like, you can give it a try by following the steps below: 2.1) Start the server by running server.sh start 2.2) Run killall Splunkm to kill all node.js processes but keeps the mongodb running 2.3) Enter the 'server' directory in your mobile access server installation folder 2.4) You need to install 'debug' node module (https://www.npmjs.com/package/debug). This module is not shipped with mobile access server, and npm is not shipped with mobile access server. To install this module, you probably have to either install npm in your Linux machine and then install the debug module by running npm install debug in current 'server' folder, or install this module in another machine and copy the entire 'debug' module installation folder to 'server/node_modules' folder. 2.5) Run NODE_DEBUG=request node --debug --harmony server.js 2.6) Navigate to the above status page, and you should be able to see debug log in the console: REQUEST response end https://android.googleapis.com:443/gcm/send 200 { 'content-type': 'application/json; charset=UTF-8', date: 'Thu, 17 Sep 2015 03:30:07 GMT', expires: 'Thu, 17 Sep 2015 03:30:07 GMT', 'cache-control': 'private, max-age=0', 'x-content-type-options': 'nosniff', 'x-frame-options': 'SAMEORIGIN', 'x-xss-protection': '1; mode=block', server: 'GSE', 'alternate-protocol': '443:quic,p=1', 'alt-svc': 'quic=":443"; p="1"; ma=604800', 'accept-ranges': 'none', vary: 'Accept-Encoding', connection: 'close' } REQUEST end event https://android.googleapis.com:443/gcm/send ... View more

Unfortunately, node.js does not seem to support using global proxy, and you have to modify http.request (https.request) to use the proxy. There are some modules like https://www.npmjs.com/package/global-tunnel which does this job but it is not tested if this affects other functionalities. There are two other ways I can think of so far, but they are not canonical solutions and are not officially tested yet. 1) change the node-gcm library The proxy settings for GCM requests is not exposed yet via configuration in the mobile access server, and if you really want to do this at present, you probably could modify the underlying library we use (node-gcm) to apply your proxy and replace the existing library in node_modules folder with the modified version. (https://github.com/ToothlessGear/node-gcm/blob/master/lib/sender.js#L92) 2) set up a custom proxy for GCM Alternatively, since the mobile access server talks to GCM using https://android.googleapis.com:443, you could modify the DNS in your Linux server to resolve android.googleapis.com to your proxy server IP address and this will make the server to connect to your proxy and this is a little bit hacky but it will probably work but I don't test this solution yet. ... View more

I removed the single hardcoded path since v1.0.1 (which is not related to this problem I think). But it is true that I didn't get it tested on Windows and I only tested it in two Linux boxes and one Mac because I don't have a Windows 8.1 copy for me to test 😞 I will try to find a Windows environment to test it later. ... View more

Thanks for the feedback. I don't implement the canceling by myself, instead, it is a feature in Splunk's JavaScript library API, but it is probably I did not use it correctly or it is not working as I expected, and I will take a close look at it. Maybe a search button is the ultimate solution to this problem 🙂 ... View more

the connection to APNs is invalid for both This means the servers in your network cannot reach APNs. To talk to APNs, port 2195 for gateway.push.apple.com should be accessible from your server. To test your network, you can use netcat, telnet or openssl client. For example: 1) Use netcat to test the connection: nc -zv gateway.push.apple.com 2195 It should report something like "Connection to gateway.push.apple.com port 2195 [tcp/*] succeeded!” 2) Use telnet to test the connection: telnet gateway.push.apple.com 2195 It should report something like "Trying 17.143.164.13… Connected to gateway.push-apple.com.akadns.net" It is probably the firewall in your network prevents your servers from talking to APNs gateway and makes the connection invalid. If you can confirm this is a network problem, you can configure your firewall to make the connection back to work. ... View more

I am the author of this app. Thanks for suggestion, I am happy to add this feature later. Currently, while you type, a search will be submitted to Splunk, and if you keep typing, the client will cancel previously submitted search if it is still running so there won't be any orphan search job left and consuming resource. However, as I mentioned in the user guide page, it is recommended to develop and verify the SPL against a small data set so that the editor can give you a quick feedback without burning huge resource. ... View more

I am the author of this app. Sorry for this issue, and you can try to restart Splunk and refresh the page to make it work, and I am not aware that Splunk does not require restarting after installing this app (since I typically use symbolic link to install this app in my development environment). I uploaded a new version (1.0.1) and you can download it and give it a try to see if it works for you. Thanks. ... View more

There is some issue with the scheme in the link (http/https). Chrome seems to have stronger enforcement of security and prevents the download. Please follow the link posted by anagavaram to download at present. ... View more