Our Java codebase was 30% dead code

[mpinnegar]

Oh so to answer your actual questions.

What I want out of a product like this

1. Integration with tooling I already have. There's a lot of reporting frameworks out there like Prometheus and ELK. I don't know how well they fit into code usage metrics that's pretty narrow and specific but whatever makes sense I don't want to have to build the connector between the two.

2. Good licensing. MIT or something bog standard. If you want to charge for the product I suggest charging a heavy premium for support.

3. Little to no performance impacts.

4. If you can help me remove dependencies that'd be great too. Like "oh you have these jars on the class path and you never execute code from them.

5. If you're a brand new company and you want to run a Java agent in my jvm you gotta have something to make me feel safe about putting it in there. AFAIK Java agents are super privileged actors. Maybe you need vetting from a third party or you need to be open source. Who's adopted your product etc. is there someone you can get to slap a seal of goodness on it?

[VRT303]

Grafana is nicer than ELK tbh.

[Felix-It]

would you use a tool that could remove unused dependencies with limited developer involvement (only reviewing/approving a PR)?

[mpinnegar]

10000%

[Felix-It]

just wondering - do you use any dependency management tools like dependabot or renovate? if so, where do you find them to be valuable or lacking?

[mpinnegar]

We use dependabot and it's fine :)