RSS Feed for Splunk
- .conf2014 Highlight Series: Splunk Monitoring Console
Welcome back to our .conf2014 highlight series! Today, we revisit another one of our most popular sessions of last year’s conference, “Splunk Monitoring – New Native Tools for Monitoring your Splunk Deployment.”
Good for All Skill Levels
Splunk Admin, Deploying Splunk
Collecting, interpreting and reporting on what Splunk is doing, especially in a distributed Splunk deployment can be challenging for the Splunk administrator. Where is the data that I’m indexing in Splunk coming from? What searches are taking up large amounts of system resources? How are the machines that Splunk is running on performing? This session covers new native tools in the Splunk platform for performing these and other administrative activities.…
- Troubleshooting connectivity issues to Splunk’s API from the SDK
A common problem we see customers struggle with is how to diagnose connectivity issues with any of our SDKs. In this post, I’ll show you a few tried and true practices that can help you figure out what might be going wrong.
There are two main families of errors folks see. One has to do with general connectivity / connection info, and the other has to do with security config on the client.
General connectivity issues
This means that you are unable to succesfully connect to the API. The best way I find to diagnose is to drop to a terminal and use curl to login to the Splunk API and see the results. The command to use is:
New features and APIs
- Added Service.getJob() method for getting a Job by its sid.
- Added Service.ConfigurationFile.getDefaultStanza() method for getting the [default] stanza of a conf file.
- Updated the GitHub commits example to show this functionality.
- The node/helloworld/get_job.js example shows how to get a Job by its sid.
- The node/helloworld/endpoint_instantiation.js example …