stanza VS leapp

Been a while since I looked into fluentd and elasticsearch but I heard Stanza (soon to be moved to the OpenTelemetry Collector) is meant to be a modern replacement for it, but seems it's still in it's early days.

And then they contacted some famous log collection projects such as the Fluent Bit and also others like Stanza as well as Syslog, I guess. And I didn't read the whole thread of the conversation around log collection. But now, they set the Stanza as the first implementation of OpenTelemetry logs. And in Stanza, the observIQ with Stanza is merged under the OpenTelemetry log repository, so that's the status. And then, they try to standardize the format of logs based on the Stanza format, such as what kind of information should be included in log.

observIQ is a hosted log management platform that's powered by our FOSS log agent, Stanza: https://github.com/observIQ/stanza. Stanza is lightweight and robust (written in Go), and can be configured to act as a Syslog receiver in about a minute (guided configuration in our app).

observIQ is a simple, cost-effective hosted log management platform designed with small teams in-mind. Log collection is powered by Stanza: https://github.com/observIQ/stanza , our high-performance OSS log agent. Stanza was also recently adopted as the official log agent of the CNCF's OpenTelemetry project. observIQ offers guided-installation, pre-made dashboards, threshold-based alerts, live tail and more.

We're a new hosted log management platform with simple, native support for gathering logs from Openshift. Deployment typically takes a few minutes. We also automatically enrich Openshift logs metadata like node, namespace, pod, container - no additional configuration required. Logs are gathered with your high-performance OSS log agent, Stanza: https://github.com/observIQ/stanza

We offer a super simple, hosted log management platform that allows you to easily ingest any syslog traffic by setting up high-speed OSS agent as a syslog receiver in just a few click (setup takes about 30 seconds). You can find more about our log agent here: https://github.com/observIQ/stanza

Self-promotion alert, my apologies: Check us out at observIQ: https://observiq.com/ We provide a super-simple host log management platform powered our high-performance OSS Log Agent, Stanza (https://github.com/observIQ/stanza). Average setup time is about 5 minutes, end-to-end. Our platform is designed with start-ups and small businesses in-mind and are priced about half as much as our competitors. Lastly, we offer 14-day free trial, but also offer a completely free plan that provides 3 gigs of ingestion/day and 3 day retention - with access to the full feature set of the platform (Dashboards, Alerts, Live Tail). Shoot me a message or chat if you have any questions!

Similarly, our platform will be rolling out this feature soon, and will utilize our lightweight FOSS log agent Stanza - written in Go. The agent may work for your project https://github.com/observIQ/stanza

Summary:

Do you find yourself overwhelmed with work, requests, or complaints and in need of assistance to alleviate the pressure, enhance communication, facilitate organization, prioritize tasks, and foster greater trust and transparency?

Alternatively, I can work as a full stack developer.

AWS Community builder, AWS User group Leader, public speaker (https://www.youtube.com/watch?v=qdu58NAQfU0&t=271s)

Or perhaps you need both? =)

I have 4+ years of experience as a product manager and 8 in product development (before pm: agile coach, UX designer, and developer).

I've been the co-founder of the open-core company behind the OSS project Leapp (https://github.com/Noovolari/leapp)

Please feel free to reach out.

You can switch to saml2aws using the browser method instead of the Okta method and it will continue to work after the upgrade. There is also a really neat GUI tool to manage your session tokens that also works. https://www.leapp.cloud

Take a try to Leapp: https://github.com/Noovolari/leapp

Hello everyone, I'm the maintainer of an open-source DeveloperTool (https://github.com/Noovolari/leapp)

With a heuristic of 7000 users daily, I started feeling the need to have more information on how Users are using the project to improve it.

Is it the right thing to do to create a better Developer Experience and gain feedback for the end users?

On a side:

- For all your employees I can advice you Leapp as open-source project (https://github.com/Noovolari/leapp). It solve mayor of the problem listed here:

I am looking to manage Leapp (https://www.leapp.cloud/) from the StreamDeck. Leapp allows you to manage and switch between different Cloud Accounts (AWS, Azure, etc). Leapp has a command line interface which I could automate with a StreamDeck plugin. Unfortunately it looks like the only official SDK is the sandboxed JavaScript one. This means I cannot automate command line tools with it.

If you’re wondering if there is a tool that allows you to stop thinking about AWS credentials and where to store them in the right way, give a look at Leapp! It takes the responsibility of storing long-term credentials in the system vault, generating/refreshing short-term credentials, and placing them in the right place for the clients to use them.

Still, there is an elementary problem that we need to address, and it’s more on the operational side of things. Once we secured and implemented a tremendous multi-account strategy, how do people access AWS accounts? It turns out there is a fantastic open-source tool that lets you handle that with no effort, and its name is Leapp.

When you have to configure access to multiple AWS accounts using the Assume Role access pattern, it becomes difficult to get rid of all the Named Profiles configuration data and relationships. When you’ve to deal with a complex access scenario, tools like Leapp (https://www.leapp.cloud) come to the rescue! Leapp avoids you to specify relationships between Named Profiles in the config file, as the access methods are stored in the tool-specific configuration file.

Leapp Github repository