On our community page.
The following programming languages are currently supported:
The Prodfiler agent is designed to be used continuously in production and has a tiny performance footprint (< 1% CPU, ~200MB of RAM).
Prodfiler makes use of eBPF to load programs into the kernel. An eBPF program must pass the eBPF verifier, which ensures that the program is safe to run, before it’s loaded into the kernel. This means that even if the eBPF program is buggy, it can not crash the kernel.
There is a maximum number of projects (1) and a per-project host limit (20)
for new accounts. Please contact us to have that limit raised.
The Prodfiler agent does not require debug symbols in order to unwind stacks, but our backend does require them in order to symbolise stack traces in the UI. We automatically mirror, index and use the debug packages provided by several distributions (e.g. Ubuntu, Debian, Fedora and Amazon Linux), so if your traces are from applications in the official repositories then they should be automatically symbolised. If they are not, please let us know via the community page.
For custom binaries, or binaries that we have not indexed, you need to ship us your symbols. We provide a script to do so, which can be integrated with your CI/CD system if necessary. See here for details.
Q: Why is a query returning obscure errors?
A: Currently, the error messages returned are not self-explanatory. Sorry! Make sure the query adheres to the filtering syntax, or feel free to contact us for assistance.
Q: Why are there no results returned?
A: Some things to check:
ec3:ami-id instead of ec2:ami-id, no results will be returned, and no error will be raised.Q: Why are there too many results returned?
A: Some things to check:
^ and $), and remember that . matches any character.Q: Is it possible to know how many / what hosts were matched by a filter?
A: Not at the moment.