• Kayvan Shah

    Kayvan Shah

    4 months ago
    Getting these errors & warning while starting the server Env: python 3.6.9
    Kayvan Shah
    Anna Geller
    +1
    10 replies
    Copy to Clipboard
  • r

    Roey Brecher

    4 months ago
    What’s the best way to prune\cleanup old data on Prefect Server? the
    .prefect
    directory reached a size of 428G.
    r
    Anna Geller
    3 replies
    Copy to Clipboard
  • Sebastian Beschke

    Sebastian Beschke

    4 months ago
    EDIT It seems I was seeing something else, please disregard 😃 Hi! I’m not sure if this has been discussed before… I’m running Prefect Server on EC2 along with an ECS agent deployed as a fargate task. I’m seeing the issue that if the server ever goes down (or the connection is lost otherwise), the agent will show a
    requests.exceptions.ConnectionError
    , but does not exit. However it’s also does not seem to reestablish the connection once the server becomes available again. Is there some way to either1. have the agent retry connecting some time after encountering a connection error, or 2. exit after a connection error so ECS can detect that and restart it? The way it looks now I have to manually restart the agent in this situation, which I don’t think is ideal… Am I missing something? Thanks in advance!
    Sebastian Beschke
    2 replies
    Copy to Clipboard
  • d

    David Beck

    4 months ago
    Hi all, I have having an issue with our logging implementation changes are not holding when registered to and running in Prefect Cloud. Essentially, the custom log handler (which is just opentelemetry-sdk) enforces a new
    _log_record_context_injector
    function to modify the names of
    PREFECT_LOG_RECORD_ATTRIBUTES
    for our purposes which is then added to the root Prefect logger. This function call occurs in a Task class I created which is set as an
    upstream_task.
    When this is run locally, all log records have the corrected attribute names. When run in Cloud, only the task run to initialize the log handler enforces the changes. Given that all tasks should inherent from the root logger, why are the changes not being implemented across the tasks/flow? Further info: we are using KubernetesRun with Docker flow storage. Also the changes hold when the implementation is run locally.
    d
    Kevin Kho
    9 replies
    Copy to Clipboard
  • s

    Stephen Lloyd

    4 months ago
    Hi. What is the overlap and important differences in features between Prefect Server and Prefect Cloud. I couldn’t find anything in the Prefect docs site that dealt with this. Context: We’re on Prefect Cloud now. We’re looking to upgrade our plan. Currently on a legacy plan WELL within the free tier, but we wanted to add additional users which requires setting up billing. Our procurement team got pricing that is a massive jump from $0/month. So much of a jump that we will have to either move to Prefect Server or move to AWS Managed Airflow. So trying to figure out what a change to Prefect Server might mean.
    s
    Anna Geller
    5 replies
    Copy to Clipboard
  • Lana Dann

    Lana Dann

    4 months ago
    is there a way to skip a directory when registering flows with the prefect cli?
    Lana Dann
    Kevin Kho
    7 replies
    Copy to Clipboard
  • Kayvan Shah

    Kayvan Shah

    4 months ago
    Is there a way to delete storage
    ../..> prefect storage
    Usage: prefect storage [OPTIONS] COMMAND [ARGS]...
    
      Commands for managing storage settings.
    
    Options:
      --help  Show this message and exit.
    
    Commands:
      create         Create a new storage configuration.
      ls             View configured storage options.
      reset-default  Reset the default storage option.
      set-default    Change the default storage option.
    Kayvan Shah
    Anna Geller
    3 replies
    Copy to Clipboard
  • Benson Mwangi

    Benson Mwangi

    4 months ago
    Hello, I have a prefect flow that I'm interacting with via the graphql API and it works perfectly. Now, I was wondering if it's possible to prefix the flow ID (i.e.when deploying the flow pre-fix the ID). I know this is counter intuative as this would mean there's no versioning of flows (i.e. perhaps the flow version is always the same). However, the reason I'm looking for this option is because my flows are executing tasks triggered through some APPS and I would not want to change the flow ID in each app whenever a flow is resubmitted. In short, is there a way to keep the flow ID constant or somewhat pre-fix it? Also, just for context I'm running a self-hosted prefect server. Looking forward and many thanks in advance.
    Benson Mwangi
    1 replies
    Copy to Clipboard
  • c

    Côme Arvis

    4 months ago
    Hello! All our flows are failing for about 20 minutes, with always the same issue (screenshots in the thread) We didn’t have this error before, do you know if there is any issue in your end? Thanks!
    c
    3 replies
    Copy to Clipboard
  • Matt Drago

    Matt Drago

    4 months ago
    Hey Folks, Been a while since I've frequented these slack channels, but I've finally gotten some time at work to upgrade the Prefect installation that I set up a while ago (version 0.14.14). I was looking at using the Helm charts so I could dispose of the ones that I hand crafted. One of the problems that I am trying to work out though is how to connect to the external DB. My deployment environment is a K8S cluster in GCP. In my current installation, I have configured cloud_sql_proxy sidecars for the graphql and hasura deployments. I cannot find a way to do this with the new charts. Is the only way to connect to the CloudSQL Postgres DB to use the private/public IP of the DB instance?
    Matt Drago
    Anna Geller
    +1
    14 replies
    Copy to Clipboard