DevService Ideas for Splunk

[melloware]

Have you thought about adding a DevService using Splunk Free?

Or I would love some docs on how to configure it for local Splunk for testing. For example this Docker Compose file:

version: "3.6"

services:
  splunk:
    image: splunk/splunk:latest
    container_name: splunk
    environment:
      - SPLUNK_START_ARGS=--accept-license
      - SPLUNK_LICENSE_URI=Free
      - SPLUNK_PASSWORD=splunkadmin
    ports:
      - "8000:8000"  # Splunk Web Interface
      - "8088:8088"  # HEC (HTTP Event Collector)
    volumes:
      - splunk_data:/opt/splunk/var/lib/splunk

volumes:
  splunk_data:

What is the Quarkus Logging Splunk configuration to hit this localhost:8088 docker compose stack?

[rquinio1A]

Today we use this QuarkusTestResource for the integration tests based on testcontainers: https://github.com/quarkiverse/quarkus-logging-splunk/blob/main/integration-test/src/test/java/io/quarkiverse/logging/splunk/SplunkResource.java

Adding a DevService would make perfect sense, there could even be a basic DevUI that integrates the Splunk web UI of the DevService as an iframe. An example of an extension doing that could be the microcks-quarkus extension: https://github.com/microcks/microcks-quarkus/blob/main/deployment/src/main/java/io/github/microcks/quarkus/deployment/DevServicesMicrocksProcessor.java

[melloware]

Yep I am the author of the Mailpit extension which is a SMTP dev service with DevUi to the mailer ui. It would be great if Splunk had this.

[vietk]

@edeweerd1A just provided this feature, hence closing this one, reopen in case you are not happy with the new devservice

[melloware]

awesome!