Faq

FAQs

Q: Can I send data from my agents using the Email and Http transports interchangeably? A: Yes! (but you might want to keep things standard for sanity's sake!).

Q: Can I send data from my Python, Ruby and Node apps? A: Yes! But each language needs its own agent. If one doesn't exist for your language, you can build (or submit) your own.

Q: Is there a Metaport Helmchart for use with Kubernetes? A: Not yet, but we'll be working on it!

Q: Does Metaport support apps that comprise multiple systems, each of which uses a different agent e.g. a React frontend and Laravel backend? A: Yes! Metaport models these as "App Groups" where each such group maps to a single "Real World Application" which itself comprises one or more individual apps written in different languages and hosted entirely separately.

Q: Does Metaport support apps with multiple domains?? A: Yes!

Q: Why does my app's framework report as being "Critical", but there's still a long time until it's end-of-life? A: Metaport is all about planning, and it determines "Critical" to be <= 3 months to end date, "Imminent" to be <= 6 months to end date, "Warning" to be <= 9 months to end date, and "Information" to be >= 12 months to end date. There are also plans in the backlog for allowing these thresholds to be determined on a team by team basis.

Q: Is there a Docker image available? A: Yes! See our Docker Hub

Q: Can Metaport automatically create issues in my team's backlog? A: Right now, issue creation into Jira, is manual, but on our roadmap is to automate issue creation into the appropriate backlog whenever CVEs are reported or EOL dates are approaching.