Sentry FAQs

GitLab takes into account the whitespace before and after the / . On the Repositories page (Organization Settings >> Repositories), you'll notice a space e.g. Owner / Repo(as opposed to Owner/Repo), which will need to be included in any command you're running.

If you are using GitLab's environment variables ( https://docs.gitlab.com/ee/ci/variables/#debug-tracing) to pass the repository as CI_PROJECT_PATH in a cURL request for example, it may not include the spaces and you'll need to hardcode the name in order for it to work.

Yes! Sentry's localization support is provided through Transifex. You can find our project here and request to join the team to begin contributing.

First, make sure you've whitelisted our IPs which can be found here.

Additionally, the 500 response is coming from GitLab so you may need to try again or double-check that your settings and permissions are correct in GitLab. You must have both owner/manager permissions in Sentry as well as owner permissions in GitLab to successfully install this integration.

When using the GitLab integration to create issues, the "reporter" field is populated as the person who set up the integration by default- this is not configurable.

For certain SDKs you have to manually enable capturing of IP addresses. Here are some examples:

C#

Sentry.ConfigureScope(s => s.User.IpAddress = "{{ auto }}");

or:

var user = new User { IpAddress = "{{ auto }}" };

Sentry.CaptureEvent(new SentryEvent { User = user });

or:

Sentry.Init(o => o.BeforeSend = e => { e.User.IpAddress = "{{ auto }}";

return e; });

Java

Sentry.getContext().setUser(

new UserBuilder().setIpAddress({{auto}}).build()

);

Native

sentry[user][ip_address]={{auto}}

If you've set up data forwarding via Splunk but events aren't being sent, here are a couple of things to check:

The instance URL is incorrect. Double check the format:

If you're using Splunk cloud, this is the format - https://input-<host>:8088

if you're hosting Splunk yourself, this is the format: https://http-inputs-<host>:8088

See the full documentation here for more infomation

Double check that in your Splunk configuration the HEC status is enabled. See this screenshot for what it should look like:

You'll need to confirm that the debug information file was actually uploaded and that it was uploadedbefore the event was reported to Sentry. You can check if the debug information file was uploaded by searching on your Debug Files page:Project Settings Debug Files.

Note:The file size limit of an individual DIF is 2GB.

General information on debug information files can be found here. Information on using the sentry-clito check, find, upload, etc. debug information files can be found here.

If you're having issues adding a GitHub repository, please refer to the troubleshooting steps below to see if any of theseresolves your issue:

Make sure you are the Owner of your GitHub organization.

Make sure you are either an Admin, Manager, or Owner of your Sentry organization.

Disconnect your GitHub Identity, then reconnect your GitHub Identity.

If you're getting a "404 Not Found error", check out this article.

400 Error

This is often because the Jira instance is not publicly accessible. Make sure your instance is routable (i.e. our server can reach it!). If not, you'll need to put your Jira instance on the internet so that we can reach it.

500 Error

Unfortunately, this can vary per user. This error means we couldn't connect to your server from our server. For example, perhaps your proxy is not configured correctly, or not set to allow our IP. If you need to whitelist our IPs, you can find a list of our IP ranges here.

If you received an email notifying you that we were unable to fetch the commit log for your release, try out some of the solutions below:

GitHub

