fgprof
tlog
| fgprof | tlog | |
|---|---|---|
| 3 | 4 | |
| 2,759 | 295 | |
| - | 1.4% | |
| 3.3 | 5.2 | |
| about 2 months ago | 3 months ago | |
| Go | C | |
| MIT License | GNU General Public License v3.0 only |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
fgprof
- Fgprof – The Full Go Profiler
-
Go profiler service in AWS
As for OP: I'm not aware of a similar offering by AWS itself. You could try https://pyroscope.io/ but I'd be hesitant to recommend it because it's based (well, copied my code without attribution/license, different story : p) on my fgprof project. Unfortunately that means it won't scale to applications with many goroutines and add O(N) stop-the-world pauses to your application 🙈.
-
Pyroscope — continuous profiling software to help you identify performance issues.
I agree the UI could use some work, but generally speaking CPU profiling is supported and does work. In fact, any HTTP endpoint that returns a valid pprof profile works, so even custom profiles are supported, such as fgprof.
tlog
-
Help with installing tlog on Debian 10
https://salsa.debian.org/ascii/tlog/-/tree/debian/latest https://github.com/Scribery/tlog
- How to log bash commands in some simple way?
- Tlog: Terminal I/O Logger
-
Bash-Oneliner: A collection of handy Bash One-Liners and terminal tricks
Enterprises that requires logging of user actions will very likely not being doing it at the shell level, either through compiled in options, or shell history.
Instead, the Kernel has built in functionality called Auditd[0], which is capable of logging any and all executions, file or socket accesses, and much more. Along with included tooling for quickly finding and alerting on events[3].
Further, if terminal logging or playback is really required (usually not), it's generally done through pam with tlog[1]. Red Hat 8 and above come with built-in tlog support[2].
[0] https://access.redhat.com/documentation/en-us/red_hat_enterp...
[1] https://github.com/Scribery/tlog/blob/main/README.md
[2] https://access.redhat.com/documentation/en-us/red_hat_enterp...
[3] https://wiki.archlinux.org/title/Audit_framework
What are some alternatives?
profefe - Continuous profiling for long-term postmortem analysis
trice - 🟢 super fast 🚀 and tiny 🐥 embedded device 𝘾 printf-like trace ✍ code, works also inside ⚡ interrupts ⚡ and real-time PC 💻 logging (trace ID visualization 👀)
go-profiler-notes - felixge's notes on the various go profiling methods that are available.
snoopy - Snoopy Command Logger is a small library that logs all program executions on your Linux/BSD system.
pyroscope - Continuous Profiling Platform. Debug performance issues down to a single line of code [Moved to: https://github.com/grafana/pyroscope]
bash-preexec - ⚡ preexec and precmd functions for Bash just like Zsh.
wzprof - WebAssembly Profiler based on Wazero
cassette_deck - 🖭 CLI gif recorder, simplified
perforator - Record "perf" performance metrics for individual functions/regions of an ELF binary.
vscode-bash-debug - Bash shell debugger extension for VSCode (based on bashdb)
tlog - Observability events system
logswan - Fast Web log analyzer using probabilistic data structures