Hi @inventsekar ! I'm using a UF on the client, where I'd like to get rid of the journald log lines. So, if I understand you correctly : I need to send all journald log-data to the HF/indexer, and there use transforms to drop the lines? Thanks for your help! Best regards Johan
... View more
Hi, I'm ingesting journald logdata, and would like to exclude all rows with "apparmor=ALLOW". To me, the journald-filter parameter would do the trick, if I can invert the selection, i.e. "grep -v" Is this possible, or is there another way to do this, without adding everything else to the journald-filter-parameter? I'm using UF and Enterprise 9.4.1 TIA Johan Nilsson
... View more
Hi, I have issues with Splunk Enterprise 9.4.2 not expanding $_index_name from etc/system/local/indexes.conf. My default-section: [default] ... coldToFrozenDir = $SPLUNK_DB/$_index_name/frozendb ... This should be fine if I read the docs for indexes.conf The config file is read, especially since it creates the $SPLUNK_DB/'$_index_name'/frozendb, i.e. without expanding the variable. $SPLUNK_DB is still expanded correctly. Googling turned up the answer in Splunk data retention - Splunk Community, but the resolution there is to manually expanding it and putting the $SPLUNK_DB/"indexname"/frozen under each stanza. And I'm not that keen on doing that. TIA Johan
... View more
Thanks. Could you elaborate? My understanding is that [httpout] will tunnel s2s over http to a HEC on the server. This give us one-way communication possible, since the diode accepts the http-session and closes it with a "200 ok"-reply.
... View more
Thanks, that's what I've found as well. I did tunnel the data through a nginx reverse-proxy, and that forwarded the data as "complete" and not "chunked". The problem is that this will change the design of the network, and will require a new approval. So any workaround that don't require design-changes would be great. //Johan
... View more
Hi, We're setting up a Splunk enterprise instance in an air-gapped environment. In addition to this, the server is situated behind a diode, making all traffic one-way. I've gotten the Splunk Universal Forwarders to send logs over http to the HEC, but the diode doesn't support chunked http-encoding. It isn't possible to turn off http 1.1-support in the diode. In the server, there's the option "forceHttp10", but since the client and server doesn't negotiate the http-version it has no effect. Is there an option in the UF to turn off http 1.1 or chunking for httpout? TIA Johan
... View more