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!

What’s New in Splunk AI: Volume 02

Welcome to the second edition of “What’s New in Splunk AI” where we look at the latest and greatest updates, ...

Splunk App Dev Quarterly Roundup: AI, Agents, and Innovation!

Another quarter, another wave of innovation. From complex integrations to pushing the limits ...

Federated Search for Dynamic Data Self Storage Is Now Generally Available on Splunk ...

 Splunk is excited to announce the General Availability of Federated Search for Dynamic Data Self Storage ...