Getting Started

How do I log in for the first time?

Parascope uses Single Sign-On (SSO) via your organization's identity provider. Navigate to your Parascope URL (e.g., your-company.parascope.io), click Sign in with SSO, and authenticate. Your account is created automatically on first login.

How do I create an API token?

Click your user avatar, select Settings, navigate to API Tokens, and click Create Token. Copy the token immediately as it is only shown once. See API Tokens for details.

What data does Parascope collect?

Parascope discovers configuration items (CIs) from your infrastructure: servers, containers, databases, network devices, cloud resources, and more. It collects configuration state and runtime metrics but does not modify your infrastructure. See How Parascope Works for the full picture.

Data and Collection

Why is my collector showing "Circuit Open"?

Circuit Open means three consecutive collection attempts have failed. The collector pauses for 60 seconds before retrying. Common causes:

Target system unreachable -- check network connectivity and firewall rules
Credentials expired -- rotate credentials in Settings > Credentials
API rate limiting -- the target system is throttling requests

See Managing Collectors for health state details.

How often does data refresh?

Each collector runs on a configurable interval, typically every 5 minutes. You can trigger a manual collection from the collector's source card by clicking the refresh button.

Why are some CIs showing as "Inactive"?

A CI becomes inactive when it is no longer discovered by its collector. This usually means the resource was deleted or decommissioned. Parascope preserves inactive CIs for historical reference. See CI Lifecycle for the full lifecycle model.

How do I add a new data source?

Navigate to Settings > Collectors, find the relevant collector, and click Add Source. You will need the connection details and credentials for the target system. See the collector-specific guides under Collectors for configuration details.

My collector credentials expired. How do I fix this?

Go to Settings > Credentials, find the affected credential, and update it with new values. The collector will automatically pick up the new credentials on its next collection cycle. If the collector is in Circuit Open state, it will retry within 60 seconds.

Search and Queries

How do I find a specific CI?

Use the global search bar at the top of the page. You can search by name, IP address, hostname, or any attribute. For advanced filtering, use the filter controls on the CI list page. See Searching and Filtering.

What is ParaQL?

ParaQL is Parascope's query language for advanced data exploration. It lets you write structured queries across all your infrastructure data, join across sources, and create visualizations. You can also type natural language questions and ParaQL will translate them. See ParaQL Query Language.

How do I export data?

From any CI list or ParaQL result, click the export button to download as CSV or JSON. API users can also fetch data programmatically via the REST API.

Permissions and Access

I can see the UI but no data appears

This usually means your user role does not have a data scope that includes the CIs you expect to see. Contact your Parascope administrator to check your team membership and data scope assignments. See RBAC Administration.

I get "Permission Denied" on certain actions

Some actions (creating API tokens, managing credentials, configuring collectors) require specific permissions. Your administrator assigns permissions through teams. Check with your admin to get the appropriate role.

Billing

How are CIs counted for billing?

Billing is based on the number of active CIs in your tenant. Inactive and deleted CIs do not count. The count is sampled daily. See Billing and Pricing for full details.

What happens if my CI count spikes temporarily?

Short-lived spikes (e.g., during a deployment that creates many temporary containers) are handled gracefully. Billing uses the daily average, not the peak. If your average consistently exceeds your plan limit, you will be notified before any action is taken.

Troubleshooting

Authentication errors

Symptom	Likely Cause	Fix
"SSO configuration not found"	Identity provider not configured for your tenant	Contact your administrator
Redirect loop after login	Session cookie issue	Clear browser cookies for your Parascope domain
API token returns 401	Token expired or revoked	Create a new token in Settings
API token returns 403	Insufficient permissions	Check token owner's role and data scopes

Collector errors

Symptom	Likely Cause	Fix
All sources show Circuit Open	Collector pod crashed or restarting	Check collector status in Settings > Collectors
Single source unhealthy	Target system connectivity or credential issue	Check the source's error message for details
Data is stale (last collection old)	Collection interval too long, or collector paused	Trigger manual collection or check collector health
"Connection refused" errors	Target system firewall or service down	Verify the target is accessible from the collector network

No data appearing after setup

Verify the collector is running: Settings > Collectors should show your collector as healthy
Verify at least one source is configured and enabled
Check that credentials are valid (no red error indicators)
Wait for at least one collection cycle to complete
If using an appliance, verify it shows as connected in the collector management page

Changes not showing up

The change history tracks modifications to CI configuration fields, not runtime metrics. If only metrics changed (CPU usage, memory), no change is recorded. Changes appear after the next collection cycle detects a difference.

Getting Help

If your issue is not covered here, you can:

Submit a support ticket from the Support page in the app
Report an issue directly from any CI detail page using the "Report Issue" button
Contact security issues via our Vulnerability Disclosure Policy

FAQ and Troubleshooting