General troubleshooting
β Nobl9 official SLOβ
You can find Nobl9 SLO in the Nobl9 Service Level Commitment.
β SSO login for Nobl9 Teams customersβ
SSO login is not activated for Nobl9 Teams customers. This is an enterprise feature.
β SSO integrations available with Nobl9β
The following integrations are supported:
- Azure
- Okta Org2Org
β Bulk user import via SSOβ
SSO grants access but does not allow for more granular user management. We can bulk create the users for the client. They can email a spreadsheet or CSV to support.
β User limit per Nobl9 Free Editionβ
Under the Nobl9 Free Edition plan, you can have a maximum of 10 users and add 20 SLOs from up to five data sources.
β If I didn't activate my Nobl9 Free account, is there a way you can do it for me? Does the activation link expire?
The activation link expires after 72 hours. If you didn't verify the email address in the first email you received, you can sign up again using the same email address. If that doesn't work, contact Nobl9 support.
β Nobl9 data retention periodβ
The data retention period in Nobl9 depends on Nobl9 Edition:
- Nobl9 Free customer metrics for 3 months
- Nobl9 Teams customer metrics for 12 months
- Enterprise customer metrics for 2 years
On demand, a detailed policy about data retention can be shared. This option requires signing a Non-Disclosure Agreement.
β Access to Nobl9 Terraform providerβ
Refer to the official Nobl9 Terraform provider page.
The SLOcademy section provides the step-by-step guide
on how to configure Nobl9 resources using the Nobl9 Terraform provider.
β Viewing Nobl9 dashboards or SLOs by unauthorized usersβ
Currently, it is not possible to view a Nobl9 dashboard without an account.
β Viewing generated access tokens in the Nobl9 UIβ
You won't be able to see the generated access tokens in the Nobl9 UI, but it's possible to retrieve them via sloctl
. If you want to retrieve client_id
and client_secret
for all agents in your organization, use the -A
flag in the sloctl get agent
command as follows: sloctl get agents -Ak
.
β Shutting down access tokens and impact of a parent access key / secret on the access tokenβ
Once you invalidate a client ID and client secret, the access token generated with these invalidated credentials becomes inactive as well.
β Limiting an API token scopeβ
The scope of an API token is based on the permissions of the user who generated the token in the UI.
β Agent logs locationβ
Agent logs exist only in the standard output within the agent container.
β Logging issues with Nobl9β
You can log a ticket at our support page or email at support@nobl9.com. If you donβt have access to the Support Center, click Not a member? to sign up.
β Response time for customer questionsβ
A support response should come in less than 24 hours for Nobl9 Teams users and in less than 8 hours for enterprise users, during normal business hours. For Nobl9 Free users, we have a public Slack channel that you can use.
β Support questions per customer limitβ
Customers can ask support as many questions as they need.