Skip to content

Instantly share code, notes, and snippets.

@AdamBien

AdamBien/51thAirhacksQ&A.md

Created May 15, 2018 06:38
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save AdamBien/dc00f6b83c2430c91533486e72fb4d54 to your computer and use it in GitHub Desktop.
Save AdamBien/dc00f6b83c2430c91533486e72fb4d54 to your computer and use it in GitHub Desktop.
Download ZIP
51thAirhacksQ&A.md
Raw
51thAirhacksQ&A.md
@mouzerly
Copy link

mouzerly commented Jun 4, 2018

Hi Adam,

A few logging and monitoring questions for a Java EE 7 or 8 greenfield project consisting of several related apps:

  1. Planning to have centralized logging, and to log events using a structured format (JSON). Is java.util.logging sufficient for this (would need to at least create a JSON formatter) or would it be better to use a logging framework like Log4j 2 or other?

  2. It looks like separate tool stacks are often used for logging and monitoring. For example, Elasticsearch/Kibana for log data and Prometheus/Grafana for metrics data. Is this a best practice (why?), or is there a good solution that supports storage and visualization for both log and metrics data?

  3. I was thinking about having apps automatically emit metrics data to some destination, beginning on startup and continuing entire time app is running. Do you see a downside to this approach? If this is done, would you recommend that app metrics also be made available through REST endpoints?

Thanks

@rinkevics
Copy link

Have you tried webassembly? Could it be the future?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment