backtrace-morgue
Advanced tools
It is recommended to install morgue using npm.
npm install backtrace-morgue -g
If you working from the repository, then instead use the following command.
npm install -g
This will install the morgue tool in your configured path. Refer to the
morgue --help command to learn more.
morgue is a command-line interface to the Backtrace object store. It allows
you to upload, download and issue queries on objects with-in the object store.
Usage: morgue login <url>
The first step to using morgue is to log into a server.
$ morgue login http://localhost
User: sbahra
Password: **************
Logged in.
At this point, you are able to issue queries.
Retroactively apply sampling on a fingerprint. The default is to keep 3 objects retained for every fingerprint. This is configurable.
Usage: morgue keep <[<universe>/]project> [--keep=N] [<query filter>] [--output]
If output is provided, then all object identifiers are output to stdout. Statistics are output to stderr. It is then possible to chain this into morgue delete:
$ morgue clean blackhole --output > file.txt
$ morgue delete blackhole --physical-only `cat file.txt`
Currently, there is an upper-bound of deleting 10000 objects.
Usage: morgue describe <[<universe>/]project> [substring]
Requests a list and description of all metadata that can be queried against.
$ morgue describe bidder uname
uname.machine: machine hardware name
uname.release: kernel release
uname.sysname: kernel name
uname.version: kernel version
Usage: morgue get <[<universe>/]project> [options] <object id> [-o <output file>]
Downloads the specified object from the Backtrace object store and prints to standard output. Optionally, output the file to disk.
The following options are available:
| Option | Description |
|---|---|
--resource=name | Fetch the specified resource rather than the object. |
Usage: morgue put <[<universe>/]project> <file> <--format=btt|minidump|json|symbols> [options]
Uploads object file to the Backtrace object store. User has the following options
| Option | Description |
|---|---|
| `--compression=gzip | deflate` |
--kv=key1:value1,key2:value2,... | upload key-values |
--form_data | upload file by multipart/form-data post request |
Usage: morgue modify <[universe/]project> (<query>|<object> ...) [--set ...] [--clear ...]
Modifies attributes of the given object in the manner specified. Both options below may be specified more than once.
| Option | Description |
|---|---|
--set | Set the given attribute=value pair |
--clear | Clear the given attribute |
You are also able to modify multiple objects by specifying filters. The
--filter, --age and --time arguments are accepted to modify.
Set hostname to fqdn.example.com for object identifier 0.
$ morgue modify --set hostname=fqdn.example.com myproject 0
Set custom attribute reason to oom for all crashes containing memory_abort.
$ morgue modify --set reason=oom --filter=callstack,regular-expression,memory_abort
Usage: morgue attachment <add|get|list|delete> ...
morgue attachment add [options] <[universe/]project> <oid> <filename>
--content-type=CT Specify Content-Type for attachment.
The server may auto-detect this.
--attachment-name=N Use this name for the attachment name.
Default is the same as the filename.
morgue attachment get [options] <[universe/]project> <oid>
Must specify one of:
--attachment-id=ID Attachment ID to delete.
--attachment-name=N Attachment name to delete.
morgue attachment list [options] <[universe/]project> <oid>
morgue attachment delete [options] <[universe/]project <oid>
Must specify one of:
--attachment-id=ID Attachment ID to delete.
--attachment-name=N Attachment name to delete.
Manage attachments associated with an object.
Allows you to perform queries on object metadata. You can perform either selection queries or aggregation queries, but not both at the same time.
Usage: morgue list <[<universe>/]project> [substring]
You may pass --verbose in order to get more detailed query performance
data.
The filter option expects a comma-delimited list of the form
<attribute>,<operation>,<value>.
The currently supported operations are equal, regular-expression,
inverse-regular-expression, at-least, greater-than, at-most,
less-than, contains, not-contains, is-set, and is-not-set.
Pagination is handled with two flags
--limit=<n> controls the number of returned rows. --offset=<n> controls the
offset at which rows are returned, another way to put it is that it skips the
first <n> rows.
Aggregation is expressed through a myriad of command-line options that express
different aggregation operations. Options are of form --<option>=<attribute>.
The * factor is used when aggregations are performed when no factor is
specified or if an object does not have a valid value associated with the
factor.
| Option | Description |
|---|---|
--age | Specify a relative timestamp to now. 1h ago, or 1d ago. |
--time | Specify a range using Chrono. |
--unique | provide a count of distinct values |
--histogram | provide all distinct values |
--distribution | provide a truncated histogram |
--mean | calculate the mean of a column |
--sum | sum all values |
--range | provide the minimum and maximum values |
--count | count all non-null values |
--bin | provide a linear histogram of values |
--head | provide the first value in a factor |
--tail | provide the last value in a factor |
--object | provide the maximum object identifier of a column |
Sorting of results is done with the stackable option --sort=<term>. The term
syntax is [-](<column>|<fold_term>).
- reverse the sort term order to descending, otherwise it
defaults to ascending.<column> term refers to a valid column in the table. This is only
effective for selection type query, i.e. when using the --select option.<fold_term> is an expression pointing to a fold operation. The
expression language for fold operation is one of the following literal:
;group: sort by the group key itself.;count: sort by the group count (number of crashes).column;idx: where column is a string referencing a column in the fold
dictionary and idx is an indice in the array. See examples .Multiple sort terms can be provided to break ties in case the previous referenced sort term has ties.
Request all faults from application deployments owned by jdoe. Provide the timestamp, hostname, callstack and classifiers.
$ morgue list bidder --filter=tag_owner,equal,jdoe --select=timestamp --select=hostname --select=callstack --select=classifiers
*
#9d33 Thu Oct 13 2016 18:36:01 GMT-0400 (EDT) 5 months ago
hostname: 2235.bm-bidderc.prod.nym2
classifiers: abort stop
callstack:
assert ← int_set_union_all ← all_domain_lists ←
setup_phase_unlocked ← bid_handler_slave_inner ← bid_handler_slave ←
an_sched_process_task ← an_sched_slave ← event_base_loop ←
an_sched_enter ← bidder_slave ← an_sched_pthread_cb
#ef2f Thu Oct 13 2016 18:36:01 GMT-0400 (EDT) 5 months ago
hostname: 2066.bm-impbus.prod.nym2
classifiers: abort stop
callstack:
assert ← an_discovery_get_instances ← budget_init_discovery ←
main
#119bf Thu Oct 13 2016 18:36:01 GMT-0400 (EDT) 5 months ago
hostname: 2066.bm-impbus.prod.nym2
classifiers: abort stop
callstack:
assert ← an_discovery_get_instances ← budget_init_discovery ←
main
Request faults owned by jdoe, group them by fingerprint and aggregate the number of unique hosts, display a histogram of affected versions and provide a linear histogram of process age distribution.
$ morgue list bidder --age=1y --factor=fingerprint --filter=tag_owner,equal,jdoe --head=callstack --unique=hostname --histogram=tag --bin=process.age
823a55fb15bf697ba3041d736ade... ▁▁▁▁▁▁▁▁▁▁▁▁▁▁▁▁▁▁▁█▁▁▁▁▁▁▁▁▁▁▁▁ 5 months ago
Date: Wed May 18 2016 18:44:35 GMT-0400 (EDT)
callstack:
assert ← int_set_union_all ← all_domain_lists ←
setup_phase_unlocked ← bid_handler_slave_inner ← bid_handler_slave ←
an_sched_process_task ← an_sched_slave ← event_base_loop ←
an_sched_enter ← bidder_slave ← an_sched_pthread_cb
histogram(tag):
8.20.4.adc783.0 ▆▆▆▆▆▆▆▆▆▆▆▆▆▆▆▆▆▆▆▆▆▆▆▆▆▆▆▆▆▆▆▆▆▆▆▆▆▆▆▆ 1
unique(hostname): 1
bin(process.age):
7731 7732 ▆▆▆▆▆▆▆▆▆▆ 1
3b851ac1ab1421409159cc38edb2... ▁▁▁▁▁▁▁▁▁▁▁▁▁▁▁▁▁▁█▁▁▁▁▁▁▁▁▁▁▁▁▁ 5 months ago
Date: Tue May 17 2016 17:28:26 GMT-0400 (EDT)
Tue May 17 2016 17:30:07 GMT-0400 (EDT)
callstack:
assert ← an_discovery_get_instances ← budget_init_discovery ←
main
histogram(tag):
4.44.0.adc783.1 ▆▆▆▆▆▆▆▆▆▆▆▆▆▆▆▆▆▆▆▆▆▆▆▆▆▆▆▆▆▆▆▆▆▆▆▆▆▆▆▆ 2
unique(hostname): 1
bin(process.age):
23 24 ▆▆▆▆▆▆▆▆▆▆ 1
24 25 ▆▆▆▆▆▆▆▆▆▆ 1
Request faults for the last 2 years, group them by fingerprint, show the first object identifier in the group, sort the results by descending fingerprint, limit the results to 5 faults and skip the first 10 (according to sort order).
$ morgue list blackhole --age=2y --factor=fingerprint --object=fingerprint --limit=5 --offset=10 --sort="-;group"
fec4bfecf8e077cf44024f5668fa... ▁▁▁█▁▁▁▁▁▁▁▁▁▁▁▁▁▁▁▁▁▁▁▁▁▁▁▁▁▁▁▁ 2 years ago
First Occurrence: Tue Jan 12 2016 13:30:12 GMT-0500 (EST)
Occurrences: 360
object(fingerprint): 1c653d
fe7294a780a16e30b619e8d94a8a... █▁▁▁▁▁▁▁▁▁▁▁▁▁▁▁▁▁▁▁▁▁▁▁▁▁▁▁▁▁▁▁ 2 years ago
First Occurrence: Wed Oct 28 2015 11:30:47 GMT-0400 (EDT)
Last Occurrence: Wed Oct 28 2015 12:16:19 GMT-0400 (EDT)
Occurrences: 203
object(fingerprint): 1c23b3
fe5e0dda6cf0fb996a521dde4087... ▁▁▁▁▁▁▁▁▁▁█▁▁▁▁▁▁▁▁▁▁▁▁▁▁▁▁▁▁▁▁▁ 1 year ago
First Occurrence: Tue Jun 14 2016 11:54:35 GMT-0400 (EDT)
Occurrences: 1
object(fingerprint): 2de5
fe46d9af7c65c084091fed51ef02... █▁▁▁▁▁▁▁▁▁▁▁▁▁▁▁▁▁▁▁▁▁▁▁▁▁▁▁▁▁▁▁ 2 years ago
First Occurrence: Tue Oct 27 2015 16:59:34 GMT-0400 (EDT)
Last Occurrence: Tue Oct 27 2015 20:05:30 GMT-0400 (EDT)
Occurrences: 3
object(fingerprint): 8f41
fdc0860ef6dfd3d0397b53043ab9... ▁▁▁▁▁▁▁▁▁▁█▁▁▁▁▁▁▁▁▁▁▁▁▁▁▁▁▁▁▁▁▁ 1 year ago
First Occurrence: Tue Jun 07 2016 11:51:55 GMT-0400 (EDT)
Occurrences: 211
object(fingerprint): 1c1958
Request faults for the two years, group them by fingerprint, sum process.age,
sort the results by descending sum of process.age per fingerprint, limit the
results to 3 faults. Note here that 1 in -process.age;1 is the second
operator (--sum) in this case.
$ morgue list blackhole --age=2y --factor=fingerprint --first=process.age --sum=process.age --limit=3 --sort="-process.age;1"
d9358a6fdb7eaa143254b6987d00... ▁▁▁▁▁▁▁▁▁▁▁▁▁▁█▁▁▁▁▁▁▁▁▁▁▁▁▁▁▁▁▁ 1 year ago
First Occurrence: Tue Sep 20 2016 21:59:46 GMT-0400 (EDT)
Last Occurrence: Tue Sep 20 2016 22:03:23 GMT-0400 (EDT)
Occurrences: 38586
sum(process.age): 56892098354615 sec
524b9f988c8ff9dfc1b3a0c71231... ▁▁▁▁▁▁▁▁▁▁▁▁▁▁█▁▁▁▁▁▁▁▁▁▁▁▁▁▁▁▁▁ 1 year ago
First Occurrence: Tue Sep 20 2016 22:01:52 GMT-0400 (EDT)
Last Occurrence: Tue Sep 20 2016 22:03:19 GMT-0400 (EDT)
Occurrences: 25737
sum(process.age): 37947233900547 sec
bffd05c6b745229fd1c648bbe2a7... ▁▁▁▁▁▁▁▁▁▁▁▁▁▁█▁▁▁▁▁▁▁▁▁▁▁▁▁▁▁▁▁ 1 year ago
First Occurrence: Tue Sep 20 2016 21:59:46 GMT-0400 (EDT)
Last Occurrence: Tue Sep 20 2016 22:03:01 GMT-0400 (EDT)
Occurrences: 20096
sum(process.age): 29630010305216 sec
Allows deleting objects.
Usage: morgue delete <[universe/]project> <oid1> [... oidN]
Object IDs must be specified; they can be found in morgue list output.
The object ID printed in the example above is 9d33.
By default, this command (as of 2019-02-26) requests physical-only deletion,
which retains only indexing. The previous --physical-only argument is a
no-op. The following options affect this behavior:
--all: Delete all related data, including indexing.
--crdb-only: Only delete the indexed data; requires physically deleted objects.
Usage: morgue flamegraph <[universe/]project> [--filter=<filter expression>] [--reverse] [--unique] [-o file.svg]
Generate a flamegraph of callstacks of all objects matching the specified
filter criteria. The --filter option behaves identically to the list
sub-command. This functionality requires perl to be installed.
To learn more about flamegraphs, please see
http://www.brendangregg.com/flamegraphs.html.
Use --unique to only sample unique crashes. Use --reverse to begin sampling
from leaf functions.
Manage Backtrace symbold service
Usage: morgue symbold <symbolserver | whitelist | blacklist | skiplist | status> <action>
Return Symbold service status for <[universe]/project>
Usage: morgue symbold status <[universe]/project>
Symbol server allows you to manage symbol servers used by symbold
List Symbold symbol server assigned to <[universe]/project>
Usage: morgue symbold symbolserver list <[universe]/project>
Example:
$ morgue symbold symbolserver list backtrace
Retruns detailed information about symbol server
Usage: morgue symbold symbolserver details [symbolserverid]
Example:
$ morgue symbold symbolserver details 1
Command line above will return detailed information for symbol server with id 1
Returns symbol server logs. You can use page and take arguments to get more/less logs.
Usage: morgue symbold symbolserver logs [symbolserverid]
Example:
$ morgue symbold symbolserver logs 1 --take=100 --page=0
Command above will return first 100 logs from page 0
Usage: morgue symbold symbolserver add <[universe]/project> [symbolserverurl]
<--name=...>
<--concurrentdownload=...>
<--retrylimit=...>
<--timeout=...>
<--whitelist=...>
<--servercredentials.username=...>
<--servercredentials.password=...>
<--aws.accesskey=...>
<--aws.secret=...>
<--aws.bucketname=...>
<--aws.lowerfile=...>
<--aws.lowerid=...>
<--aws.usepdb=...>
<--proxy.host=...>
<--proxy.port=...>
<--proxy.username=...>
<--proxy.password=...>
Add new symbol server to symbold service. Available options:
name - symbol server name,concurrentdownload - maximum number of concurrent download that symbolmd will do at the same time,timeout - download timeoutwhitelist - determine if symbol server should use whitelist or not,servercredentials - symbol server auth optionsservercredentials.username - symbol server auth user name,servercredentials.password - symbol server auth password,aws.accesskey - AWS S3 access keyaws.secret - AWS S3 secretaws.bucketname - AWS S3 bucket nameaws.lowerfile - determine if symbold should use lower case symbol nameaws.lowerid - - determine if symbold should use lower case debug idaws.usepdb - determine a way to generate url to S3 symbolsproxy.host - proxy hostproxy.port - proxy portproxy.username - proxy usernameproxy.password - proxy passwordExample:
$ morgue symbold symbolserver backtrace https://symbol.server.com --name=name --timeout=400
Usage: morgue symbold symbolserver update [symbolserverid]
<--url=...>
<--name=...>
<--concurrentdownload=...>
<--retrylimit=...>
<--timeout=...>
<--whitelist=...>
<--servercredentials.username=...>
<--servercredentials.password=...>
<--aws.accesskey=...>
<--argv.aws.secret=...>
<--argv.aws.bucketname=...>
<--argv.aws.lowerfile=...>
<--argv.aws.lowerid=...>
<--argv.aws.usepdb=...>
<--argv.proxy.host=...>
<--argv.proxy.port=...>
<--argv.proxy.username=...>
<--argv.proxy.password=...>
Update symbol server with id [symbolServerId]. If aws, proxy and servercredentials data doesn't exists symbold will ignore update server credentials. If any of them exists, symbold will try to update all properties. Example:
$ morgue symbold symbolserver update 1 --url="http://new.symbol.server.url"
Usage: morgue symbold symbolserver disable [symbolserverid]
Disable symbol server. Symbold won't use disabled symbol server.
Usage: morgue symbold symbolserver enable [symbolserverid]
Enable symbol server.
Usage: morgue symbold [whitelist|blacklist] [--name=...]
Add new element to blacklist/whitelist
Usage : morgue symbold [whitelist|blacklist|skiplist] [--itemid=...]
Usage: morgue symbold [whitelist|blacklist|skiplist] <--page=...> <--take=...>
List <--take> elements from [whitelist|blacklist|skiplist] from <--page> page
Create and manage scheduled reports.
Usage: morgue report <list | create | delete | send> [--project=...] [--universe=...]
Usage: morgue report <project> create
<--rcpt=...>
<--title=...>
[--filter=...]
[--fingerprint=...]
[--histogram=...]
[--hour=...]
[--day=...]
--period=<week | day>
Example:
$ morgue report MyProject create --rcpt=null@backtrace.io
--rcpt=list@backtrace.io --filter=environment,equal,prod
--title="Production Crashes weekly" --period=week
Usage: morgue report <project> delete <report integer identifier>
Usage: morgue report <project> list
Usage: morgue merge <project> list of fingerprints
Usage: morgue unmerge <project> list of fingerprints
Fingerprints can be merged and unmerged to a group via those commands. A group on a fingerprint is currently represented as a sha256 with mostly zeros in the beginning. Those special group fingerprints can be used in further merge commands to enlargen the group even more.
Unmerging accepts real fingerprints and groups. It separates the fingerprint from the group. After the operation the fingerprint is independent again.
When listing crashes, fingerprint;original can be used to get the original fingerprint from before the grouping process if wanted.
Usage: morgue repair <[universe/]project>
Repair a project's attribute database. For each corrupted pages of a project's attribute database, reprocess the affected objects (if possible). Once completed and successful, transition the database into normal mode.
Usage: morgue reprocess <[universe/]project> [<query>|<object> ...] [--first N] [--last N]
Options for reprocess:
--first=N Specify the first object ID (default: earliest known)
--last=N Specify the last object ID (default: most recent known)
Reprocess the project's objects. This command can be used to re-execute indexing, fingerprinting, and symbolification (where needed).
If a set of objects (or query) is specified, any values for --first and
--last are replaced to match the object list. If no query, object list,
or range is provided, all objects in the project are reprocessed.
Usage: morgue retention <list|set|status|clear> <name> [options]
Options for set/clear:
--type=T Specify retention type (default: project)
valid: instance, universe, project
Options for status:
[--type=<universe|project> <name>]
Options for set:
--max-age=N Specify time limit for objects, in seconds
--physical-only Specifies that the policy only delete physical copies;
indexing will be retained.
Configure the retention policy for a given namespace, which can cover the coroner instance, or a specific universe or project.
$ morgue retention clear a_project
success
$ morgue retention set blackhole --max-age=3600
$ morgue retention list
Project-level:
blackhole: max age: 1h
$
Usage: morgue sampling <status|reset> [options]
Options for either status or reset:
--fingerprint=group Specify a fingerprint to apply to.
Without this, applies to all.
--project=[universe/]project Specify a project to apply to.
Without this, applies to all.
Options for status only:
--max-groups=N Specify max number of groups to display
per project.
Retrieve the object sampling status, or reset it. Project is a required flag if fingerprint is specified.
Usage: morgue symbol <[<universe>/]project> [summary | list | missing | archives] [-o <output file>]
Retrieve a list of uploaded symbols or symbol archives. By default, morgue symbol
will return a summary of uploaded archives, available symbols and missing symbols.
If archives is used, a list of uploaded, in-process and symbol processing errors
are outputted. If list is used, then a list of uploaded symbols is returned. If
missing is used, then the set of missing symbols for the project are included.
Create, modify and delete data scrubbers.
Usage: morgue scrubber <project> <list | create | modify | delete>
Use --name to identify the scrubber. Use --regexp to specify the pattern to
match and scrub. Use --builtin to specify a builtin scrubber, ssn, ccn,
key and env are currently supported for social security number, credit card
number, encryption key and environment variable. If --builtin=all in create
subcommand, all supported builtin scrubbers are created. --regexp and
--builtin are mutually exclusive. Use --enable to activate the scrubber, 0
disables the scrubber while other integer values enable it.
Usage: morgue setup <url>
If you are using an on-premise version of coronerd, use morgue setup
to configure the initial organization and user. For example, if the server is
backtrace.mycompany.com, then you would run morgue setup http://backtrace.mycompany.com.
We recommend resetting your password after you enable SSL (done by configuring
your certificates).
Usage: morgue nuke --universe=<universe name> [--project=<project name>]
If you want to nuke an object and all of the dependencies of the object. Do not use this operation without making a back-up of your data.
Usage: morgue token [create | list | delete] [--project=...] [--universe=...]
Usage: morgue token create --project=<project> --capability=<capability>
Capability can be any of:
Multiple capabilities can be specified by using --capability multiple times
or using a comma-separated list.
Usage: morgue token list [--universe=...] [--project=...]
List API tokens in the specified universe, for all projects or a specified project.
Usage: morgue token delete <sha256 or prefix>
Delete the specified token by substring or exact match.
Usage: morgue user reset [--universe=...] [--user=...] [--password=...]
Modify users.
Currently, can only be used to reset user passwords. Prompts for user and password if either is not specified.
Create isolated tenants for receiving error data and log in. Tenants provide namespace isolation. Users in one tenant are unable to interact with any objects outside of their tenant.
This is an enterprise feature and not enabled by default for self-serve customers. The tenant commands require superuser access.
Usage: morgue tenant <list | create | delete>
create <name>: Create a tenant with the specified name.
delete <name>: Delete a tenant with the specified name.
list: List all tenants on your instance.
1.0 Create a Tenant
After logging into an object store as a superuser, we are able to simply create a tenant using the following command:
$ morgue tenant create testingxyz
Tenant successfully created at https://testingxyz.sp.backtrace.io
Wait a few minutes for propagation to complete.
Tenants are required to be contained with-in the same TLD. For example,
a tenant of name X is expected to be contained in X.sp.backtrace.io.
After creating a tenant, you will probably need to invite an initial
administrator user for the tenant. For that, please see invite sub-command
listed below. You must use the --tenant option to invite an administrator
to a particular tenant.
2.0 Delete a Tenant
After logging into an object store as a superuser, we are able to simply create a tenant using the following command:
$ morgue tenant delete testingxyz
Tenant successfully deleted.
Please note this is a destructive command from a configuration perspective. Unless you are maintaining backups, there is no way to restore your configuration data.
3.0 List Tenants
You can list existing tenants using the morgue tenant list command
as below.
$ morgue tenant list
ID Tenant URL
1 test https://test.sp.backtrace.io
4 test1 https://test1.sp.backtrace.io
Compute the similarity and list acceptably similar crash groups according to their callstack attribute.
Usage: morgue similarity <[universe]/project> [filter expression]
[--threshold=N] The minimum length of the callstack for groups to
consider for similarity analysis.
[--intersect=N] The minimum number of common symbols between
two groups.
[--distance=N] The maximum acceptable edit distance between
two groups.
[--fingerprint=N] A fingerprint to compute similarity to.
Invite new users into your system. Requires you to have logged in.
Usage: morgue invite <create | list | resend>
create <username> <email>
--role=<"guest" | "member" | "admin">
--metadata=<metadata>
--tenant=<tenant name>
--method=<"password" | "saml" | "pam">
delete <token>
resend <token>
1.0 Invite a User
Below, we invite a new user into the tenant currently logged into (or
the first tenant, if multiple exist). The default settings for the user
are to use password authentication and have a member role.
$ morgue invite create <username> <user e-mail>
$ morgue invite sbahra user@backtrace.io
Invitation successfully created for user@backtrace.io
Sending e-mail...done
1.1 Invite a User as an Administrator
$ morgue invite create user user@gmail.com --role=admin
Invitation successfully created for user@backtrace.io
Sending e-mail...done
1.2 Invite a User into a Particular Tenant
$ morgue invite create user user@gmail.com --tenant=mystudio
Invitation successfully created for user@backtrace.io
Sending e-mail...done
2.0 List Pending Invitation
This will list invitations that have yet to be accepted or activated.
$ morgue invite list
Tenant Username Method Role Email Token
1 ashley2 password admin ashley2@backtrace.io f892200fa564...
1 jack1 password member jack@backtrace.io 39c1b80a7e00...
1 jack2 password member jack+2@backtrace.io c399bdf23873...
1 jack17131 password member jack+4512@backtrace.io 784d2a8ffe12...
1 jack25262 password member jack+24688@backtrace.io 97e306d3373a...
1 jack25629 password member jack+28155@backtrace.io ed02ceea2ba4...
1 jack28000 password member jack+3644@backtrace.io 3f87906bd5d9...
1 jack19468 password member jack+28771@backtrace.io 3c6b3a3aaf41...
1 jack15686 password member jack+4203@backtrace.io 78bd9cd127a8...
4 jack2268 password member jack+19325@backtrace.io 776c6d389f89...
4 jack20597 password member jack+24692@backtrace.io 48972737a85e...
4 jack4803 password member jack+30407@backtrace.io 4943913c86f3...
3.0 Delete an Invitation
Below, we demonstrate how to delete an invitation. We pass a token (or unique substring) for deletion.
$ morgue invite delete f8922
Invitation successfully deleted.
Use this command to check the callstack results for a given object.
$ morgue callstack evaluate project oid
$ morgue callstack evaluate project file.json
FAQs
command line interface to the Backtrace object store
The npm package backtrace-morgue receives a total of 196 weekly downloads. As such, backtrace-morgue popularity was classified as not popular.
We found that backtrace-morgue demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 7 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Research
Security News
Socket researchers uncover a malicious npm package posing as a tool for detecting vulnerabilities in Etherium smart contracts.
Security News
Research
A supply chain attack on Rspack's npm packages injected cryptomining malware, potentially impacting thousands of developers.
Research
Security News
Socket researchers discovered a malware campaign on npm delivering the Skuld infostealer via typosquatted packages, exposing sensitive data.