Account Settings

Contents

• Account Settings

  • Metric Expiry

  • Tag Expiry

  • Default Timezone

  • Billing and Invoices

  • Changing Your Account Email

  • Receive Billing Emails to a Different Address

Metric Expiry

If you use a lot of transient metrics generated by spin-up VMs or on-demand instances, you may want to expire these after a period of inactivity to help manage your total number of stored metrics.

For example, if you set the Expiry Period to 30, any matching metric that hasn’t received data in 30 days will be deleted. The wildcard (*) character is greedy, which means it will match everything that fits into the given pattern (as opposed to Graphite where it matches only one node level).

For prefixes that are subsets of each other, the more specific name will take priority. So for foo = 1 and foo.bar = 5, foo and foo.baz and foo.baz.steve will be set to 1. foo.bar, foo.bar.baz and so on will be set to 5.

Consideration: Our Expiry feature is not intended for blocking metric patterns from ingestion, rather cleaning up stale metrics that haven't received data for X days.

NOTE: You can configure a global expiry rule to target all (*) metrics, but if you target a *specific.metric.pattern*, the global expiry will be overridden. Additionally, any expired namespaces will be recreated if they are re-sent, and will continue to map to all of their historic data.

Tag Expiry

Hosted Graphite supports Expiry Rules for tagged metrics. Similar to how metric expiry rules work with a few exceptions listed below:

• Tags have to be the exact match to the tag listed on the series.

  • EX: cpu.usage;region=south;server=db-0001

  • In order to add an expiry rule to the series above, the tag field will have to be one of the following: name, region, or server.

  • In order to set the rule for the series name: cpu.usage set the tag to name.

    • This will expire all the series with this name regardless of the tags it is identified by.

  • At the moment only one tag per field is accepted.

• The value field does accept wildcard characters.

  • For example if you want to expire all series with the prefix cpu then the tag would be name and the value would be cpu.* and all these series would expire after the defined period of inactivity:

  cpu.usage.total;region=south;server=db-0001

  cpu.usage.sys;region=east;server=db-0002

  cpu.usage.user;region=west;server=db-0001

• The expiration will be processed by the of time listed.

  • Ex: Suppose you have 2 series:

    cpu.usage;region=south;server=db-0001

    diskspace.available;region=south;server=db-0001

  • With the following expiry rules:

    • tag: name; value=cpu.usage -> 2 days

    • tag: server; value=db-0001 -> 1 day

  • This would expire every series with a server of db-0001 including the ones listed for the first expiry rule. The following day, if the series diskspace.available is recreated, then it would expire once more.

Default Timezone

Setting a default timezone within Hosted Graphite ensures that graphs rendered by Graphite are configured to use that timezone.

Simply pick the timezone of your choice from the dropdown, and the setting will be automatically saved.

Billing and Invoices

You can easily manage your billing preferences and settings with our provider, Stripe.

Changing Your Account Email

You can change the email address associated with your Hosted Graphite account by navigating to the account settings page, clicking on the Advanced Options button at the bottom of the page, and selecting Enter the new email.

After you fill out the form a confirmation link will be sent to your new email address to verify the change.

If an account already exists with the new email, you’ll need to either rename that one first or contact us to delete it.

Receive Billing Emails to a Different Address

If you would like to receive a copy of billing invoices to an email address that is different from the one primarily used on the account, please contact support.