GitHub returned a 404 Not Found error. If this repository exists, ensure that your installation has permission to access this repository ( https://github.com/settings/installations ).

If you have already confirmed the correct permissions from the message above:

Your GitHub identities in Sentry may not be synced up with the user who is creating the release in Sentry.

If you have already connected your identity and arestill receiving this message, you may need to disconnect or reconnect your identity.

All Sentry users will need to do this if they are creating releases.

Try the troubleshooting steps in this Help Center article.

Unauthorized: either your access token was invalid or you do not have access

Confirm that the Auth Token being used to create the release in Sentry has the correct scopes and is also associated with the GitHub identity of the user who is creating releases in Sentry.

You may also need to disconnect/reconnect your GitHub identity as mentioned above.

Bitbucket

Error Communicating with Bitbucket (HTTP 500): Something went wrong

Unfortunately, this message usually indicates that there's something wrong on Bitbucket's end. We suggest to try and associate the commits with the release again.

Sentry currently has two types of integrations: Global and Legacy. The difference is important when choosing an action for a new Alert Rule.

The option "Send a notification (for all legacy integrations)" will send an alert to legacy integrations and explicitly NOT to the new Global Integrations.

What's the difference between Global and Legacy integrations?

Legacy Integrations are configured per-project and offer little customization. Legacy notification integrations (HipChat, PagerDuty, VictorOps, etc).

Global Integrations are still configured within Project Settings but are global across your Sentry organization. They offer more granular control (the Slack integration allows you to choose specific channels per-alert rule, whereas legacy integrations can only alert the same channel).

Over time, Legacy integrations will be migrated to Global integrations. When that happens, you'll need to disable the old integration and configure the new integration.

You're able to change the subject linefor alertemailswithinyour Project's Email Settings by going to Project Settings > Alerts. Email subjects can include variables such as $project, $title, and ${tag:key}, such as ${tag:environment} or ${tag:release}.

Note that this won't affect Workflow emails.

You need to make sure you have authorized Sentry for your Repo or Organization.

The owner of the repo needs to go to Account Settings > Authorized Applications and make sure that Sentry is an authorized application.

If you have a repo that is part of an organization on Github:

Visit https://github.com/settings/connections/applications/0dc8e2df8aa45477de5e and see if the organization has a red 'x'. If so, you need to 'Grant Access' (which can be done by the owner of the organization).

Once you grant access you can go to Organization Settings > Third Party Access > Sentry to confirm the authorization.

If you are not the owner of the account you can follow these instructions.

Note: Deleting all of your issues may not be the best choice. Read about other options here.

With bulk actions - both deleting and resolving - you can only do up to 1000 issues at a time. When in your issue dashboard for a given project you can select issues matching a given query, is:unresolved for example, and then select Resolve or use the dropdown to Delete Issues:

Bulk Remove

Should you wish to use the API you can use the Bulk Mutate endpoint or endpoint for resolving and deleting, respectively.

Go to your Project Settings.

Click on Legacy Integrations under Legacy Integrations.

Find the integration you are looking for and then click Configure Plugin.

Enter the required information and click Save Changes.

Make sure you have enabled your integration by clicking Enable Plugin.

If you have a search term that has a colon you need to wrap the term in quotation marks.

Ex.

Rack::Timeout needs to be "Rack::Timeout"

Alerts are only sent when a rule is triggered. For example, if the rule condition is when "an event is first seen", an alert will not be dispatched until a new issue is created. (Depending on how many unique issues your project is receiving, this can take some time.)

Ensure that the notification integration is enabled under the rule actions, either as the specific service, or covered under "all enabled services".

Yes, if using the global Slack integration you can configure alert rules to route notifications to a specific Slack channel. In the "Take these actions" section, choose "Send a notification to the {workspace} Slack workspace to {channel} and show tags {tags} in notification" and fill out the appropriate fields.

The issue search understands a variety of tags, including "age" and "event.timestamp". Search returns Issues which have at least one occurrence or event matching your query.

Age: age always relative to the current time, and respects h, d, and w.

example: age:-24h (Issues new in the last 24 hours)

Timestamp: event.timestamp is an absolute tag and respects >,<,<=, and >=. It uses UTC.

example: event.timestamp:2017-01-02 (Events that occurred on January 2nd)

event.timestamp:<2017-01-02T01:00:00 (Events from before January 2nd)

See the documentation for more examples and other tag examples! https://docs.sentry.io/workflow/search/

Like all search tags, these tags can be combined with themselves (to form ranges) and each other.

No. We suggest setting up a server/service that proxies our webhook into a request that fits your use case.

Yes - from the Issue Details page click "Merged". You will see the fingerprints that have been merged into that issue. Select the checkbox(es) and click "Unmerge".

Most of our SDKs provide a mechanism for determining whether to send an event to Sentry based on custom logic.Here's a code snippet showing how to use shouldSendEventwith the Cocoa SDK:

self.shouldSendEvent = ^BOOL(SentryEvent *_Nonnull event) { return (sampleRate >= ((double)arc4random() / 0x100000000)); };

See the rest of the Cocoa SDK documentation here, and configuration for other SDKs here.

You're seeing this notification due to your organization exceeding it's monthly quota. You will no longer receive new events until either a user with the role of Organization Owner or Billing enables on-demand spending on your Usage & Billing page, increases the capacity of your plan, or when your next Usage Period starts.

To help manage your future event volume, we recommend:

Configuring sample_rate, see documentation specific to your SDK: https://docs.sentry.io/error-reporting/configuration/#sample-rate

Filtering events using before_send, see documentation specific to your SDK: https://docs.sentry.io/error-reporting/configuration/filtering/

Enabling on-demand spending by adding a dollar amount, or toggling Unlimited

More information can be found here: https://docs.sentry.io/accounts/quotas/#controlling-volume

You control who can see events. We allow you to add your team members, as well as share events with anonymous users should you wish to do so.

What's an event?

An event is one instance of you sending us data. Generally, this is an error, but it's possible to send us non-error related data as well.

What's an issue?

An issue is a group of similar events. More details about why certain events are grouped together can be found here: https://docs.sentry.io/learn/rollups/, but most often events are grouped becausethey'retriggered by the same part of your code, or, if that dataisn'tavailable, because they are exceptions of the same type and value.

Our on-premise version of Sentry is totally open source, so you can run it yourself without any limitations:

You can read more about our open source philosophy in this blog post. If you have any questions about running Sentry on-premise please contact us at [email protected].

Go to your personal settings by selecting your avatar in the bottom left corner.

Select Account.

Select Appearance.

Select your timezone under Time Zone.

You can update your email/password in your Account Settings.

All of our pricing information can be found here: https://sentry.io/pricing/

Normally, Sentry begins to discard events as soon as your organization depletes its event capacity. However, we understand that errors can come in spikes and service interruptions can be challenging, so we include a one time grace period for all paid accounts.

If an account depletes its event capacity and has never previously triggered a grace period, we continue to accept events for the next 3 days at a maximum rate of 10K events per hour. If you choose not to increase your capacity, Sentry will stop accepting events for the remainder of the current billing month. However, if you increase your capacity, events accepted during the grace period will be counted as consumed capacity.

Once you've used your grace period, we recommend using our on-demand spending caps to ensure you have time to adjust your capacity in the event of a spike in errors.

Sentry groups issues together based on the Grouping Algorithms shown here. If you'd like to override the default grouping, you have some options. To configure this using the SDK, take a look at the SDK fingerprinting documentation page and the documentation specific to your SDK. To configure this in your project settings, please read the server side fingerprinting and custom grouping enhancements documentation to learn more.

Sentry may sponsor your account if you're a non-profit, open source project, educator, or student. You can apply for a free Sponsored Sentry plan here: https://sentry.io/for/good/

You can manage notifications in your personal notification settings. Note that there are options for workflow notifications that are separate from options for project alerts. Selecting "default" means that project will follow the top level project filter.

In the body of each email you will see the specific reason you are receiving that email.

Select Unsubscribe to stop receiving emails for this issue.

You will automatically be subscribed to an issue when taking one of the following actions:

Assignment

Comments

Regressions

Resolution

You can unsubscribe from a particular issue by selecting that issue and clicking the Unsubscribe button.

Reach out to any Organization Ownerin your organization to remove this for you. They can do so by going to Organization Settings >> Members >> Your name and clicking "Reset two-factor authentication".

If you are theOrganization Owner, enabling two-factor authentication on a user account is a security feature, and to remove or reset it, we must verify your identity. Please contact support and send a copy of your government-issued photo ID to review.

Yes. Please reach out to Support and include the following:

Organization slug

New domain you need to add

Contact email address with the new domain (so we can verify)

Note that we can also swap your domain for you if it's been changed, just let us know!

Note: You must have theManageror OrganizationOwnerrole to add a new member.

Navigate to the upper left dropdown >>Membersand click "invite members". Complete the form and they'll receive an email to join your Sentry organization. See our documentation about member roles if you have questions about permissions.

Note that if you're on the Developer (free) plan you're limited to one member and cannot invite anyone else. Upgrade to a paid plan to invite more members.

Warning: For security reasons, Sentry Support may not be able to restore access to accounts with two-factor authentication enabled if you lose your authentication device or don't have access to your Recovery Codes.

With two-factor authentication, or 2FA enabled, you're able to log into your Sentry account with this additional security measure. 2FA provides another layer of security from a malicious person trying to access your account by requiring the user to enter the passwordand a generated authentication code.

You can manage yourtwo-factor authentication settings on your Account Settings > Security page.

After 2FA is enabled, any time you try to log into your account you will need to enter in your password and the authentication code that is generated by one of the methods shown in the screenshot above.

We highly suggest you store yourRecovery Codesin a secure place, preferably somewhere you can access from a different device. In the event you lose or change the primary device for 2FA, you still have a backup method for accessing your account.

Note: If you need to change your primary device for 2FA such as changing phones, please make sure you disable 2FA for your account before enabling it on a new device.

Open up your Account settings.

ClickMore.

ClickCloseAccount.

Review the information on the page, then selectCloseAccount.

Reserved capacity is purchased for the current billing year and cannot be refunded. Downgrading will reduce your reserved capacity for the following annual billing period.

Yes.

Once events have been processed and grouped they count towards your quota. Setting an issue's status to 'ignored' in the UI prevents you from being notified about future events for that issue. 'Ignore Until' can be a great way to improve your workflow.

Any events that are ignored on the client side (i.e shouldSendCallback) do not count toward your quota since they never hit our servers.

You can go to Usage and Billingon the left hand sidebar while in your main organization view and then select Update billingjust below the Spike Protection toggle on the Usage and Billing page.

Note: You must have either Billing or Owner permissions to both access and/or make changes to this information.

We do not have additionalinformation as towhy your card was declined. We use Stripe for processing payments, so you might find this page useful.

Contacting your bank or credit card company may be the best way to solve the issue.

We let you set a cap on the maximum amount of on-demand events that you can be charged for. On theUsage & Billingpage you can toggle the unlimited on-demand spend, as well as set a cap.

Reserved capacity allows you to prepay annually for significant discounts. Your prepaid, reserved capacity is always applied before on-demand capacity. Unused reserved capacity expires at the end of each billing month.

Reserved Capacity Price Schedule

Events

Price

Price per additional event

$0.00024 / event$0.00019 / event (with annual commit)

All additional events are rejected.

In order to see future events for that month you must increase your on-demand spend (or upgrade to a larger plan).

Your plan will continue until the end of the current billing cycle. After this, youll revert to the base free plan, with includes a limited number of events and team members.

Note that you may have an annual contract that you pay for on a monthly basis - in this case you will not be downgraded until the annual contract ends.

We support most major credit card providers[1]:

Visa

MasterCard

American Express

JCB

Discover

Diners Club

Additionally we support invoicing for our enterprise accounts. For more information on enterprise pricing, you can contact [email protected].

[1] Credit cards are processed via Stripe.

You can add an alternate email address in your Email settings within your Account Settings. Once the email address is verified, you can update the drop-downs for Alerts and Workflow under the "Fine Tuning" section in your Notification settings.

We guarantee your new, lowered on-demand spending cap will be applied within 24 hours. In the meantime, the old on-demand spending cap will remain in effect. However, in most cases, the new spending cap will be applied within minutes.

After the new spending cap is in effect, all additional events will be rejected and no additional on-demand capacity will be added. At end of billing month, you will be charged for any on-demand capacity consumed.

If you've begun a trial from a paid account, you will simply be reverted to your previous plan plan.

If you've begun a trial from the Developer (free) plan you will be returned to the Developer plan, which has limited members and events.

If you've begun a trial from the legacy Free plan, when your trial ends you will be on the current Developer (free) plan, not the legacy Free plan like before.

For all scenarios, all of your previous events, comments, settings, and other data will remain unchanged.