+1
Thanks Christian
Scott
On 2/12/24, Christian Grobmeier wrote:
> Hello,
>
> This vote is to put Chainsaw to the "Dormant" components. There is much work
> to be done on this component, but not enough hours can be committed to do
> that work. To reflect this situation to the user, it is better
Thank you for spending time working on it Christian.
I started contributing to Chainsaw in 2003. I agree. It's time.
The primary benefit of Chainsaw was its built-in support for real-time
tailing of ssh-accessible pattern-layout based logs - something
Kibana doesn't support well, and something n
That's great!
Global app settings used to be loaded on startup and saved on exit.
LogPanel-specific settings were persisted on exit and loaded on
startup on a per-tab-name basis, mostly using LogPanelpreferenceModel.
There are a few preferences I'd like to restore - the tab-expression
event rout
I'll go through the UI and re-add small features that I think are
critical but were lost in the log4j1-jettison effort.
I'll follow-up in a new thread.
Scott
On 11/28/23, Scott Deboy wrote:
> I've fixed the logger tree split pane UI (left artifacts when you
>
28/23, Christian Grobmeier wrote:
> Hi Scott,
>
> I believe you; thanks for speaking up and being around.
>
> How can I help?
>
> I think Chainsaw needs to see a release soon, so what can I do to help you?
>
> I am glad to clean up things and whatever is necessary.
>
I have dropped the ball here, but will commit to working on this, this year.
I want to preserve a bunch of what can be done in the
https://github.com/apache/logging-chainsaw/tree/chainsaw-with-log4j1-dep
branch, and some of that just isn't possible because equivalent
functionality was never added
user hook things up - some sort of
> visual programming/flow-based view would be very cool but also very
> complicated.
>
> -Robert Middleton
>
> On Mon, Oct 9, 2023 at 3:24 PM Christian Grobmeier
> wrote:
>>
>> On Sun, Oct 8, 2023, at 23:19, Scott Deboy wrote:
>
rmat for storing properties.
>
> I am not sure what the status currently is, if Scott is still working on
> it :) I could also make some kind of proposal or so for storing properties
>
> On Tue, Oct 3, 2023, at 01:20, Scott Deboy wrote:
> > I think persisting to json format makes se
be commented.
>> >>>>> I didn't remove those things yet, as they seemed to big and I
>> >>>>> didn't
>> >>>>> understand well how they'd work or how I would test (I lack the
>> >>> knowledge
>> >>>>> of ho
thank you, its easy to track):
>>>
>>> https://github.com/apache/logging-chainsaw/commit/75bedf98665188eef4d13e4bfbb4b0dae456f65e
>>>
>>> One question: why did we remove Xstream? it seem there was an update
>>> late
>>> 2022 to address some security.
>>> Should we ju
I pushed branch "chainsaw-with-log4j1-dep" representing the working
log4j1 code for those that want to easily see what used to exist.
I'll probably selectively incorporate pieces from that branch into master.
On 10/1/23, Christian Grobmeier wrote:
>
> On Sun, Oct 1, 2023,
Middleton
>
> On Sun, Oct 1, 2023 at 3:14 PM Christian Grobmeier
> wrote:
>
>> On Sun, Oct 1, 2023, at 20:59, Scott Deboy wrote:
>> > It's great to see the contribution, thanks Christian!
>> >
>> > I pulled down latest master and it looks like there are
t log4j2-supporting feature.
Scott
On 10/1/23, Scott Deboy wrote:
> It's great to see the contribution, thanks Christian!
>
> I pulled down latest master and it looks like there are some UI
> glitches we should fix - for example, resizing the logger tree pane
> doesn't
It's great to see the contribution, thanks Christian!
I pulled down latest master and it looks like there are some UI
glitches we should fix - for example, resizing the logger tree pane
doesn't render correctly.
As I mentioned before, I assume there are a bunch of features we lost
when we moved f
+1 to everything Ralph said.
On Fri, Sep 29, 2023, 3:53 PM Ralph Goers
wrote:
> I’m sorry, I can’t really agree with much of any of this. Following the
> thoughts being proposed in this thread much of Log4j 2 and even the initial
> work I did to create it would not have seen the light of day. Al
I think Robert commented out most of that to get rid of the log4j1
dependency. I'm slightly concerned we'll lose a ton of UI
functionality in that process, but it's in history if it's still
needed, so delete away if you'd like.
For comparison, you can look at the 'chainsaw-with-log4j1-dep' branch.
This is a log4j2 feature.
Scott
On Fri, Sep 29, 2023, 12:24 PM Christian Grobmeier
wrote:
> Volkan asked this question here:
> https://github.com/apache/logging-chainsaw/issues/24
>
> I guess, since Log4j1 is EOL we can safely remove this feature, right?
>
There should be a default config. Do you have anything in the .chainsaw
directory? If so, delete it.
On Fri, Sep 29, 2023, 9:49 AM Christian Grobmeier
wrote:
> OK, got it running, after commenting those lines:
>
> //statusBar.setSelected(config.getBoolean("statusBar"));
> statusBar.setSelected(f
how up as green by default.
The UI supports multiple tabs (log sources) and will live tail for you as
well.
Note the search results show up as blue in the log panel, and the gutter on
the right displays the individual line colors (black is a search match).
On Mon, Sep 25, 2023 at 8:46 PM Sco
ne instead of a table, so that fields do not get cut
> off(like they currently do in the table) and it can better scroll like a
> real terminal when new messages come in. Right-clicking will open up a
> pop-up menu contextually depending on what it is you have clicked on(the
> tim
Please review the various display setting controls. Most of what you
mention can be toggled from visible to hidden.
VfsLogFilePatternReceiver does exactly what you're describing. Allowing
live remote tailing of logs over an ssh accessible path.
You control if these logs end up in separate tabs or
gt;
> -Robert Middleton
>
> On Fri, Sep 22, 2023 at 10:30 AM Scott Deboy
> wrote:
>
> > -1
> >
> > While changes may be infrequent, the project is still useful and works
> > well. I'll continue to contribute to maintenance.
> >
> > Scot
-1
While changes may be infrequent, the project is still useful and works
well. I'll continue to contribute to maintenance.
Scott
On Thu, Sep 21, 2023, 10:00 AM Volkan Yazıcı wrote:
> As earlier discussions[1] indicate, Chainsaw has been lacking on
> maintenance and no PMC member stepped up to
hat they can build a project that passes all their
> security scans.
>
> Ralph
>
> > On Sep 19, 2023, at 11:26 AM, Scott Deboy wrote:
> >
> > Ralph,
> >
> > I already removed the socket appender vulnerability. I believe that was
> the
> > onl
b Issues for Chainsaw AFAIK.
> Both of these need to be addressed if the project is going to be considered
> active. Are you willing to help with both of these?
>
> Ralph
>
> > On Sep 19, 2023, at 3:25 AM, Scott Deboy wrote:
> >
> > Well, it still works we
Well, it still works well, and real time log analysis and Chainsaw's
support for filtering are very powerful for many dev-local use cases.
User base I can't speak to, but I agree based on lack of questions it's
probably very low to non-existent.
I'd prefer we find an option that isn't "nuke it fr
ould be helpful if you have time Scott would be a
>> manual on how to use Chainsaw and the features that it has. I
>> understand it enough now, but for people first trying to use it there
>> isn't really any good documentation.
>>
>> -Robert Middleton
>>
>&
Looks great!
It's a lot of work for sure - lots more to do to fully remove log4j1 -
custom level support (java.util.logging and Android for example),
support for UI-based interactions for some receivers(activateOptions),
and the loggerRepository extension pieces.
I definitely want to see VFSLogFi
Arbitrary text formats are already supported in Chainsaw -files can be
tailed locally or remotely (ssh) via a receiver that leverages Commons
VFS:
https://logging.apache.org/chainsaw/2.x/apidocs/org/apache/log4j/chainsaw/vfs/VFSLogFilePatternReceiver.html
The receiver supports the common pattern
Chainsaw Mac integration leverages java9 features now (Mac prefs menu
integration). I can review merge requests.
On Sat, May 8, 2021, 11:19 AM Matt Sicker wrote:
> It appears that Chainsaw updated its minimum Java version to 9. I'll
> get that fixed in the Jenkins build. As for committing the re
I've repaired the Mac UI integration and I think it's time to make a release.
I'm not sure of the process, it's been forever.
'mvn clean site:site package' works fine for me on my Mac, including
DMG creation.
I'd like to get the DMG available to folks for download.
Happy to help,
Thanks,
Scot
I'll work to get that Chainsaw release out.
On 2/9/21, Davyd McColl wrote:
> Hi Matt
>
> log4net has been quite quiet over the last quarter, partly because I took a
> break from all things code for a month, and partly because I'm still trying
> to pick up momentum after that break!
>
> However, t
al) should use an allowlist of deserializable classes.
> > > That's what we did in log4j2's serialized log event receiver code a
> > > few years ago, for example:
> > > https://github.com/apache/logging-log4j2/commit/5dcc192
> > > (CVE-2017-5646).
> &
eneral) should use an allowlist of deserializable classes.
> > That's what we did in log4j2's serialized log event receiver code a
> > few years ago, for example:
> > https://github.com/apache/logging-log4j2/commit/5dcc192
> > (CVE-2017-5646).
> >
> > On
I assume reverse-connect is still fine (SocketHubAppender/Receiver),
as Chainsaw is being configured to reach a specific (assumed trusted)
endpoint, yes?
On 11/6/20, Scott Deboy wrote:
> Holy cow. February?
>
> I have zero problem with us nuking the object serialization receiver
>
Updated to version 3 of the parent pom and clean site:site package
runs fine, pushed to master.
On 11/7/20, Matt Sicker wrote:
> Looks like we need to either fix this pom or the parent pom.
>
> On Fri, Nov 6, 2020 at 21:34 Mr. Jenkins
> wrote:
>
>> *BUILD FAILURE*
>> Build URL
>> https://ci-buil
wrote:
> Great to hear from you again! I don’t know if you saw it but there is a
> Chainsaw related email on Feb 12 of this year in the private list that you
> should take a look at if you are planning on doing some work on Chainsaw.
>
> Ralph
>
> > On Nov 6, 2020, at 5:5
Hey all,
Long time.
I decided to work through the pom ugliness and a couple of swing
degradation issues in Chainsaw.
I found an ASL2 Mac dmg creation maven plugin, and it works well on my
Mac, if anyone cares to try it out please do.
Pushing changes to master shortly.
ide a profile. Do you know how? I only discovered this issue when
> writing the Jenkinsfile since I build it on macOS locally (and while
> releasing).
>
> On 15 March 2018 at 14:58, Scott Deboy wrote:
>
>> Hi Matt,
>>
>> Re: 1123826836323a94d73355f0f6d7fd39466ad657
Hi Matt,
Re: 1123826836323a94d73355f0f6d7fd39466ad657 - Disable macOS packaging step
Looks like you disabled this to get jenkins working? Has a comment:
"FIXME: make this plugin optional"
Can you re-enable it? Optional is fine, I test with this all the time.
Thanks,
Scott
Nice catch! Will check it out.
Scott
On 3/15/18, ruch...@gmx.de wrote:
> Hello,
>
> I just downloaded the latest version and there seems to be a bug when
> importing / displaying log4j xml files:
>
> The line nr. is show in the column 'MILLISDELTA' (see screenshot).
>
> Regards
>
> Marc
>
>
>
I'm looking at adding an ES receiver and was curious what folks would
like to see when it comes to configuration options/capabilities, other
than the ability to continually retrieve new events on some polling
interval, which I'll make sure to add.
Scott
I haven't looked much at the src/site tree of Chainsaw, but it's clear that
the 'real' site code in svn was seeded from Chainsaw's src/site at one
point, but src/site is now stale.
Can I blow that directory away and remove any site-related targets
from Chainsaw's pom?
Thanks,
Scott
Thanks Matt! Looks good!
Scott
On 1/25/18, Matt Sicker wrote:
> This vote passes with 3 +1 votes from Scott Deboy, Remko Popma, and myself.
> I'll be following up with an announcement thread shortly.
>
> On 24 January 2018 at 18:50, Matt Sicker wrote:
>
>> So far so
+1
The added complexity of managing the various repo builds and compatibility
outweighs the build-time related cost of adding this code to core, easily.
Just consider the time required to RM these other repos. There is no
savings here to be found.
Scott
On Jan 24, 2018 6:20 PM, "Remko Popma" w
My recollection is vague, tied to pom machinations supporting a
similar separation for the 'log4j companions': outside of core log4j -
chainsaw, component, extras, receivers and zeroconf'
Some of the issues I recall having to deal with when we had the
generic 'component' module:
- Some classes s
Correcting my prior comment: the nightmare I was referring to was the
ugliness we did and un-did related to the never-released receivers and
'component' companions. Definitely feels like deja vu.
https://github.com/apache/log4j-component/blob/trunk/pom.xml
apache-log4j-companions-parent etc etc
I recall the log4j logging-parent nightmare of a number of years back.
Please let's not re-visit that.
https://github.com/apache/logging-parent/blob/master/pom.xml
Scott
On Jan 21, 2018 4:51 PM, "Remko Popma" wrote:
> Log4j2 is not like Maven. Maven (I assume) has a plugin API. Log4j2
> module
+1
Pulled the git tag, built it and started Chainsaw from the standalone
tarball and zips.
Wandered through the website - there is cleanup to be done, but that's
work that can be done post-release.
Scott
On 1/20/18, Matt Sicker wrote:
> This is a vote to release Apache Chainsaw 2.0.0-rc2
>
> S
Sure
On Jan 20, 2018 9:04 AM, "Matt Sicker" wrote:
> Wouldn't it be 2.0.0-rc2? Also, good timing: I can cut a new RC in the next
> few hours.
>
> On 20 January 2018 at 09:47, Scott Deboy wrote:
>
> > Matt, would you mind re-spinning a new build at 2.1.0-
Matt, would you mind re-spinning a new build at 2.1.0-rc1?
On 1/19/18, Scott Deboy wrote:
> I finally looked at this. I pushed a change to app assembler config
> to make the bin directory executable, and updated HOWTOBUILD to
> mention you need to run mvn site:site first.
>
&g
be updated to
> link to the (future) dist URLs instead of ones in the site's directory (no
> proper mirroring in the old links).
>
> On 12 November 2017 at 19:25, Scott Deboy wrote:
>
>> I don't recall why - it was a while back :)
>>
>> Yes, I think 2.1.0-rc1 wo
+1
On Nov 23, 2017 10:20 AM, "Ralph Goers" wrote:
> Or ask the author if he would like it to become part of Logging Services.
>
> Ralph
>
> > On Nov 23, 2017, at 7:51 AM, Gary Gregory
> wrote:
> >
> > On Thu, Nov 23, 2017 at 4:10 AM, Remko Popma
> wrote:
> >
> >> Interesting:
> >> https://gith
Awesome!
Re: appenders:
We went through a couple of code re-orgs back in 2011 and 2013, some
stuff was moved out of Chainsaw to apache-log4j-extras. Looks like
some was left behind.
You can define Chainsaw as an appender yourself - so the UI starts if
it's in the log4j xml config file.
Because
I don't recall why - it was a while back :)
Yes, I think 2.1.0-rc1 would make sense, once we fix the /bin directory issue.
On 11/12/17, Matt Sicker wrote:
> On 12 November 2017 at 13:53, Scott Deboy wrote:
>
>> That's right -forgot we rev'd to 2.1 internally (i
That's right -forgot we rev'd to 2.1 internally (info.plist, release
notes, couple other places).
Would it be easiest to release the new version as 2.1.0.0 instead of
2.0.0-rc1? Otherwise I could downgrade 2.1 refs, we never had an
official release with that rev.
Scott
On 11/12/17, Mikael Ståld
I think we can either fix or remove that menu item from the menu after
the release - I don't know how useful it is.
Scott
On 11/12/17, Mikael Ståldal wrote:
> When starting Chainsaw, I see this warning:
>
> Could not find any local JavaDocs, you might want to consider running
> 'ant javadoc'. Th
Fixed.
On 11/12/17, Mikael Ståldal wrote:
> In the About text, it says:
>
> Please send questions, bug reports and/or feature requests to
> log4j-...@logging.apache.org
>
> which is obsolete.
>
>
> On 2017-11-10 20:00, Matt Sicker wrote:
>> This is a vote to release Apache Chainsaw 2.0.0-rc1.
>>
That's right - we don't bundle in a JMS jar, although users can add
one to the classpath to use the JMSReceiver.
On 11/12/17, Mikael Ståldal wrote:
> When running Chainsaw, I see this error message:
>
> Failed to locate Receiver class:org.apache.log4j.net.JMSReceiver, looks
> like a dependent cla
t;>>> definitely get Chainsaw back in the game. I think you would have an
>>>> easy
>>>> time attracting a talent pool for something like that. For example
>>>> http://akveo.github.io/blur-admin/ is currently available on Github and
>>>> has 80
think you would have an easy
> time attracting a talent pool for something like that. For example
> http://akveo.github.io/blur-admin/ is currently available on Github and
> has 8000 stars. Could be the starting point for the next generation
> logging UI.
>
> Cheers,
>
>
I'd love to hear what folks think of the user experience with the
'latest Chainsaw' and its feature set.
There are a ton of features. It will be interesting to get a sense of
how many of those features we get 'for free' in any of these other UI
toolkits. It was a lot of heavy lifting to get Swin
I had ran mvn clean site:site install and it worked.
On 11/11/17, Mikael Ståldal wrote:
> On 2017-11-10 20:00, Matt Sicker wrote:
>> Artifacts:
>> https://dist.apache.org/repos/dist/dev/logging/chainsaw/
>> svn revision 23048
>
> When I look at that URL, it says: Revision 23059
>
Here's my +1.
Site looks good, and it builds and runs.
Thanks Matt
On 11/10/17, Scott Deboy wrote:
> Updated screenshot.
>
> On 11/10/17, Scott Deboy wrote:
>> Awesome..I'll commit a new screenshot then.
>>
>> On 11/10/17, Ralph Goers wrote:
>>&g
Updated screenshot.
On 11/10/17, Scott Deboy wrote:
> Awesome..I'll commit a new screenshot then.
>
> On 11/10/17, Ralph Goers wrote:
>> The web site doesn’t have to be locked into the release. An image can be
>> updated after the release pretty easily.
>>
&g
Awesome..I'll commit a new screenshot then.
On 11/10/17, Ralph Goers wrote:
> The web site doesn’t have to be locked into the release. An image can be
> updated after the release pretty easily.
>
> Ralph
>
>
>> On Nov 10, 2017, at 1:03 PM, Scott Deboy wrote:
>
Would it be possible for me to push an updated screenshot and re-spin?
On 11/10/17, Scott Deboy wrote:
> Wow that screen shot looks ancient and ugly. I should pull up
> something on the Mac with updated default colors - it looks much
> better.
>
> Scott
>
> On 11/10/1
Wow that screen shot looks ancient and ugly. I should pull up
something on the Mac with updated default colors - it looks much
better.
Scott
On 11/10/17, Matt Sicker wrote:
> Oh, and in case it isn't obvious how to test this, you can extract from
> either the zip or tar.gz files and run the cha
FYI, I think most folks just use pattern layout, which probably makes
VFSLogFilePatternReceiver the most commonly used receiver. Since it's
VFS, anything accessible over SSH is retrievable and can be
live-tailed.
Also, Chainsaw V2 can pull in logs generated by Log4j2 if you
configure an Advertise
ich
aren't present at all in log4j2, are found throughout the code.
A json receiver would be great!
Me, I've been working on a private cloud IaaS implementation for a few
years now - almost no Java there.
Scott
On 10/14/17, Matt Sicker wrote:
> On 14 October 2017 at 13:28, Scott Deb
Try out Chainsaw - it's super useful once you get the model. Under
help, there's info on the expression syntax, and the chainsaw-log tab
(where chainsaw log messages route by default) can be a playground for
working with the colorization/filtering/expressions.
Here's my general flow:
1. Filter a
Awesome! Happy to help here where I can, although I haven't worked in
Java in forever.
Chainsaw is really five parts:
- Receivers which grab the data from whatever source
- The 'route events to tabs' mechanism
- Table/event rendering, including search/filter/colorization and
time deltas betwe
Chainsaw supports log4j1's xml format over UDP and TCP, as well as any
regular text format via (VFS)LogFilePatternReceiver. It also supports
log4j1's serialized loggingevent format.
Chainsaw integration with Logj42 is via VFSLogFilePatternReceiver -
you have to specify the pattern and an accessib
very java main() method deserves http://picocli.info
> >
> >> On May 31, 2017, at 8:54, Ralph Goers
> wrote:
> >>
> >> At the request of Scott Deboy I have migrated chainsaw to git. You can
> view it at https://github.com/apache/logging-chainsaw <
> ht
74 matches
Mail list logo
