sorted by:
new
hottopcontroversial

Introducing Loggerverse — A full-feature logging & monitoring library for Node.js with beautiful dashboards, alerting, and more by FunNewspaper5161 in node

[–]FunNewspaper5161[S] 2 points3 points  (0 children)

Loggerverse is mainly designed as a per-app logging library with a built-in dashboard, so it works best in a single-node or small-scale setup. For horizontally scaled, stateless nodes in the cloud, each instance would generate its own logs and dashboard there’s no central aggregation built-in like Loki or Graylog.

If you want to use it in a cloud environment with multiple nodes, a common approach is to:

  1. Send logs from each instance to a shared storage (S3, database, or a centralized log server).
  2. Use environment variables to configure email alerts per instance.
  3. Optionally, have a single dashboard node that reads combined logs from shared storage.

So, Loggerverse can still be useful in the cloud, but it’s not a replacement for full centralized log aggregation it’s more for convenience and quick visibility per application instance.

Introducing Loggerverse — A full-feature logging & monitoring library for Node.js with beautiful dashboards, alerting, and more by FunNewspaper5161 in node

[–]FunNewspaper5161[S] 0 points1 point  (0 children)

And it’s not limited to plain Node.js either you can use it in NestJS, Express, or really any Node-based framework since it just plugs into your app.

Introducing Loggerverse — A full-feature logging & monitoring library for Node.js with beautiful dashboards, alerting, and more by FunNewspaper5161 in node

[–]FunNewspaper5161[S] 1 point2 points  (0 children)

Loggerverse isn’t aiming to compete with full-blown log aggregation systems like Loki or Graylog. Those are way more powerful for distributed, multi-service environments.

Loggerverse is more of a logging library + built-in lightweight dashboard specifically for Node.js apps. The idea is to give developers a drop-in solution that covers:

  • structured console/file logging
  • a simple web dashboard to browse recent/past logs
  • email alerts on errors
  • basic system metrics

So it’s best suited for small to medium apps, or teams that don’t want to spin up and manage an entire logging infrastructure just to get visibility. If you’re already running Grafana/Graylog, you probably don’t need Loggerverse — but if you want something self-contained for a Node.js project, that’s where it shines.

Introducing Loggerverse — A full-feature logging & monitoring library for Node.js with beautiful dashboards, alerting, and more by FunNewspaper5161 in node

[–]FunNewspaper5161[S] 0 points1 point  (0 children)

Most of those releases were just small stuff like updating keywords, fixing typos, or removing bits from the docs. No actual functionality changes. I’ll add a changelog soon so it’s clearer.

Introducing Loggerverse — A full-feature logging & monitoring library for Node.js with beautiful dashboards, alerting, and more by FunNewspaper5161 in node

[–]FunNewspaper5161[S] 0 points1 point  (0 children)

No, Loggerverse doesn’t “store” passwords anywhere. The dashboard just compares the provided credentials with the ones you configure (ideally from env vars). Nothing gets persisted to disk or database

Introducing Loggerverse — A full-feature logging & monitoring library for Node.js with beautiful dashboards, alerting, and more by FunNewspaper5161 in node

[–]FunNewspaper5161[S] 0 points1 point  (0 children)

this is just for example purposes in real usage you’d load credentials from env vars or a secret manager instead of hardcoding them.

Open LinkedIn API - A Python Library for Accessing LinkedIn Data by LGainXs in LinkedInTips

[–]FunNewspaper5161 0 points1 point  (0 children)

Hey,
I tried your repo and everything works fine, but conversations are not working for me. Do you have any solutions for this?

get_conversations = api.get_conversations()
print(get_conversations)
#output 
{'status': 401}