Helicone Community Page

Updated 3 months ago

Custom properties not showing in results table anymore

Despite being recorded (see second screenshot).
Attachments
CleanShot_2024-07-01_at_11.12.382x.jpg
CleanShot_2024-07-01_at_11.12.462x.jpg
s
D
C
8 comments
org id b15046aa-bf53-460e-aee7-ae3908bcae35
To address the issue of custom properties not appearing in the results table even though they are recorded, you can follow these steps:

  1. Ensure Proper Header Format:
    • Verify that you are using the correct header format for custom properties. The header should be named in the format Helicone-Property-[Name] where [Name] is the name of your custom property.
    • Example:
      Plain Text
      curl https://oai.helicone.ai/v1/completions \
        -H 'Content-Type: application/json' \
        -H 'Helicone-Auth: Bearer HELICONE_API_KEY' \
        -H 'Helicone-Property-Session: "24"' \
        -H 'Helicone-Property-Conversation: "support_issue_2"' \
        -H 'Helicone-Property-App: "mobile"' \
        -d ...
    source
  1. Check Request ID:
    • Ensure that each request has a unique Request ID. You can pre-define the Request ID and assign it to the header Helicone-Request-Id.
    • Example:
      Plain Text
      import { OpenAI } from "openai";
      const uuid = randomUUID(); // define your Request ID
      const configuration = {
        apiKey: process.env.OPENAI_API_KEY,
        basePath: "https://oai.helicone.ai/v1", // Set the API endpoint
        defaultHeaders: {
          "Helicone-Auth": `Bearer ${HELICONE_API_KEY}`,
          "Helicone-Request-Id": uuid, // Assign your Request ID
        },
      };
    source
  1. Update Custom Properties Post-Request:
    • If you need to update custom properties after the request has been made, you can do so by making a PUT request to the designated API endpoint. Ensure you have the correct Request ID from the response header helicone-id.
    • Example:
      ```python
      const { data, response } = await openai.chat.completions
      .create({
      model: "gpt-4o",
      messages: [
      {
      role: "user",
content: "Write 5 random words",
},
],
})
.withResponse(); // include this line

console.log(response.headers.get("helicone-id")); // get the request ID
`` [source](https://docs.helicone.ai/features/advanced-usage/custom-properties) 4. **Verify Data in Helicone Dashboard**: - After ensuring the above steps, check the Helicone dashboard to see if the custom properties are now appearing in the results table. You can access the Helicone UI at http://localhost:3000` and add users or check logs as needed.

If you have followed these steps and the custom properties still do not appear, you may want to reach out to Helicone support at help@helicone.ai or schedule a call with the team for further assistance. source
Hi , sorry about the inconvenience, we’re looking into this and will get back to you soon.
Filtering still works so not a huge deal
Hi, we pushed out a fix last night. Is it working for you now?
Add a reply
Sign up and join the conversation on Discord