News for hackers. Stuff that matters.
Re:Grafana, Loki, and Tempo will be relicensed to AGPLv3 by jabiko on Tuesday April 20, 2021 @01:33PM (#26877712)
Even though we use Grafana only internally and there would be no problem with AGPLv3 in theory I see big meetings with legal coming up which might result in us not being able to use it anymore.

I could image that its the same with other corporations. In the end that might hurt the popularity of Grafana quite a lot.

Re:Grafana, Loki, and Tempo will be relicensed to AGPLv3 by jchw on Tuesday April 20, 2021 @02:45PM (#26879259)
While many are dismissing your concerns, I do think this is a valid point, at least to some degree. For example, Google institutes a blanket ban on all AGPL code:

https://opensource.google/docs/using/agpl-policy/

Now, one can read into why exactly this may be, though I have a strong feeling it is simply due to the fact that enforcing correct use of the license is harder than usual. Even if you use it alongside only compatible licenses, like GPLv3, it presumably would make the entire distribution subject to AGPLv3 restrictions. GPLv3 virility is a little easier to deal with, and of interesting note the Bazel build system contains some awareness of licenses.

https://docs.bazel.build/versions/0.24.0/be/functions.html#l...

On the other hand, one might view this as a benefit. So, I guess it depends on who you ask, really. It's not clear that big corporations would necessarily have an easier time with SSPL or TSL either.

Note: IANAL, please do not take my understanding of how these software licenses work as fact :)

Re:Grafana, Loki, and Tempo will be relicensed to AGPLv3 by raegis on Tuesday April 20, 2021 @03:20PM (#26879992)
I suspect this is not a popular opinion, but Google's AGPL policy reads like FUD to me. From the first paragraph:

"...extremely difficult for Google to comply with..."

and

"...presents a huge risk to Google..."

and later in the document is the best part:

"This viral effect requires that the complete corresponding source code...".

All from a company which built itself on GPL software. This reminds me of Steve Ballmer ranting about Linux being a virus 20 years ago.

More:

"Do not install AGPL-licensed programs on your workstation, Google-issued laptop, or Google-issued phone without explicit authorization from the Open Source Programs Office."

Assuming Google follows its own policy, this just creates a hassle for its employees. Worse, Google making this public sends a strong anti-AGPL message to other companies. I'd bet $10 RStudio server (AGPL) is installed somewhere at Google (perhaps the commercial version). But other organizations with less sophisticated legal departments might just ban RStudio completely following Google's lead. I would not call Google irresponsible here, but I think it could act more responsibly.

Re:Grafana, Loki, and Tempo will be relicensed to AGPLv3 by gpanders on Tuesday April 20, 2021 @05:04PM (#26881651)
Re:Grafana, Loki, and Tempo will be relicensed to AGPLv3 by jeffbee on Tuesday April 20, 2021 @05:31PM (#26882018)
On the one hand you have a large department of battle-hardened IP lawyers who say that AGPL virality is overbroad and poorly defined, and on the other hand you have a FOSS advocate who says it's fine, so I guess we'll never know for sure!
Re:Grafana, Loki, and Tempo will be relicensed to AGPLv3 by josephcsible on Tuesday April 20, 2021 @05:51PM (#26882283)
The FSF and other similar organizations have lawyers too. What do you think their opinion is?
Re:Grafana, Loki, and Tempo will be relicensed to AGPLv3 by jeffbee on Tuesday April 20, 2021 @06:17PM (#26882599)
The FSF is not generally a party to the license, so it makes no difference what they think.
Re:Grafana, Loki, and Tempo will be relicensed to AGPLv3 by matkoniecz on Wednesday April 21, 2021 @02:52AM (#26886186)
> AGPL virality is overbroad

Going against interest of Google (and similar companies) is one of main points of AGPL, so this indicated that it works as intended!

Re:Grafana, Loki, and Tempo will be relicensed to AGPLv3 by kavalg on Wednesday April 21, 2021 @05:09AM (#26887068)
Yep, but guess who will win corporate argument inside the company. You may advocate as much as you like, but no legal person will approve the general use of the software in the company. I guess some companies, like Amazon will find their way around the license and still be able to offer it as a service under commercial terms, but not the average Joe in the corporate world.
Re:Grafana, Loki, and Tempo will be relicensed to AGPLv3 by 188201 on Tuesday April 20, 2021 @01:46PM (#26877950)
I think that's misunderstanding of AGPL. For internal use, AGPL does not require to share the proprietary part.

If a company develop an proprietary UI and use Loki as backend, this is not serving Loki directly to customer, so that does not require company to release their code.

It is similar to GPL. Dynamic linking to a GPL software does not require the developer releasing their code.

Only provider serving Loki instance directly to customer required to share the code.

Only Amazon is upset that they cannot just host a popular open source project directly on their cloud. Maybe they could pay a license fee for dual licensing arrangement, which is a better way to support open source startup.

Re:Grafana, Loki, and Tempo will be relicensed to AGPLv3 by btown on Tuesday April 20, 2021 @02:08PM (#26878420)
I think this is a misunderstanding of how vague the AGPL actually is.

The key clause is "your modified version must prominently offer all users interacting with it remotely through a computer network (if your version supports such interaction) an opportunity to receive the Corresponding Source of your version."

Would putting AGPL software behind a reverse proxy change the fact that you're a user interacting with it remotely? What about a reverse proxy that changes/adds some headers? What about a really smart reverse proxy that reformats some of the output or repackages it or mixes it with things from other data sources? Is that materially different from the API that powers the "proprietary UI" you're describing?

And say you're pretty confident that you're on the right side of things. Can you point to any case law where courts have established precedent about what "interacting with it remotely" means in this context? No? Then to be on the safe side, you'll probably need to maintain a source code repository for your Corresponding Source, remember to update it every time you update a minor version of the service internally, and maintain an info screen in your product with "prominent" links to that source code repository, which likely means it needs sign off from a product team if not a legal team as well. All things that add expense and barriers to entry.

I think the AGPL is great for services like Grafana's UI itself, where there's likely to be a "human gap" between the software and anyone outside your organization. But things like Loki that are designed to power other proprietary systems that may well be touched by end users through a computer network, where Loki's output may have influence or side effects on the output the user sees? I don't think it's nearly as clear what liability that entails.

(Obligatory: Not a lawyer, the above is not legal advice.)

Re:Grafana, Loki, and Tempo will be relicensed to AGPLv3 by PeterisP on Tuesday April 20, 2021 @02:23PM (#26878766)
Most companies who use Grafana or Loki as part of some deployment would use an unmodified version, so the only AGPL specific clause, which you cite, would not apply and is irrelevant.
Re:Grafana, Loki, and Tempo will be relicensed to AGPLv3 by rlpb on Tuesday April 20, 2021 @08:42PM (#26883986)
This kind of hand-wringing is what the naysayers were doing with GPL software in the 90s. That the GPL would never fly in business because lawyers would get hung up in "what if" interpretations that were never the intent or spirit of the GPL in the first place.

It turned out alright.

Re:Grafana, Loki, and Tempo will be relicensed to AGPLv3 by p_l on Wednesday April 21, 2021 @04:54AM (#26886971)
Not really. GPLv2 had more sensible legal language, even if that turned out to burn FSF intentions at times, but over time lawyers started digging in more into "derivative software" clause. Also a lot of the naysayers were fueled by RMS himself doing whack a mole by forcing projects to adopt GPL in not nice manner (and I'm not talking about them using something big or critical from GPL project).

TL;DR FSF is heavily responsible for the "GPL is viral" message sticking.

Re:Grafana, Loki, and Tempo will be relicensed to AGPLv3 by Thaxll on Tuesday April 20, 2021 @02:36PM (#26879046)
And 99.99% of users don't modify the code so it's irrelevant.
Re:Grafana, Loki, and Tempo will be relicensed to AGPLv3 by Rapzid on Tuesday April 20, 2021 @02:18PM (#26878648)
I don't understand the point you're trying to make with the reverse proxy as it doesn't seem related to anything the parent wrote.
Re:Grafana, Loki, and Tempo will be relicensed to AGPLv3 by btown on Tuesday April 20, 2021 @02:26PM (#26878819)
Sure! Saying that the parent’s “develop an proprietary UI and use Loki as backend” is a slippery slope to “user sees data that incorporates data served from Loki” which I am arguing could be interpreted as data that would require the developer to maintain a source repository for Loki under the AGPL.
Re:Grafana, Loki, and Tempo will be relicensed to AGPLv3 by Rapzid on Tuesday April 20, 2021 @02:32PM (#26878974)
I see now and yes the AGPL seems vague in that regard.

If it's anything like dynamic linking and GPL that could be considered okay even if it's not the intention of the licensee. Seems like the license should be more explicit about what "interacting with" entails.

Re:Grafana, Loki, and Tempo will be relicensed to AGPLv3 by Dylan16807 on Tuesday April 20, 2021 @09:16PM (#26884274)
> that would require the developer to maintain a source repository for Loki under the AGPL.

Is that a problem? Fork it on github, and update the repository every once in a while or upon request.

Re:Grafana, Loki, and Tempo will be relicensed to AGPLv3 by rhaps0dy on Tuesday April 20, 2021 @02:14PM (#26878576)
> Dynamic linking to a GPL software does not require the developer releasing their code.

That's not true, you do have to release the code. There is no difference between statically or dynamically linking to a GPL library. Source: https://www.gnu.org/licenses/gpl-faq.html#GPLStaticVsDynamic

You may be thinking of the LGPL.

Re:Grafana, Loki, and Tempo will be relicensed to AGPLv3 by gpanders on Tuesday April 20, 2021 @05:01PM (#26881609)
Not everyone agrees on this point [1]. One relevant quote: "This is ultimately a question not of the GPL per se, but of how copyright law defines derivative works."

Whether or not dynamic linking constitutes a "derived" work is still an open question, legally speaking. Obviously the FSF has their own thoughts on this, but it's unclear how an actual court would rule.

(IANAL, this is not legal advice, etc. etc.)

[1]: https://en.wikipedia.org/wiki/GNU_General_Public_License#Lin...

Re:Grafana, Loki, and Tempo will be relicensed to AGPLv3 by zmmmmm on Tuesday April 20, 2021 @09:15PM (#26884268)
That may be true, but a state of ambiguity is as good as saying its covered by GPL ... no organisation is going to look at that and say "that's fine, let's use it".

In fact, state of ambiguity is the worst for everyone because neither will users be able assume they can exercise their free software rights. So everyone loses.

Re:Grafana, Loki, and Tempo will be relicensed to AGPLv3 by tamalsaha001 on Tuesday April 20, 2021 @02:05PM (#26878355)
That does not seem to be the case. From [1]

The difference between the AGPL and traditional GPL is simple: The AGPL seeks to close a "loophole" that allows a company or organization to modify GPL'ed software and use it to provide a service — but without actually distributing changes. So a company can take a package like, say, WordPress and modify the software significantly to sell a service — but hold back changes because it's not technically "distributing" or "propagating" the software. The AGPL goes a bit further and says that if the program is "intended to interact with users through a computer network" and if the version that you received gives users "the opportunity to request transmission to that user of the Program's complete source code," you have to maintain that functionality and distribute the modified version.

[1] https://www.networkworld.com/article/2229265/is-the-affero-g...

Re:Grafana, Loki, and Tempo will be relicensed to AGPLv3 by rasz on Tuesday April 20, 2021 @02:24PM (#26878793)
Wasnt this solved with GPLv3 anti tivoization rules?
Re:Grafana, Loki, and Tempo will be relicensed to AGPLv3 by tzs on Tuesday April 20, 2021 @04:04PM (#26880768)
The anti-tivoization rules only apply if:

1. the software is conveyed in a "User Product", and

2. that conveyance occurs as part of a transaction in which the right of possession and use of that product is transferred to the recipient.

A "User Product" is defined as 'either (1) a “consumer product”, which means any tangible personal property which is normally used for personal, family, or household purposes, or (2) anything designed or sold for incorporation into a dwelling'.

In other words, it only covers software that is installed on actual physical hardware when that hardware is sold (or rented, etc) to the consumer.

For a sale of a service, it is completely out of scope.

This is probably the most misunderstood clause in GPLv3, with people thinking that it some sort of general anti-DRM clause. Almost everybody, for example, thinks that it is why you can't have GPLv3 code on the Apple app store, but because it only applies to conveyances that are part of the transaction by which you acquire your iPhone or iPad it in fact does not apply to software purchased later from the app store. Apple's app store DRM is perfectly compatible with GPLv3.

The incompatibility between the app store and GPL is that the license agreement for the app store says you won't redistribute the app or reverse engineer it. GPL does not allow adding additional license restrictions like that, and so you can't satisfy both the app store license and GPL.

Re:Grafana, Loki, and Tempo will be relicensed to AGPLv3 by pabs3 on Wednesday April 21, 2021 @01:38AM (#26885787)
Related note: the GPLv2 also requires users to be able to reinstall the software:

https://sfconservancy.org/blog/2021/mar/25/install-gplv2/

Re:Grafana, Loki, and Tempo will be relicensed to AGPLv3 by detaro on Tuesday April 20, 2021 @02:26PM (#26878829)
How would the anti-tivoization rule that discusses physical products apply to a service?
Re:Grafana, Loki, and Tempo will be relicensed to AGPLv3 by atat7024 on Tuesday April 20, 2021 @02:35PM (#26879029)
> I think that's misunderstanding of AGPL.

That's GPs point.

Re:Grafana, Loki, and Tempo will be relicensed to AGPLv3 by klintcho on Tuesday April 20, 2021 @01:51PM (#26878056)
This might be the case. However there is an additional risk and process component:

- you might not want to risk because you don't have lawyers etc in your company.

- even if you have lawyers etc in your company, if there are 2 alternatives one which is just an MIT license, you'll probably go for that one because you don't want to have a 1.5 month review of the use of this AGPL licensed alternative.

In general things like this https://github.com/xdspacelab/openvslam/wiki/Termination-of-... (repo with 3k stars), an effort terminated because of some traces of GPL code MIGHT be somewhere in there comes to light. Even though Grafana etc are mostly tools, for my startup I would probably not risk any of this (for my own sake and also for any kind of due diligence in case it ever gets acquired)

Re:Grafana, Loki, and Tempo will be relicensed to AGPLv3 by aulin on Tuesday April 20, 2021 @02:41PM (#26879163)
did not follow the events of openvslam, wouldn't they be required to still release the source code of the previously public version as GPL? also once the doubt is there, why not rerelease as GPL?
Re:Grafana, Loki, and Tempo will be relicensed to AGPLv3 by catlifeonmars on Wednesday April 21, 2021 @03:25AM (#26886403)
In my experience a lot of legal departments will block off entire classes of licenses just to be on the safe side.
Re:Grafana, Loki, and Tempo will be relicensed to AGPLv3 by jpalomaki on Tuesday April 20, 2021 @03:19PM (#26879958)
How does this actually work towards your employees or 3rd party personnel (for example consultants) getting access to the tools - would you have to make the source code available for them and allow them to distribute the code?
Re:Grafana, Loki, and Tempo will be relicensed to AGPLv3 by josephcsible on Tuesday April 20, 2021 @03:47PM (#26880451)
A company giving its own employees access to software for work use only doesn't count as distribution, but giving it to contractors can: http://www.gnu.org/licenses/gpl-faq.en.html#InternalDistribu...
Re:Grafana, Loki, and Tempo will be relicensed to AGPLv3 by jpalomaki on Tuesday April 20, 2021 @05:14PM (#26881790)
AGPL uses the wording "all users interacting with it remotely through a computer network".
Re:Grafana, Loki, and Tempo will be relicensed to AGPLv3 by ezoe on Tuesday April 20, 2021 @09:51PM (#26884503)
But think about it. Anyone that use AGPLv3 software can demand the AGPLv3 license, including employees and contractors. Once they got it, they can freely publish it to the public because it's AGPLv3. Forcing NDA to not leak it to the public doesn't work here because it violate AGPLv3 license thus copyright infringement.
Re:Grafana, Loki, and Tempo will be relicensed to AGPLv3 by drdaeman on Tuesday April 20, 2021 @02:20PM (#26878702)
Cannot be helped - that's just fear of the unknown.

If legal is familiar with AGPL, like they are with GPL, BSD or Apache, they should see no issue. This change does not really affect anyone except for the very small number of people/companies that make their own changes to software and make this software available online to others.

If you aren't such a company and legal would still say you guys can't use e.g. Grafana anymore... the truth will be that it's some incompetent (or severely underhanded, where they can't do any research and err on the side of caution) legal department, failing at their jobs.

Re:Grafana, Loki, and Tempo will be relicensed to AGPLv3 by gen220 on Tuesday April 20, 2021 @02:27PM (#26878839)
Many devs at Google routinely use GPLv3 code, in GNU Emacs, to make an example.

Unless you’re repackaging Grafana into an app bundle for customers to use, there’s no violation occurring here, right?

Re:Grafana, Loki, and Tempo will be relicensed to AGPLv3 by kevincox on Tuesday April 20, 2021 @03:28PM (#26880125)
GPL and AGPL are very different here.

If a developer uses GPL Emacs to write a server that uses GPL libraries and Google runs that sever in their datacenter it is very clear that Google doesn't have to release any source code.

However Google's argument is that if they make a web application that uses AGPL MongoDB as a backend it is unclear if 1. The user is interacting with MongoDB over a network and 2. do they need to release the code of their server.

It appears that the answers are 1. Yes and 2. No but apparently Google isn't confident to use that in court. (Or at least they don't see enough benefits for that risk)

Re:Grafana, Loki, and Tempo will be relicensed to AGPLv3 by dvfjsdhgfv on Tuesday April 20, 2021 @01:45PM (#26877929)
In a large number of cases, this is not an issue at all. Just like we all use GPL-ed kernel and a ton of other stuff. There is also no problem with making AGPL-based services available to customers. The caveat is that when you modify AGPL-based code, you need to make the source of these modifications available, too. For some reason, this scares Amazon a lot. Developers know that and use AGPL when they don't want to be screwed by AWS.
Re:Grafana, Loki, and Tempo will be relicensed to AGPLv3 by Iolaum on Tuesday April 20, 2021 @02:24PM (#26878785)
If Amazon was really scared of AGPL then MongoDB wouldn't need to relicense.
Re:Grafana, Loki, and Tempo will be relicensed to AGPLv3 by pritambaral on Tuesday April 20, 2021 @04:40PM (#26881326)
This is a myth that has been repeated far too often. Amazon had made no move on MongoDB _until MongoDB started using the SSPL_. No hosted-MongoDB, no MongoDB-derived products, nothing.

MongoDB Inc. instead went after much smaller companies, like mLab, holding their future hostage and thus strong-arming them to sell themselves to MongoDB Inc. a short while before they announced the monopolistic license change that would have effectively shut those small companies down anyway.

Frankly, I'm tired of hearing this myth. MongoDB would like you to believe they were David in a fight against Goliath — PR and marketing have always been their strong suit — but they were quite happy playing Goliath themselves while pointing fingers at imaginary Goliaths.

Re:Grafana, Loki, and Tempo will be relicensed to AGPLv3 by jsdwarf on Tuesday April 20, 2021 @02:10PM (#26878487)
I don't get why Amazon should be scared by AGPL. I mean all of their services run on GPLed Linux, why should they be scared by a GPLed Grafana?Even if they had to open-source their Grafana contributions, they could do this in a way that they are worthless for potential competitors (e.g. if the contribution depends on a proprietary Amazon system)
Re:Grafana, Loki, and Tempo will be relicensed to AGPLv3 by yorwba on Tuesday April 20, 2021 @02:37PM (#26879069)
> they could do this in a way that they are worthless for potential competitors (e.g. if the contribution depends on a proprietary Amazon system)

That is not allowed.

"""The "Corresponding Source" for a work in object code form means all the source code needed to generate, install, and (for an executable work) run the object code and to modify the work, including scripts to control those activities. However, it does not include the work's System Libraries, or general-purpose tools or generally available free programs which are used unmodified in performing those activities but which are not part of the work. For example, Corresponding Source includes interface definition files associated with source files for the work, and the source code for shared libraries and dynamically linked subprograms that the work is specifically designed to require, such as by intimate data communication or control flow between those subprograms and other parts of the work."""

(Emphasis on that last part mine.)

"""Notwithstanding any other provision of this License, if you modify the Program, your modified version must prominently offer all users interacting with it remotely through a computer network (if your version supports such interaction) an opportunity to receive the Corresponding Source of your version by providing access to the Corresponding Source from a network server at no charge, through some standard or customary means of facilitating copying of software."""

If Amazon modifies Grafana so it depends on a proprietary Amazon system, the source code for that system is included in the Corresponding Source, and if they allow users to interact with that modified version, they need to provide them with access to the proprietary system's source code.

Re:Grafana, Loki, and Tempo will be relicensed to AGPLv3 by bboreham on Tuesday April 20, 2021 @01:41PM (#26877854)
Would you consider paying for a licence to use it?
Re:Grafana, Loki, and Tempo will be relicensed to AGPLv3 by t-writescode on Tuesday April 20, 2021 @04:18PM (#26881001)
If I was in charge of the money, assuming it’s a reasonable price for on-prem Grafana, I would pay for a license to Grafana, just to not have the licensing stress.
Re:Grafana, Loki, and Tempo will be relicensed to AGPLv3 by jabiko on Tuesday April 20, 2021 @01:49PM (#26878011)
Honestly, I have no idea.

I think if there would be a possibility to pay money to have what we are doing reviewed by Grafana and be "certified" to be withing what they consider acceptable under the AGPL that might actually be a good option

Re:Grafana, Loki, and Tempo will be relicensed to AGPLv3 by bboreham on Tuesday April 20, 2021 @01:52PM (#26878070)
What about just paying for a commercial licence to use it to meet your needs?
Re:Grafana, Loki, and Tempo will be relicensed to AGPLv3 by jabiko on Tuesday April 20, 2021 @02:02PM (#26878270)
I have no Idea. Realistically its probably not the license cost but the one time and the perpetual operational overhead associated with the license that's going to be the problem.
Re:Grafana, Loki, and Tempo will be relicensed to AGPLv3 by peterbonney on Tuesday April 20, 2021 @02:14PM (#26878575)
That makes zero business sense. Your first post is about the one time and perpetual operational overhead associated with operating under the prior FOSS license (yes, you’re saying it’s the new license that’s a problem, but since the situation arose while operating under the prior conditions then implicitly those conditions carried this very overhead). Operating under any license carried an overhead, unless you simply choose to not read (or to read and ignore) the fine print.
Re:Grafana, Loki, and Tempo will be relicensed to AGPLv3 by jabiko on Tuesday April 20, 2021 @02:56PM (#26879504)
> Your first post is about the one time and perpetual operational overhead associated with operating under the prior FOSS license

My first post is about the fact that even though the planned use case would be 100% compliant to the AGPLv3 license the fear that is associated with that license could prevent such use.

> That makes zero business sense

Purchasing a license in that case while not strictly necessary might be seen as an insurance. So that makes business sense.

In the end though I highly doubt that's whats going to happen. The most likely outcome is that we just get told to get rid of Grafana and use something else.

Re:Grafana, Loki, and Tempo will be relicensed to AGPLv3 by peterbonney on Tuesday April 20, 2021 @03:28PM (#26880126)
> In the end though I highly doubt that's whats going to happen. The most likely outcome is that we just get told to get rid of Grafana and use something else.

Whatever you replace it with will have the same licensing overhead. Again, this makes no sense.

If you said we can’t afford to pay for it, fine. But you explicitly said you don’t think cost is an issue.

Maybe I’m making the wrong inference, but it sounds like you’re afraid your higher ups just don’t want to have any restrictions placed on whatever business need it is that Grafana is filling for you. If I haven’t misunderstood that fear, then I regret to say that any software product other than one you build and maintain yourselves will come with some restrictions or the possibility of future restrictions.

When I say this makes no business sense, that’s what I’m trying to get at: other than (potentially) licensing cost, any Grafana substitute will come with the same issues, plus switching costs. So unless there is a FOSS product that provides a better solution to your problem, by definition switching will be more costly than maintaining status quo.

Or am I missing the point?

Re:Grafana, Loki, and Tempo will be relicensed to AGPLv3 by sokoloff on Wednesday April 21, 2021 @05:04AM (#26887045)
I think you’re getting the essential facts but drawing a conclusion that is still wrong, at least for some people/companies.

“What can I do with Grafana in my business under GPL?” is much more clearly defined than the same question changing only the last word to AGPL. Alternatives available under Apache v2 or other non-copyleft licenses are also clear. For GPL, all I need to be careful to avoid doing is distributing the software and I’m in a well-understood situation.

It’s this closing off of futures unknown but possible that is markedly worse under AGPL. Anything that you’re doing today that could apply externally as well seems to be an area where a decision to continue to follow Grafana tip could bite you. And not updating could also bite you. Grafana will lose contributors and users over this. All of that I’m sure Grafana considered and made the best choice for Grafana.

Re:Grafana, Loki, and Tempo will be relicensed to AGPLv3 by peterbonney on Thursday April 22, 2021 @06:52PM (#26909092)
Losing users and contributors, sure.

Losing users who would otherwise be willing to pay for a commercial license (as the OP said they are) that could be negotiated to explicitly cover whatever future use case they’re concerned about? That makes no sense.

Re:Grafana, Loki, and Tempo will be relicensed to AGPLv3 by globular-toast on Tuesday April 20, 2021 @01:38PM (#26877808)
There should be no problem with it even if you use it externally. It's about time companies stopped seeing open source as freely exploitable. Every company that uses open source software should be obliged to contribute, or pay for proprietary software.