Feedback
Got feedback? We want it! Submit your comments and suggestions for our community here.

Post formatting consumes characters

nplamondon
Communicator

Posts appear to now be interpreted as markdown, so there are lots of instances of broken answers since not everyone properly uses code tags. For example, if I had posted an unformatted props.conf on the old site, it now looks like:

[sample]

INDEXEDEXTRACTIONS = csv
SHOULDLINEMERGE = False
TIMEFORMAT = %Y%m%d
TIMEPREFIX = ^
MAXTIMESTAMP_LOOKAHEAD = 8
MAXDAYS_AGO=10000s

Real example of SPL being mangled: https://community.splunk.com/t5/All-Apps-and-Add-ons/SAI-Windows-entity-does-not-show-up/m-p/480674/...

Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

From Raw Data to Executive-Ready Stories, Faster

Build Data Stories for Every Audience  A dashboard is rarely just a dashboard. It might be the view an ...

Guided Onboarding with Auto-schema Is Now Generally Available

  We are excited to announce the General Availability of Guided Onboarding with Auto-Schematization ...

ATTENTION: We’re Moving! (AGAIN!)

The Splunk Community Slack is undergoing a system migration to keep our workspace secure and ...