github.com/go-graphite/carbonapi@v0.17.0/.github/ISSUE_TEMPLATE/bug_report.md (about)

     1  ---
     2  name: Bug report
     3  about: Create a report to help us improve
     4  title: "[BUG] "
     5  labels: bug
     6  assignees: ''
     7  
     8  ---
     9  
    10  **Describe the bug**
    11  A clear and concise description of what the bug is.
    12  
    13  **CarbonAPI Version**
    14  What's the CarbonAPI version you are running? Does this issue reproducible on current master?
    15  
    16  **Logs**
    17  If applicable, add logs (please use log level debug) that shows the whole duration of the request. Request can be identified by UUID if needed.
    18  
    19  **CarbonAPI Configuration:**
    20  Please include carbonapi config file that you are using (please replace all information you don't want to share, like domain names or IP addresses).
    21  
    22  **Simplified query (if applicable)**
    23  Please provide a query that triggered the issue, ideally narrowed down to smallest possible set of functions.
    24  
    25  If you have a complex query like `someFunction(otherFunction(yetAnotherFunction(metric.name), some_paramters), some.other.metric.name)` it is very helpful to try to remove some of the functions around the `metric.name` and check which one triggers the problem.
    26  
    27  **Backend metric retention and aggregation schemas**
    28  Please provide backend's schema (most important thing - if query cross retention period or not), aggregation function, xFilesFactor (if applicable).
    29  
    30  **Backend response (if possible)**
    31  If that's possible - please share some sample set of backend responses. Most important thing here:
    32  1. Are all backend responses the same? If not, what's the difference?
    33  2. Do they contain special values, like Inf/NaN values?
    34  3. Do all of them have same step?
    35  
    36  To get the backend response, you can send request for the same metrics towards the backend:
    37  1. You should remove all the functions from the request as most backends do not support any of them
    38  2. You might need to convert relative time offsets to unix time, e.x. if you have "from=-1h" you might need to pass `from={current-timestamp}-3600&until={current-timestamp}` where `{current timestamp}` should be replaced by actual value. On some systems you can use command line to get current timestamp `date +%s` or even you can ask for a timestamp that was 1 hour ago: `date +%s --date="1 hour ago"`
    39  
    40  **Additional context**
    41  Add any other context about the problem here. Like version of a backend.