Building for the Splunk Platform

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 

Get Updates on the Splunk Community!

New Splunk Observability innovations: Deeper visibility and smarter alerting to ...

You asked, we delivered. Splunk Observability Cloud has several new innovations giving you deeper visibility ...

Synthetic Monitoring: Not your Grandma’s Polyester! Tech Talk: DevOps Edition

Register today and join TekStream on Tuesday, February 28 at 11am PT/2pm ET for a demonstration of Splunk ...

Instrumenting Java Websocket Messaging

Instrumenting Java Websocket MessagingThis article is a code-based discussion of passing OpenTelemetry trace ...