General Page
-
Agent
-
AutoTrace
-
Infrastructure Monitoring
-
Req - Install - Config
- Getting Instana Agent logs for Windows Host
- Getting Instana Agent logs for Linux Host
- Getting the Instana Agent logs for Windows Host
- How to collect the Instana Agent DEBUG logs
- Agent failure due to inability to add repositories
- Multi MySQL monitoring
- How to Configure more than one MySQL Instance
- Processing Time - Response time of the application/service/endpoint
- JVM and Spring Boot missing data due to writing permissions
- "Started At" field changes based on time frame selected even if Process ID remains the same
- Instana Host Agent - How to?
-
-
Backend On-Prem
- How to collect Instana doc for Self-hosted Instana backend environments on Kubernetes/OpenShift
- Sliding vs. Tumbling window
- Changing Default Admin name and Password - Instana Backend
- How to Update Manually the Instana Product Repository for OnPrem
- Backend Password Reset
- Migrating Instana from Single-Host to Multi-Host
- Instana backend upgrade best practices (on-premises)
- Self-hosted Backend Password Reset
- Migrating Instana from Single-Host to Multi-Host
-
Backend SaaS
-
Event & Alerting Management
-
Instana for z/OS
-
Integrations
-
Mobile Monitoring
-
Platform Monitoring
-
Sensors - Setup & Discovery
-
Synthetic Monitoring
-
User Interface & Customizations
-
User Management & Authorization
-
Vulnerabilities
-
Website Monitoring
-
Zapm Connect
How to open a case in our Support?
Need text
Procedure
- Go to the IBM Support page
- Choose Open a case
- For product choose Instana Observability
- Fill out the rest of the fields
- Submit case
How to open an AHA Tool! idea?
How to get the Linux Agent logs?
How to get the Linux Agent DEBUG logs?
How to get the Windows Agent logs?
How to get the Windows Agent DEBUG logs?
How to get the on-prem logs?
You can run the instana debug command to dump the debug information of the system where the backend is running. In case something is wrong, this is the first step.
The debugging information includes information about the system, the hardware, the state of all the installed components, and their health. This data is collected locally, and nothing is transmitted over the wire.
A temporary directory (instana-debug_{timestamp}) is created in the same directory where you run the instana debug command with information about the system, the hardware, the state of all the installed components and their health, and component configuration settings, which give support engineers helpful information. Additionally, all information is written into instana-debug_{timestamp}.tar.gz a file.
How to collect agent data on Kubernetes and Red Hat Openshift?
How to collect data for the Self-hosted Backend on Kubernetes and Red Hat Openshift?
Instana list of issues by severity
When a user opens a case the severity level is set, but the severity of a case can be adjusted during the life of the case as more information becomes available. The following is a list of severity levels with a definition. Severity 1 issues are typically reserved for production system down or critical outages.
| Severity | Business Impact | Detailed description |
|---|---|---|
| 1 | Critical | System or Service Down Business critical functionality is inoperable or a critical interface has failed. This usually applies to a production environment and indicates an inability to access products or services resulting in a critical impact on operations. This condition requires an immediate solution. Note: We will work with you 24 hours a day, seven days a week to resolve Severity 1 problems provided you have a technical resource available to work during those hours. You must reasonably assist IBM with any problem diagnosis and resolution. For IBM Cloud services, you must log a Service Down case within 24 hours of first becoming aware that there is a critical business impact and the Cloud service is not available. |
| 2 | Significant | A product, service, business feature, or function of the product or service is severely restricted in its use, or you are in jeopardy of missing business deadlines. |
| 3 | Some | The product, service, or functionality is usable and the issue does not represent a significant impact on operations. |
| 4 | Minimal | An inquiry or non-technical request. |
Where do I find more information?
Was this topic helpful?
Document Information
Modified date:
31 August 2023
UID
ibm17010023