moshebe/gtrace

Unofficial, simple yet effective Google Cloud Trace CLI tool.

gtrace's Issues

verbose/debug mode

Support verbose and debug prints (-v ?)

[Informational] Use case for gtrace CLI

This is pretty neat! I'm the PM for Google Cloud Trace and I'm curious about your use case(s) for this CLI. When do you use this CLI as opposed to using the Google Cloud Console web UI for Cloud Trace?

I suspect the ease of being able to use cmd line tools like grep, sed, etc on a terminal is the main motivation but wanted to confirm.

Support only JSON input/output

Same as title implies

Change input to --file

Input can be either a file or stdin

auto detect project from gcloud configuration

Instead of requiring the --project we can auto-detect the active project and use it as the default

gcloud config get-value project

README

• Motivation for the project
• Authentication (auto-detect GCP credentials / supply base64 decoded credentials env)
• Installation / Building from source
• Usage example
• Contribution Guideline

Bonus: nice logo 😄

Remove --output flag

Use the proper unix way

gtrace get > file.json
# Or
gtrace get | tee file.json

CLI design

Tech:

• stdlib? maybe https://github.com/urfave/cli?
• store config?

Features we may think about:

• control project from command line (like in gcloud --project)
• set default project (use by default the gcloud project id or override it only for our tool?)
• exclude/include spans (whitelist/blacklist) - by regex
• exclude/include labels (whitelist/blacklist) - by regex
• sources: fetch trace from GCP: by trace id, search by filters
  • (enable pre-created filters for example: if I want to search for bla-id instead of passing
    LABEL:bla-id:1234 I'd like to create a custom filter for bla-id and just find it by:
    gtrace get bla 1234 (maybe we can hold per such a filter the exclude/include spans etc.)
• Destinations: stdout, file (/tmp or given path?)