Over a million developers have joined DZone.
{{announcement.body}}
{{announcement.title}}

Define Your Log Repository as a Chrome Custom Search Engine

DZone's Guide to

Define Your Log Repository as a Chrome Custom Search Engine

· DevOps Zone ·
Free Resource

Learn how integrating security into DevOps to deliver "DevSecOps" requires changing mindsets, processes and technology.

If you have a production app, you should be using some log repository (we use Splunk at Commerce Sciences).

Now, Splunk is great, but it’s causing us a bit of a headache – whenever we access it, we have to go through a few pages of login (not really needed), and a page requesting we upgrade to the latest version (we usually ignore it). All and all, it takes too much time and friction to search for logs.

Today, I had a cool idea – why not configure a Chrome Custom Search Engine and save us the trouble? It turns out it works and it’s awesome (it makes your log just a CTRL-L away). Just add a new Splunk search engine (read the help if you need), enter your favorite keyboard shortcut (I went with “spl”, but you can use “log”) and as a URL enter

http://yoursplunkserver.com/en-US/app/search/flashtimeline?q=search%20%s

That’s it – you just made your logs a whole lot more accessible. If you try this on another log repository other than Splunk, please post your own URL as a comment. Enjoy!

Learn how enterprises are using tools to automate security in their DevOps toolchain with these DevSecOps Reference Architectures.

Topics:

Published at DZone with permission of

Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}