Developing for Splunk Enterprise

Custom REST API endpoint with PersistentServerConnectionApplication

douglasmsouza
Explorer

I'm currently using PersistentServerConnectionApplication to implement custom API endpoints inside Splunk. Any changes I make in code delays about 1 or 2 minutes to start working. 

Is this the correct behavior or am I missing something? If it is the correct behavior, is there any form to test the endpoint immediately after save the code?

Also, I would like to know if BaseRestHandler approach still works on Splunk newer versions (8.x), because I coudn't make this work (python can´t find splunk.rest.BaseRestHandler class).

Best regards.

Labels (2)
0 Karma
1 Solution

livehybrid
Contributor

Ive recently been working with REST endpoints in this way, it took a bit of head scratching but the process stays running, and can be killed with something like this:

sudo kill $(ps -aux | grep -i [\/]opt.*persistconn | awk '{print $2}')

Then it will pick up your changes next time you query it.

I hope this helps

Will 

View solution in original post

livehybrid
Contributor

Ive recently been working with REST endpoints in this way, it took a bit of head scratching but the process stays running, and can be killed with something like this:

sudo kill $(ps -aux | grep -i [\/]opt.*persistconn | awk '{print $2}')

Then it will pick up your changes next time you query it.

I hope this helps

Will 

View solution in original post

.conf21 CFS Extended through 5/20!

Don't miss your chance
to share your Splunk
wisdom in-person or
virtually at .conf21!

Call for Speakers has
been extended through
Thursday, 5/20!