Solace Community is getting a facelift!

On March 3rd we will be starting the process of migrating Solace Community to a new platform. As a result, Solace Community will go in to a temporary read-only state. You will still be able to come onto Solace Community and search through posts to find answers, but you won't be able to ask questions, post comments, or react in any way.

We hope to have the migration complete by Wednesday March 5th (or sooner), so please keep an eye out!

Additional Solace PubSub+ logging [solace/solace-pubsub-standard]

Tomasz
Tomasz Member Posts: 5 ✭
in General Discussions #1

Maybe it would be possible to add additional console log when solace event broker is ready for configuring ?

For now we're searching for "Primary Virtual Router is now active" on /usr/sw/jail/logs/system.log which is making waiting complicated (executing grep/cat on this file in a loop instead of waiting for console log).

Tagged:

Answers

  • marc
    marc Member, Administrator, Moderator, Employee Posts: 973 admin
    #2

    Hi @Tomasz,

    Can you share more about what you're trying to do here? Is this for manual configuration or automated via your CI/CD pipeline?

  • Tomasz
    Tomasz Member Posts: 5 ✭
    #3

    We need some additional information to be able to determine when we can execute solace configuration using cli.

    You can see the example here:

    https://github.com/testcontainers/testcontainers-java/blob/main/modules/solace/src/main/java/org/testcontainers/solace/SolaceContainer.java

    For now we are checking system.log file in a loop to verify solace readiness and then we're executing configuration script.

  • marc
    marc Member, Administrator, Moderator, Employee Posts: 973 admin
    #4

    Interesting, but if we were to write something to the console wouldn't you now just be checking the console output in a loop for a different message? or does testcontainers have some sort of built-in support that handles that?

  • Tomasz
    Tomasz Member Posts: 5 ✭
    #5

    Veryfing console log is already implemented on testcontainers and this can be used (with this new information) as a container wait strategy.

    But this information can be useful even for standard solace setup (using docker container for example) - to show the time when user can manually configure solace.

Categories

This Month's Leaders

This Week's Leaders