merrimanr

Almost all correct. There are other `ServiceDiscoverer` instances created [here](https://github.com/apache/metron/blob/master/metron-analytics/metron-maas-service/src/main/java/org/apache/metron/maas/service/runner/Runner.java#L193) and [here](https://github.com/apache/metron/blob/master/metron-analytics/metron-maas-common/src/main/java/org/apache/metron/maas/functions/MaaSFunctions.java#L229). Here's what each one does: `MaasIntegrationTest` - Used to test which endpoints are registered. Runs in test. `MaaSFunctions`...

Ah makes sense @nickwallen. Done with latest commit.

You're correct @ruffle1986. The group should already be added when full dev spins up rather than having to add it in a separate step. I am testing a change that...

The latest commit should setup the parser group in full dev automatically.

We are not at a point in the review where we can spin up or test anything. Agreed, documentation belongs in the REST README.

I filed this as a bug back in March based on feedback from the contributors working on the parser aggregation feature branch. This fix is required for that feature to...

Are you saying you want a more detailed description the bug as it relates to the UI? This might be easier to demonstrate when the UI part is further along.

It was a Slack conversation. @ruffle1986 was testing and noticed group names were not working for the endpoint that gets status for all topologies (vs the endpoint that gets status...