#Does File Bandwidth charge include egress to Axiom?

9 messages · Page 1 of 1 (latest)

sly oak
#

Does File Bandwidth charge include egress to Axiom?

hushed domeBOT
#

Hi @sly oak. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave:

#

Based on the provided knowledge sources, I don't have specific information about whether File Bandwidth charges include egress to Axiom. The documents mainly discuss file bandwidth in relation to user access and CDN usage, but don't explicitly mention Axiom in this context.

However, it's worth noting that Convex does support log streaming to Axiom, as mentioned in the Log Streams documentation (https://docs.convex.dev/production/integrations/log-streams). This feature allows you to stream logs, including function executions and console logs, to Axiom for better observability and historical log retention.

While the log streaming feature is mentioned, there's no explicit information about whether this log streaming to Axiom counts towards your file bandwidth usage. To get a definitive answer on this specific question, it would be best to reach out to Convex support directly or ask in their community Discord channel.

Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:

#

@sly oak Kapa.ai is still learning and improving, please let me know how I did by reacting below.

sly oak
#

@hushed dome I meant Database Bandwidth

hushed domeBOT
#

Let me check the knowledge base for you again. One moment! :books:

#

I apologize for the confusion in my previous answer. Let me address your question about Database Bandwidth specifically.

Based on the provided knowledge sources, there is no explicit mention of Database Bandwidth charges including egress to Axiom. However, we can infer some relevant information:

  1. Database Bandwidth is measured for function executions. According to the Log Streams documentation (https://docs.convex.dev/production/integrations/log-streams#function_execution-events), function execution events include usage metrics for database read and write bytes:

    "usage": {
  "database_read_bytes": number,
  "database_write_bytes": number,
}

    These metrics make up the database bandwidth used by the function.

  2. Log streaming to Axiom is a separate feature that allows you to send logs and metrics to Axiom for analysis and visualization. This is mentioned in the Log Streams documentation (https://docs.convex.dev/production/integrations/log-streams) and further explained in Stack article about Log Streams (https://stack.convex.dev/log-streams-common-uses).

  3. The log streaming feature itself doesn't appear to be counted as part of your Database Bandwidth usage. It's a separate Pro plan feature that allows you to export your logs and metrics.

Given this information, it seems that Database Bandwidth charges are primarily related to your application's database operations, not the log streaming to Axiom. However, to get a definitive answer about whether there are any hidden costs or bandwidth charges related to Axiom log streaming, it would be best to contact Convex support directly or ask in their community Discord channel.

Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:

#

@sly oak Kapa.ai is still learning and improving, please let me know how I did by reacting below.

spice basin
#

Hey Omar, we do not currently charge for bandwidth for exporting to integrations like Axiom or Sentry, this is included in the price for function calls usage.

p.s. I noticed your support request submitted via the dashboard may have gotten lost / failed to send. We're pushing out a fix for that now, so future tickets you file will go through!