Getting Data In

splunk-bunyan-logger logs in impractical format

mcv
Engager

I'm using splunk-bunyan-logger to log to splunk. The example on https://github.com/splunk/splunk-bunyan-logger suggests using it like:

 

 

Logger.info({
    message: {
        temperature: "70F",
        chickenCount: 500
    }
}, "Chicken coup looks stable.");

 

 

 I'm using it like:

 

 

logger.info({ name, type: 'queryPerformance', ms }, `${name} took ${ms} ms`);

 

 

Despite not wrapping my own fields (name, type and ms) in a `message` object, in splunk, they do still end up in a message object. So I have to search by `message.type` instead of just `type`. Also, the text message ("Chicken coup looks stable" or `${name} took ${ms}`) does not show up anywhere at all.

Is there a better way to use splunk-bunyan-logger to make it log the way I want it to?

Labels (1)
0 Karma

richgalloway
SplunkTrust
SplunkTrust
The logger uses Splunk's HTTP Event Collector, which expects events in JSON format. See https://docs.splunk.com/Documentation/Splunk/8.0.4/Data/FormateventsforHTTPEventCollector
The problem with using someone else's code is you're stuck with how they do it. To log the way you want to you'll need to write your own code, perhaps using the bunyan logger as a starting point.
---
If this reply helps you, Karma would be appreciated.
0 Karma
Get Updates on the Splunk Community!

Splunk Mobile: Your Brand-New Home Screen

Meet Your New Mobile Hub  Hello Splunk Community!  Staying connected to your data—no matter where you are—is ...

Introducing Value Insights (Beta): Understand the Business Impact your organization ...

Real progress on your strategic priorities starts with knowing the business outcomes your teams are delivering ...

Enterprise Security (ES) Essentials 8.3 is Now GA — Smarter Detections, Faster ...

As of today, Enterprise Security (ES) Essentials 8.3 is now generally available, helping SOC teams simplify ...